How do I send voice notes to another app with a webhook?

Create a webhook in Sentio settings, give it an HTTPS address you control, and choose which events and note fields it should receive. Sentio then sends a signed POST request with a JSON payload whenever a matching event happens, such as a note being created. Something has to be listening at that address, so this suits people comfortable with a small script or an automation service. It is not a one-click connection to Notion or any specific app.

Last reviewed October 23, 2026

What you set up

In Settings, under Webhooks, you name the webhook, paste the destination address and pick the events: entry created, entry updated, entry deleted, export completed, and a test event. You also choose which parts of a note are included: title, transcript, rewritten text, timestamps, tags and category. A test button sends a sample so you can confirm your endpoint receives it. When the webhook is created Sentio shows a signing secret once, so copy it then. The settings page has a regenerate button, but we could not find the server route behind it, so if you lose the secret, plan on creating a new webhook.

What arrives at your endpoint

Each delivery is a POST with a JSON body containing the event name, a timestamp, a source block, and a note object with the note id plus whichever fields you enabled and that the note actually has. There is no audio file in the payload. Headers carry the event name and timestamp, and, when a secret exists, a signature. The events fire when notes are created, edited or deleted through the app, so saving a new web recording is the typical trigger. We have not verified that notes created by bot-joined meetings trigger webhooks.

Verify the signature

The signature header holds v1= followed by an HMAC-SHA256 of the timestamp, a period and the raw request body, keyed with your secret. Recompute it on your side from the exact bytes you received and compare, so a stranger who finds your address cannot send you fake notes. Sentio sends the timestamp in its own header, so you can also reject deliveries that are far from the current time. Do this before your script writes anything anywhere.

Reliability, limits and what you still build

Deliveries are queued and sent in the background, so saving a note does not wait on your server. A failed delivery is retried up to three more times with growing delays, each attempt has a 30 second timeout, and the result is recorded in a delivery log you can open from the webhook. An account can have 100 deliveries in an hour. The address must use HTTPS in production, and addresses on localhost or private networks are blocked, so a script on your own laptop needs a public address first. After the note arrives, writing it into a database, a task manager or a document is your code. The Yearly plan lists webhook workflows among its features.

Common questions

Can a webhook send notes to Notion?

Only if you build the receiving side. Sentio has no built-in Notion integration, so your endpoint would have to write to Notion itself.

What happens if my server is down?

Sentio retries the delivery up to three more times with increasing delays. If it still fails, the failure is recorded in the delivery log for that webhook.

Can I point a webhook at localhost?

No. Localhost and private network addresses are blocked, and production requires HTTPS. Use a public HTTPS address.

Does the payload include the original recording?

No. It carries note text and metadata according to the fields you select, not the audio.