Zapier, n8n and Make
Start Zapier Zaps, n8n workflows and Make scenarios when rows are inserted, updated or deleted, through database webhooks: setup in each tool, what the workflow receives, and fetching the changed rows.
Automation tools start from a database webhook: Sovaria calls the tool’s webhook URL after a write to a table (Database webhooks). Copy the URL from the tool, then add it under Schema › Webhooks with the table and events to watch.
| Tool | In the tool |
|---|---|
| Zapier | Webhooks by Zapier › Catch Hook, then copy the hook URL. |
| n8n | Add a Webhook trigger node (method POST) and copy its production URL. |
| Make | Webhooks › Custom webhook, then copy the address. |
The workflow receives which table changed, the event and how many rows; not the rows themselves. Add a step that fetches what it needs from your project’s REST API with a server key kept in the tool’s secrets.
{
"type": "database.change",
"project_id": "…",
"table": "orders",
"event": "INSERT",
"timestamp": "2026-10-20T10:15:02.120Z",
"event_id": "…",
"data": { "row_count": 1 }
}- Each delivery has
X-Sovaria-Delivery(unique) andX-Sovaria-Signature. Zapier, n8n and Make can check the signature in a code step (Alerts: Slack, Discord, Teams, webhooks). - Failed deliveries are retried and then kept as dead letters you can replay from the delivery log (Database webhooks).