Gambit mastery

A gambit is one step in a flow. This section holds one page per gambit type, each with the gambit shown in the builder, its editor open, and every setting that editor offers.

Every gambit type

The Gambits tab of the Gambit Types palette groups the types into five categories.

Category	Gambit	What it does
AI Agents	AI Agent	Runs its own reasoning and tool-use loop, then leaves through an exit route.
Input Types	Text	Collects a typed answer, with a format such as email or phone.
Input Types	Button	Offers a set of choices and captures the one the end user selects.
Input Types	Card	Offers cards with images, titles, and their own buttons.
Input Types	Star Rating	Captures a rating on a row of stars.
Input Types	Date & Time	Captures a date, a time, or both, from an inline picker.
Input Types	Media Upload	Accepts files, with type and size limits you set.
Input Types	Geo Location	Captures the device location.
Input Types	Auto Suggestion	Offers typeahead suggestions from a list you supply.
Flow Control	Start and End	Bound every flow. Start is placed for you, and End marks the conversation complete.
Flow Control	No Input	Sends messages and moves on without waiting for an answer.
Flow Control	Redirect	Sends the end user to an external address.
Flow Control	Language	Lets the end user choose the conversation language.
Integrations	API Call	Calls an HTTP endpoint and makes the response available to later gambits.
Integrations	Custom Code	Runs JavaScript against the flow’s variables.
Integrations	Channel	Sends a WhatsApp template message from a connected account.
Integrations	Trigger	Starts the flow from an external event.
Handoff	Live Chat	Escalates the conversation to a human agent.

Tool gambits come from the palette’s Tools tab instead. Each calls one action from a connected toolkit or from CodeKit, and they are covered in Enable and use actions. Knowledge Retrieval also sits in the Tools tab, badged Built-in. It searches knowledge bases and returns results to an agent, and it attaches to an AI Agent gambit the way a tool gambit does. See Attach knowledge to an agent.

What every gambit editor shares

Selecting a gambit in the builder opens its editor in the right panel. Every editor opens with the same header and metadata row, whatever the gambit type. The header runs along the top of that panel, and the LABEL and VARIABLE fields sit directly under it. The elements appear in this order, left to right.

Element	What it is
Type name and icon	The gambit type, in the editor header. A tool gambit shows its toolkit’s logo instead of a type icon.
Info icon	Appears on a tool gambit, and holds the toolkit’s description.
Unsaved changes	An amber dot and label beside the type name while the editor holds edits you have not saved. It reads Saving… with a spinner while the save runs.
Book icon	Opens the Documentation panel for this gambit type. Only API Call, Custom Code, Language, Trigger, and Channel carry one.
GID badge	The gambit’s number in the flow. The same number appears on the gambit in the builder.
Code icon	Opens the gambit’s raw JSON. While the JSON is open the icon becomes a panel icon, which takes you back to the visual editor.
Save	A green button that saves the edits. It appears only while there are unsaved changes, and it is disabled while a section holds an error.
Close icon	Closes the editor and returns the panel to its empty state.
LABEL	Names the gambit. This is the text shown on the gambit in the builder.
VARIABLE	Names the variable that stores the gambit’s captured value. It follows the label until you edit it by hand.

Renaming a variable does not update existing references to it in messages, API calls, conditions, or custom code. Update those gambits before you save. Validate in the toolbar warns about a reference that no gambit defines.

Below that row, the sections differ by type. Most gambits offer Messages for the bubbles sent before the step, and a type-specific Configuration section. Input gambits add POST Action, and all of them except Media Upload add Conditions. Every input gambit carries Allow Skip, which lets the end user move on without answering. It adds a skip hint to the prompt and an arrow button to the composer. Input gambits other than Text also carry Allow Free Text. It is on for a new gambit, and it adds a Free Input handle for typed answers. Input gambits and Live Chat also carry a Bridge Event accordion, which appears only when the agent runs inside a native mobile bridge. It sends an event type and key and value parameters to the host app. See Bridge events.

How to read these pages

Every page in this section shows the same demo flow: Start, a Welcome message, the gambit the page covers, then End. The gambit and its editor are highlighted, and the rest of the screen is dimmed.

Welcome

Core concepts

Guides

Developer

Every gambit type

What every gambit editor shares

How to read these pages

​Every gambit type

​What every gambit editor shares

​How to read these pages

​Related pages

Every gambit type

What every gambit editor shares

How to read these pages

Related pages