Skip to main content
A Component gambit holds a kit of native capabilities, called components. An AI Agent gambit linked to the kit can call any of them. In Workflow Mode, the gambit runs one component as a flow step instead.

​
When to use it

Use a Component gambit when the agent needs more than text: a form, a date picker, a meeting booking, a chart, or a file it reads or writes. You do not connect a toolkit or write a custom action. For a third-party action, use a tool gambit. See Enable and use actions.

​
Add a Component gambit

Component sits in the Connected group of the palette’s Tools tab, beside Knowledge Retrieval and CodeKit. Drag it onto the builder. You can also start from the AI Agent gambit. Select Manage tools in its Tools & Capabilities region, open Add tools, and pick Component under Built-in Tools. The new gambit is linked to the agent at once. See AI Agent gambit.

​
Components

The components fall into three groups. The book icon on a component opens its documentation inside the editor. Web Search is listed under Actions as Coming soon and cannot be added. For field and upload settings, see Form and File Upload. Two components need setup before they work. Data Extraction needs its fields, and Meeting Scheduler needs a scheduling integration. Enable the component, then select its gear icon to configure it. See Data Extraction and Book meetings with the Meeting Scheduler.

​
Agent mode

With Workflow Mode off, the editor shows a Components section. Its badge counts the components the kit includes. Link the gambit to an AI Agent gambit by dragging from its handle to the tool handle on the agent. The agent then reads each component’s name and description to decide when to call it.

​
Setup steps

The gear icon opens a setup dialog. For Data Extraction and Meeting Scheduler, the dialog is a series of steps that ends with Review. Other components open a single form. The dialog also offers these settings. Allow free text appears only for components that accept an answer.

​
Workflow Mode

The Workflow Mode switch sits at the top of the editor. With it on, the gambit runs one component as a flow step and continues on that component’s outcome routes. The Configure Component section holds: Interactions, displays, and File Generator can run as a flow step. The Component dropdown in Workflow Mode does not offer the other actions. If one was already selected, an error under the dropdown asks you to pick another component. A Messages section appears once a component is picked. It holds the bubbles sent before the component.

​
Outcome routes

Each outcome of the component gets its own row in the routing section, with a dropdown that picks the target gambit. An outcome with no target shows Continue and moves to the next step. The gambit shows one handle per outcome. Free text appears only while Allow free text is on.

​
Read the result

Set the gambit’s Variable name to read its result in later steps. The outcome is stored as {{api.gambit_variable.component_kind.outcome}}, for example {{api.booking.meeting_scheduler.outcome}}. The editor lists the other result fields for the selected component under the Component dropdown.

​
Form

In Workflow Mode, pick Form and fill its Inputs. In agent mode, describe the fields and rules in the agent’s instructions so it supplies them when calling Form. In Workflow Mode, the Docs button opens the component’s reference in the editor. A form accepts title, submitLabel, and submissionTitle for the heading, submit button, and heading after submission. Its fields list defines each question: Email, phone, number, date, and select fields validate their answers before submission completes. Protection does not make the original value available everywhere: Mask mode supplies a reusable reference to supported tools, while Redact mode does not retain the original. For a complete workflow, follow Collect and reuse form answers. The example uses a gambit with Variable set to intake and fields keyed topic and details. Later steps can read these results: Use the topic reference in a condition to branch, or pass the answer references into a later tool step. See Flow control and branching and Use variables.

​
File Upload

In Workflow Mode, pick File Upload and set its Inputs. In agent mode, tell the agent which file types and size limit to request. For receipts, set label to Upload your receipts, add .pdf and image/* to accept, set maxSizeMb to 5, and turn on multiple if several receipts are needed. Connect Uploaded to the next step, then test with an allowed file, a disallowed type, and a file above 5 MB. The end user confirms the selected files to submit them. File Upload collects files. It does not read their contents. Link a File Reader component to an AI Agent gambit when the agent needs to inspect them. See File Reader.

​
Data Extraction

Data Extraction collects details from the end user as separate typed fields, such as an address or an order description. Each field is its own input, so the agent asks for a required field before it calls the component. Enable Data Extraction, then select its gear icon to open the Fields step. Add up to 30 fields.

​
Other channels

Only the web widget can show a component that waits for an answer. On another channel, such as WhatsApp, that component ends with an error instead of showing its card. Verification Code is the exception and still sends its code. In Workflow Mode, Meeting Scheduler follows its configured Error route. Other interactions have no Error route in the editor. The flow continues through the gambit’s next connection. Do not read a submitted answer on that path, because no card was answered.