Webhooks & realtime
Webhooks
A webhook sends an HTTP request to your URL whenever rows change in a table.
- Open a table, click the ⋯ next to the view name → Webhooks → Create webhook.
- Enter the URL and the method (usually
POST). - Choose the events: rows created, rows updated, rows deleted, fields created/updated/deleted, views created/updated/deleted, or all events. Row events can be limited to changes of certain fields or to rows visible in a view.
- Add headers if your receiver needs authentication, e.g.
Authorization: Bearer .... - Choose whether to use field names instead of ids in the payload.
- Click Trigger test webhook to send a sample, then Save.
Payload
{
"table_id": 42,
"database_id": 7,
"workspace_id": 3,
"event_id": "ad3f...",
"event_type": "rows.created",
"items": [
{ "id": 128, "order": "1.0000", "Name": "Northwind Labs", "Amount": "1240" }
]
}
Updated-row events also contain old_items with the previous values.
Delivery
- Every call and its response are visible in the webhook’s call log.
- Failed calls are retried; after too many consecutive failures the webhook is deactivated and the table’s admins are notified. Reactivate it in the webhook settings.
- Respond with a
2xxstatus within a few seconds and do slow work asynchronously.
Webhooks vs automations
Use a webhook when another system should receive raw events. Use an automation when you want to transform data, call several services or add conditions without writing a receiver.
Realtime updates
The web interface updates live through a WebSocket at /ws/core/. Your own
applications can use it too:
- Connect to
wss://your-server/ws/core/?jwt_token=<JWT>. - Subscribe to a table:
{"page": "table", "table_id": 42}. - Receive messages such as
rows_created,rows_updated,rows_deleted,field_created,view_updated.
Zapier, Make and n8n
Integration platforms connect through the REST API with a
database token:
use their HTTP modules with Authorization: Token ..., and point their
webhook triggers at a Basemind webhook.