Trigger reference

Workflows start manually, on a schedule, or from the outside via webhooks and API calls — see the triggers guidefor the concepts. This page lists what the platform registers, rendered from the live APIs (/node-engine/webhook-sources and/node-engine/trigger-variables).

Webhook sources

These sources have a dedicated adapter: incoming payloads are verified (source-specific signatures) and normalized into the common trigger shape. URL paths are relative to your webhook-api base URL (http://localhost:3200 on a local stack); {token}is the trigger's unguessable secret token.

Source	Webhook URL
discord	/triggers/discord/{token}
slack	/triggers/slack/{token}
telegram	/triggers/telegram/{token}
whatsapp	/triggers/whatsapp/{token}

Sources without a dedicated adapter still work: any generic JSON delivery to a workflow's webhook URL starts a run with the raw payload.

Trigger variables

Whatever starts a run is available to every node in the flow through these references:

Variable	Contains
$trigger.source	Where the event came from (e.g. telegram, webhook, api).
$trigger.sender	Who caused the event, as identified by the source.
$trigger.prompt	A natural-language message, when the source carries one.
$trigger.payload	The full normalized payload of the event.