Baserow webhooks automatically notify external systems when your data changes. Webhooks eliminate manual data monitoring by sending instant notifications to any URL when your database changes occur.
Set up webhooks to trigger actions when rows are created, updated, deleted, or when views and fields change - no manual checking required.
Webhooks are automated notifications that Baserow sends to external applications whenever specific events happen in your database. Instead of constantly checking for changes, webhooks push updates to your systems in real-time.
When you create, update, or delete data in Baserow, webhooks instantly notify your chosen endpoint with detailed information about what changed. This enables seamless integration with other tools, automated workflows, and real-time data synchronization.
For webhooks in Baserow Cloud, there is a maximum capacity of 5,000 pending calls per webhook. Any additional calls beyond this limit will be dropped. Please note that webhook calls are handled one at a time.
Baserow supports multiple webhook events to match different integration needs:
If using deprecated webhook types (
row.created
,row.updated
,row.deleted
), migrate to the new batch types (rows.created
,rows.updated
,rows.deleted
) for better performance.
Access webhook settings
Configure basic settings
Select trigger events
Add custom headers (optional)
Test your webhook
Save and activate
Baserow sends structured JSON payloads containing event details and affected data.
Example payload for “View Created”:
{
"table_id": 50000,
"database_id": 1000,
"workspace_id": 300,
"event_id": "00000000-0000-0000-0000-000000000000",
"event_type": "view.created",
"view": {
"id": 0,
"table_id": 0,
"name": "View",
"order": 1,
"type": "grid",
"table": null,
"filter_type": "AND",
"filters_disabled": false,
"public_view_has_password": false,
"show_logo": true,
"ownership_type": "collaborative",
"owned_by_id": null,
"row_identifier_type": "id",
"public": false
}
}
Key payload elements:
table_id
, database_id
, workspace_id
specify the sourceevent_type
and event_id
describe what happenedView webhook call logs to troubleshoot issues:
In the webhook edit view, click Delete at the bottom. Warning: Deleted webhooks cannot be restored.
Baserow implements automatic retry logic for failed webhook calls:
200 OK
statusBaserow automatically retries failed webhook calls a limited number of times. Ensure your endpoint returns a 200 OK
status code and can handle temporary traffic spikes.
Yes, use conditional row update webhooks to trigger only when specific field values change. You can also use view-based webhooks that only trigger for rows matching view filters.
Check the webhook call logs in Baserow to see request/response details. Common issues include wrong URLs, missing authentication headers, or endpoints not returning 200 OK
status codes.
Baserow doesn’t impose strict rate limits, but ensure your receiving endpoint can handle the volume of changes in your database. Consider batching operations if you’re making many simultaneous updates.
Yes, webhooks work seamlessly with Zapier, Make, n8n, and other automation platforms. Simply use the webhook URL provided by your automation tool as the endpoint.
Based on the Baserow documentation structure, you might also find these topics helpful:
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions—we’re ready to assist you.
Contact support for questions about Baserow or help with your account