Skip to main content
Send a templated HTTP request after a workflow completes so another system can receive the call outcome.

​
Prerequisites

  • A destination service that accepts the chosen HTTP method.
  • A credential or secure header strategy if the destination requires authentication.

​
Configure a completion request

  1. Add a Webhook node to the workflow.
  2. Turn it on, choose GET, POST, PUT, PATCH, or DELETE, and enter the destination URL.
  3. Select an optional managed credential and add only the custom headers the destination needs.
  4. Build the JSON payload with run context values such as workflow ID, initial context, gathered context, annotations, and call metadata.
  5. Complete a test call and confirm the destination received the expected shape.

​
Constraints and failure states

Webhook nodes are standalone integration nodes and do not require graph edges. When disabled, the request is skipped. A destination failure does not make an already completed call safe to retry automatically; design the receiver for idempotency.

​
Protect your data

Send the minimum payload and use a managed credential instead of embedding a secret in custom headers. Treat transcripts, recordings, and context fields as sensitive unless the receiver is approved for them.

Related topics

Tracing configurationHTTP tool configurationTemplate variablesGlobal nodeAgent node