Webhooks: start an Automation flow from Notes
Send each new database row, change or comment in Notes to a URL — an Automation webhook trigger starts a flow with it. Set it up, test it, and read the delivery.
Notes can send a signed POST to a URL whenever a database row is added, changed or deleted, or a comment is written. Point it at an Automation flow with a Webhook trigger and the flow runs with what happened in Notes — a task, an email, a CRM update. Only admins of the workspace manage webhooks.
Connect Notes to an Automation flow
- In Automation, make a flow that starts with Webhook and Publish it. Copy its Webhook URL and Secret: How a flow starts.
- In Notes, open Webhooks in the menu (admins only).
- Under New webhook, paste the URL and the Secret (optional) — the trigger's Secret from Automation.
- Pick the events: All events, or row.created, row.updated, row.deleted and comment.created.
- Click Create webhook. The message Webhook created — deliveries are signed with the secret you pasted. confirms it.
Every delivery is signed with that secret the way Automation checks it, so the trigger accepts it. A retry of the same delivery runs the flow once.
For any other receiver
Leave Secret (optional) empty. Notes makes a secret and shows it once, under The signing secret — shown only now: copy it into the receiving end. Each delivery carries X-Pages-Signature: sha256=… (HMAC-SHA256 of the body) and X-Webhook-Signature: sha256=… (of <X-Webhook-Timestamp>.<body>).
What a delivery holds
The body is JSON: event, workspace_id, occurred_at and data — the row or the comment. In the Automation flow it is in {{trigger.body.event}}, {{trigger.body.data.…}} and so on.
Test it and watch it
- In the table, the row's menu → Send a test sends a
test.pingdelivery — the flow runs once with it. The result shows in Last delivery a few seconds later. - Last delivery shows the receiver's answer and when: a
2xxworked; any other code is shown in red. - The switch in On stops and starts deliveries. Delete stops them at once.
If something doesn't work
Last delivery shows 403
Automation refused the delivery: the Secret is not the trigger's, or the flow is switched off or has no published version. Switch the flow on in Automation; for the secret, delete the webhook and create it again with the trigger's Secret.
Last delivery shows 404
The URL is not a flow's webhook — usually copied only in part. Copy the Webhook URL from the trigger again.
Last delivery shows failed
Notes could not reach the URL in three tries. Check the address; only https addresses are accepted.
"No spaces in the secret"
Paste the secret exactly as Automation shows it, without spaces or line breaks.
"Webhook limit reached (20)"
A workspace has at most 20 webhooks. Delete one you no longer use.