Webhooks

Webhooks push data out of the platform to an external URL. Where a subscription runs your SQL when something changes, a webhook takes the result of an event and delivers it to an endpoint you specify.

Requires an active configuration. Select one on the Settings page first.

How it works

1. Create an event whose SQL produces the payload you want to send.
2. Create a webhook that points at your external endpoint and references that event.
3. When the webhook fires, the platform runs the event and POSTs its query result to your URL.

Outbound calls from SQL

You can also make an HTTP call directly from event SQL with the CALL(WEBHOOK ...) provider — useful for notifying a partner system inline as part of a handler:

SELECT CALL(WEBHOOK "partner" FROM (
    SELECT &order_id AS order_id, 'completed' AS status TYPE OBJECT
) NEXT "on_delivered" GET) AS result;

See CALL functions for the full WEBHOOK / TG / SSE_SEND provider syntax.

Inbound webhooks

The reverse direction — an external service calling into the platform — is handled by an event exposed as an API endpoint, or by an AI Agent webhook trigger, which gives you a public /webhooks/{token} URL that fires an agent.

Related:

• Events — the handler that builds the payload
• Subscriptions — trigger events on data/blockchain/timer changes
• CALL functions (SQL)