Skip to main content
A Trigger gambit is a webhook entry point. An external system POSTs to its endpoint, and the flow starts from that gambit rather than from a conversation the end user opened.

​
When to use it

Use it when your system, not the end user, decides the conversation should happen: an order ships, a payment fails, a renewal is due. The trigger sends nothing itself. A downstream Channel gambit sends the first message, and on WhatsApp that message must be a template.

​
The gambit and its editor

Every page in this section shows the same demo flow: Start, a Welcome message, the gambit this page covers, then End. The gambit sits third, selected, with its editor open on the right. The rest of the screen is dimmed. The gambit renders as a Trigger pill with the line Webhook entry point, one outgoing Default handle, and nothing feeding into it.

​
Trigger configuration

The endpoint always runs the published flow. Publish the agent before you call it, and publish again after you change this gambit, or the call fails.

​
Authentication

The endpoint needs an API key. Until one exists the editor shows No API keys configured, with a Generate key button beside it. Generating a key needs a paid plan, and the key is shown once. Key handling and the request format are covered in Authentication.