Webhook

The channel for when a workflow is started not by a person in a chat but by another system: a form on your site, a CRM, a task scheduler, your own backend.

Enabling it

Deploy tab → Webhook channel. It issues a URL and an API key; the key is shown in full once and behind a button afterwards. The panel carries a ready curl example — the easiest thing to copy and try immediately.

The request body arrives at the entry node whole: in the graph it is the value on entry’s output, and the trigger context sits on its data port. Take it apart from there with the JSON nodes or with templates.

What comes back

The webhook queues the run and answers immediately — the channel does not wait for a result. Check the outcome in Executions, or have the workflow deliver it: an HTTP request back, an email, a message in a messenger.

What next

• Scheduled runs — when the trigger is time, not another system.
• The HTTP request node — the way back out of a workflow.