Skip to main content

​
Conversation Flow Components

Make complex agents easier to build, reuse, and maintain by packaging parts of your conversation into Components. A Component is a mini flow (a group of nodes) that you can reuse across agents and flows.

​
Why use Components?

  • Reuse: Build once, drop into many agents and flows.
  • Consistency: Keep behavior uniform across use cases (e.g., identity check).
  • Clean canvas: Hide detailed logic inside a focused sub-flow.
  • Faster iteration: Update a shared Component to improve every agent that uses it.

​
Where to find it

In the dashboard, open your agent’s builder:
  • Left sidebar → Components tab
  • Two sections:
    • Library Components: Account-level, shared across agents.
    • Agent Components: Local to the current agent.

​
Create a Component

You can create either a library (shared) Component or an agent-level (local) one. Both open in a dedicated editor tab.
  • Create a Component:
    1. In Components, click + Create.
    2. You’ll start with a “Begin” node, a basic conversation node and an “Exit Component” end node.
    3. Add nodes and connect edges to form your sub-flow.
    4. Set a start node by connecting the Begin tag to the first node.
    5. Make sure you linked “Exit” node correctly so that you won’t stuck at this component.
    6. You can switch back to the main agent by click the bottom navigation bar.
    7. You can rename the component by clicking the ”…” on the right of the Component name.
Notes:
  • Components cannot contain other Components; you add regular nodes inside a Component.
  • Available node types match your agent’s channel (voice vs chat).

​
Add a Component to your flow

  • From the Components tab, click a Component. A single Component node appears in your canvas.
  • Connect into the Component: link any node to the Component node.
  • Connect out of the Component: select the Component node and connect its outgoing edge to where the conversation should continue.
  • To edit what happens inside, click “Edit Component” (or open the Component tab) and modify its internal nodes.
  • You can modify the Component node name, which will also be reflected in the Component.
Tip: End nodes inside the Component hand control back to the main flow. Back on the main canvas, make sure the Component node’s outgoing edge points to the next step.

​
Shared vs Local Components

Shared (Library Components):
  • Account-level. Reusable across multiple agents.
  • Edits sync to every agent that uses it — great for universal steps.
Local (Agent Components):
  • Live only in the current agent.
  • Edits affect this agent only.
Convert Between Shared & Local:
  • Turn on “Save component to library” to create a shared (library) version.
  • Turn off syncing to convert the reference in your agent to a local copy that stops receiving updates.
Deletion Behavior:
  • Deleting a shared Component from the library downgrades linked instances in agents to local copies and stops sync updates (your agents keep working).
Publish Agent: When you publish an agent, we protect production behavior and keep draft work flexible:
  • Published version snapshots shared Components as local copies.
    • This prevents future library updates from changing already-published calls.
    • The published artifact is stable and won’t auto-update from the library.
  • Your latest editable draft stays linked to the shared Component.
    • You continue to benefit from library updates while iterating.
    • When you’re ready, publish again to roll out the latest changes.
Recommended workflow:
  • Build using Library Components → test → Publish → keep iterating in draft.
  • Publish again whenever you want to promote the latest shared/local changes to production.

​
Best practices

  • Keep Components focused: One clear job (e.g., “Collect Shipping Address”).
  • Name clearly: Use action + outcome (e.g., “Verify Identity”).
  • Design clean entry/exit: Always set a start node; include an end node to exit cleanly.
  • Reuse variables: Use dynamic variables to pass captured data back to the main flow.
  • Test in context: Open Test panel to simulate end-to-end behavior after inserting the Component.

​
FAQ

  • How do I update a shared Component used by many agents?
    • Under any agent, you can navigate to the component edit page. When you editing, changes apply everywhere it’s used.
  • Can I stop changes from affecting an agent?
    • Yes. In that agent, turn off syncing to convert its reference to a local copy.
  • What happens if I delete a library Component?
    • Agents keep a local copy; they stop syncing with the deleted library item.
  • Can I move a local Component into the library?
    • Yes. Use “Save component to library” to create a shared version and update references.
  • Can Components include tools/functions?
    • Yes. Components can include function nodes and use your configured tools. Tools behave the same as in the main flow.
    • The tools need to be defined within the component and will not be visible outside at agent level.
  • What if I did not link the Begin node in a component?
    • It tranisite to the next node based on the Component node edges.
  • What if I did not link the Exit node properly in a compoent?
    • It will stuck inside the component and cannot transite out.
⌘I