DocumentationWorkflowsLogic and data
Send webhook response node
Sends an HTTP response back to whoever called the webhook. Put this block at the end of your workflow, it only kicks in if the webhook trigger is set to the 'Custom webhook response block' response mode. Otherwise it's ignored. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Sends an HTTP response back to whoever called the webhook. Put this block at the end of your workflow, it only kicks in if the webhook trigger is set to the 'Custom webhook response block' response mode. Otherwise it's ignored.
Use Send webhook response as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Send webhook response from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Send webhook response has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Status code | Configure this value in the node panel. | Standard |
| Response content | What goes back to the caller. Plain text or a JSON object, add fields as rows for convenience, or switch to raw JSON in the top right. Variables like {{ $json.text }} are allowed. Empty = the item is returned as-is. | Standard |
| Response headers | Configure this value in the node panel. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Success response to the webhook caller: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"ok": true,
"message": "Workflow läuft."
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.