Let an AI agent offer a workflow

An AI agent can offer a structured workflow during a conversation and continue answering when it finishes. The visitor must confirm before it starts. For example, a car sales agent can ask whether the visitor has a trade-in, offer a car-details workflow when they say yes, then use the collected details in its next reply.

Saying “yes, I have a trade-in” does not start the workflow. The visitor starts it using the offer's Start button, or declines with Not now.

Build and attach the workflow

Tenant owners and tenant admins manage these attachments for their own agents.

Open Chat → Workflows and build an active workflow with one start node. Use messages, questions, forms, typed inputs and deterministic conditions to collect the information you need.
Give every path an End Conversation node. Within a called workflow, this node returns control to the AI agent; it does not end the surrounding conversation. In an ordinary workflow it still ends the conversation.
Save the workflow. Open AI → AI agents, save your agent if it is new, then open Edit.
Under Callable workflows, below the agent's settings, select the Workflow and enter a unique Callable key, such as trade_in.
Enter a Visitor-facing title, such as “Trade-in details”, and explain When should the agent offer this workflow? For example: “Offer this after the visitor says they have a car to trade in. Explain that it collects the car details and wait for their confirmation.” To get a starting point, click Generate with AI. It drafts this text from the agent's instructions and the selected workflow's steps and replaces what is in the box. Review and edit it before saving.
Check Fields returned to the agent. Selecting a workflow fills it with the field names of the workflow's questions, inputs and form fields, such as vehicle_make, vehicle_model, year. Each name is the node name (or form field label) in lowercase, with spaces and symbols replaced by _. Remove any field the agent should not receive; only listed fields are returned.
If the workflow needs starting values, configure the optional Input schema for those inputs. Undeclared inputs are rejected.
Click Save workflow attachment. The attachment appears in the list as Not published: the agent cannot offer it yet. Click Publish agent in the same section (or Publish on the AI agents page). The badge changes to Published.
Try the offer in Chat test, including confirmation, declining and returning to the AI conversation.

If the agent doesn't offer the workflow, open the conversation under Chat → Conversations and click Show AI Details on an AI reply. When the workflow is available to the agent, its system prompt includes a Workflow offers line listing it. If that line is missing, the attachment isn't published for the agent version that answered: check the agent name and version shown there. Also make sure the agent's instructions don't tell it to collect the same details itself.

What visitors experience

The AI offers the workflow when it matches the conversation. Only one workflow can run at a time. After confirmation, the visitor answers its questions. When the workflow reaches its end, control returns to the AI with the workflow's outcome and collected information.

Reloading the widget preserves the running workflow's progress. Declining suppresses repeated offers for the same callable key and version. Offers can expire, so an old button may no longer start a workflow.

If a staff member takes over, pending offers expire and a running workflow pauses. After the chat returns to AI control, the workflow can continue from its collected state with the visitor's next input.

Publish changes and stop new starts

Publishing captures the attached workflow's definition with the agent version. Editing the original workflow does not change an already published attachment: save the attachment again and republish the agent to capture the new definition. Existing calls keep their captured definition.

To change an attachment, click Edit next to it. Its settings load into the form; the callable key can't be changed. Save, then publish the agent again.

Use Disable on an attachment to prevent new starts across published versions. This does not replace the definition of an already running call.

Callable workflows currently exclude file uploads, appointment booking, human-handoff nodes, nested AI chat and AI-based conditions. Use the regular workflow builder for those paths. A callable workflow must have a return path from every node and cannot connect onward from its return nodes. Save workflow attachment checks these rules and tells you which step breaks them, so you can fix the workflow before publishing.

Translations

The offer title and the workflow's messages and labels are translated automatically into the visitor's language when the agent offers the workflow, if they have no current translation. Publishing the agent also prepares them in the languages your chats already use. To use your own wording, open the attachment's Title translations and Workflow step translations panels, choose a language in Translate to:, then edit and approve it. The instructions for when to offer the workflow and its internal field names are never translated.