The callback node sends pipeline results to an external URL via an HTTP request. It is a terminal node. Nothing connects after it. Use callbacks to integrate DocPipe with your backend systems, databases, or third-party services.Documentation Index
Fetch the complete documentation index at: https://docs.docpipe.ai/llms.txt
Use this file to discover all available pages before exploring further.
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. See the Business Central guide |
| Retry count | number | No | Number of retry attempts on failure. Defaults to 3 |
| Timeout (ms) | number | No | Request timeout in milliseconds. Defaults to 30000 |
Test mode behavior
When the pipe 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
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