Webhook

Identifier and availability

• Type: action
• Stable identifier: send_webhook
• Status: Selectable — available in the new-node selector and importable.

Purpose

Sends a webhook request to another system.

Prerequisites and context

Required configuration: url, payload. Review the available context below before using variables.

Parameters

Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.

Inputs and available variables

This node declares no additional variable groups. The always-available date group and context inherited from its path still apply.

Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.

Connections and branches

This is a sequential action with no branch ports. A root placement uses from set to null and branch set to actions; a branch placement uses the branching action key and branch token. Use a 1-based order within that path.

Connection fragment:

{
    "from": null,
    "to": "action_send_webhook",
    "branch": "actions",
    "order": 1
}

Valid JSON node example

{
    "key": "action_send_webhook",
    "type": "action",
    "name": "send_webhook",
    "display_name": null,
    "parameters": {
        "url": "https://example.com/automation-hook",
        "payload": {
            "contact_id": "{{contact.id}}",
            "event": "automation"
        }
    }
}

Validation and runtime caveats

Payload string values support runtime variables. The destination URL is validated as an absolute HTTP(S) URL at import and should be reviewed for external side effects.

See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.