Skip to main content
A Trigger gambit is an entry point for your own server. Your server calls the Tars API, 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 sample request body sends agentId, triggerId, channelUserId, and data. The data object carries the fields from Extra Request Data. Keys that can start this trigger lists the API keys with the Start conversations permission and access to this agent. Each key shows All resources or the agent’s name. With no matching key, the list reads No keys can start this trigger yet. Admins can select Create key or Manage keys, which open the organization’s integration settings in a new tab. Other members see that only admins can create and manage keys. See Authentication. Send test calls the endpoint with the key you entered. On success, it shows the status code and Conversation started.