POST each time its summary is generated. You can also have it fire when any note or file transcription finishes or fails, so an automation can react without polling. You can point it at Slack, Discord, n8n, Zapier, Make or your own server. Webhooks are a Pro feature.
Webhooks don’t fire for dictations. To trigger something from dictation, use a voice shortcut or the Vowen CLI.
How to set up a webhook
1
Open the Integrations tab
Go to Notes, click the Notes settings gear in the toolbar, then open the Integrations tab.
2
Configure the webhook
Click Configure on the Webhook card (“POST summaries to a URL”). The Configure Webhook panel opens.
3
Enter the URL
Paste your endpoint into Webhook URL. This is the only required field.
4
Add headers or a secret (optional)
Click + Add header for auth or routing headers. Fill in Signing secret if your receiver should verify requests.
5
Save
Click Save. The webhook is active once a URL is saved.

vowen webhook, which is also where you choose which events send a request.
When it fires
Everything except
note.created is off until you turn it on with vowen webhook events, so an existing endpoint keeps receiving exactly what it did before:
note.created and note.completed overlap: a summarized note sends both if both are subscribed. Pick note.completed alone if you want one request per finished note.
To send a note by hand, open it and use one of these:
- The Webhook box on the Details tab of the note’s side panel. It shows the endpoint’s host and a Send button.
- More options (…) › Send to webhook.

Send automatically
Send automatically is on by default. Turn it off to send only when you click Send. The endpoint stays configured.Payload
For any URL that isn’t a Slack or Discord webhook, the body is JSON:
The
note.completed, note.failed, transcription.completed and transcription.failed events send the same fields, plus:
For a transcription,
title is the file name and summary is empty. For a failure, summary is empty.
The Content-Type is always application/json. A custom header can’t change it.
If your interface language isn’t English, fallback text such as the default note title is localized.
Slack and Discord
Vowen recognizes Slack and Discord webhook URLs and formats the post for them. There is nothing to configure.
Slack and Discord posts carry the title and summary only. They don’t include the transcript, tags or note ID. Long summaries are truncated to fit each service’s message limits. For a failure event, the error takes the summary’s place.
Custom headers
Add any number of header name and value pairs under Headers, for example a bearer token. Header values are encrypted on your device. Vowen’s ownX-Vowen-* headers and Content-Type are applied after yours, so a custom header can’t override them.
Verify requests with a signing secret
Set a Signing secret and Vowen signs every request. Click Generate a new secret to create a random one, or paste your own. The secret is stored encrypted on your device and is never sent. Only the signature is.Headers
The signature is an HMAC-SHA256 of this string, keyed with your secret:
Example: verify in Node.js
Delivery logs
Click Logs in Configure Webhook to open Webhook Logs.- The last 25 deliveries are kept.
- Each row shows Time, Status, Trigger, Note and Duration.
- Expand a row to see the Endpoint, Format (
json,slackordiscord), Request headers, Request body and Response body. - Headers such as
AuthorizationandCookie, and any header whose name containskey,token,secret,passwordorauth, are stored as***. - Request and response bodies are cut off at 2,048 characters.
- Refresh reloads the list. Clear logs empties it.
Errors and retries
A failed delivery never interrupts recording or note generation. Non-2xx responses and network errors are written to the log. Vowen doesn’t retry, so use the log to spot failures and click Send on the note to try again.Limits
- Pro only.
- Meeting notes and file transcriptions. Not dictations.
- One webhook URL.
- The webhook settings are stored on this device and aren’t part of Cloud Sync.