Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| URL | string | Yes | The webhook URL to receive the results |
| Method | select | No | HTTP method: POST (default), PUT, or PATCH |
| Headers | key-value editor | No | Custom headers to include in the request |
| Body | template editor | No | Custom body template. Defaults to the full pipeline output |
| Body format | select | No | JSON (default) sends the body as application/json. OData Batch sends a Business Central JSON $batch request with Isolation: snapshot. Connector Write-back does not send a raw HTTP body; instead it posts the approved values from an upstream reconcile node back to the connector selected on this node, used to update existing records in Business Central and similar systems. It requires a connector to be selected, and when this format is chosen the Body template editor is hidden (the body is derived from the reconcile result, not authored manually). See the Business Central guide |
| Timeout (seconds) | number | No | Request timeout in seconds. The send is cancelled after this many seconds. Leave blank to use the system default (45s) |
Transient delivery failures are retried automatically by the platform; there is no retry-count field to configure on the node.
Connector write-back
This section appears only when Body format is set toConnector Write-back. It requires a connector to be selected on the node, and it surfaces a write-back panel with the following fields:
| Field | Type | Required | Description |
|---|---|---|---|
| Reconcile node | select | Yes | The upstream reconcile step whose approved values are written back. You need a reconcile node upstream, or this selector is empty |
| Record id path | template editor | Yes | The path to the record’s unique id, read at run time to target the update. For example, use {{value[0].id}} for a collection response or {{id}} for a single record |
| Write back line items | toggle | No | When on, reveals a required Line id path field |
| Line id path | template editor | Yes when Write back line items is on | Points at each line’s id, for example {{id}} |
Test mode behavior
When the pipeline is in Test mode, the callback node does not send the HTTP request. Instead, the run output shows a preview with:- The resolved request URL
- The resolved request headers
- The rendered request body
Connector Write-back callback, the test-mode preview shows the prepared request that would be sent, rendered in a read-only JSON editor.
Inputs and outputs
Allowed inputs: Any action node (extract, transform, route, merge, review, parse, validation). Output: Terminal node, no downstream connections. Sends an HTTP request to the configured URL with the pipeline results.Related
Webhooks and callbacks guide
Payload format, verification, and integration patterns
Webhook signing keys
Verify webhook signatures for security
Email output
Deliver results via email instead
Transform action
Transform data before sending via webhook
Business Central guide
Connector write-back and OData batch requests