Widgets Overview

Distinct from the chat widget itself (the floating bubble), an inline widget is a UI component the agent renders directly within a conversation. Instead of replying with plain text, the agent shows a card, a form, a chart, a button — and the user can interact with it without leaving chat.

• Code — the visual layout, written using a built-in component library
• Schema — the data fields the widget expects from the agent and their types
• Default Example — initial field values when the widget first renders
• Named Examples — saved data presets for previewing different scenarios
• Functions — actions tied to interactive elements (button clicks, form submits)
• States — named wrappers whose visibility is controlled by conditions on current values

Widgets come in two flavours: Widget-Only actions (rendered with no API call) and Server Actions with Widgets (the widget renders the result of an API call).

The agent today can invoke a small set of built-in tools — navigation, calendar booking via Cal.com, lead capture via the built-in form. Custom inline widgets (the design described above) are tracked in the roadmap; ping us if you have a concrete use case to prioritize.