REST API / Webhook
Push records to any REST endpoint. Batches the run's records into a single POST with a stable Idempotency-Key.
Push records to any REST endpoint. Batches the run's records into a single POST with a stable Idempotency-Key.
What this connection offers
Deliver records to a REST destination. This connector batches a run’s records into one POST with a stable duplicate-prevention key. The receiver must honour that key to prevent duplicates; use HTTP request for per-record requests.
| Detail | Value |
|---|---|
| Available uses | records |
| Sign-in | Credentials or access key |
| Catalogue identifier | rest.webhook |
| Connection scope | tenant |
| Direction | destination |
Connect
- Open Connections, choose to connect a service, and select REST API / Webhook with the uses listed above.
- Give the connection a recognisable name.
- Fill the settings below in the connection form. Secret fields belong in the credential form, never in chat.
- Check the connection status and run a connection test where offered.
- Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.
Connection settings
| Setting | Type | Required | Secret | Explanation |
|---|---|---|---|---|
Endpoint URL (url) | url | yes | no | — |
Bearer token (bearer_token) | password | no | yes | — |
Update credentials
Rotate credentials on the saved connection, then test and check a dependent task. A hidden stored secret is not an empty secret. Supply a replacement only when you intend to change it.
Diagnose a failure
Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See connection lifecycle.