Inbound webhook URL
A workflow with a webhook trigger has a unique inbound URL. POSTing to that URL starts a run immediately, with the request body available to the workflow as its trigger payload.
bash
curl -X POST https://eu1.wextl.com/hooks/<webhookId> \
-H "Content-Type: application/json" \
-d '{"example": "payload"}'Payload format
The webhook receiver accepts JSON bodies. The parsed body is exposed to every node in the run as the trigger's output — map individual fields the same way you would map any other node's output.
Webhook vs. schedule vs. run-once
Pick the trigger that matches when you want the workflow to run:
- Webhook — an external system decides when to run (an event just happened elsewhere).
- Schedule — you decide the cadence (every hour, every weekday morning).
- Run-once (via the REST API or MCP) — you decide the exact moment, e.g. kicking off a run from a script or an AI agent.
Testing a webhook
POST a sample payload to the webhook URL with curl (or any HTTP client) and check the run in your run history — the fastest way to confirm the trigger and field mappings behave the way you expect before wiring up the real sender.