Agents
Specialized AI personas with an identity, goals, knowledge, and connected services - built in a guided builder, no workflow wiring required.
Agents
An Agent is a specialized AI persona with a clear job, a personality, knowledge sources, and (optionally) connected services it can act on. Where a Flow gives you a blank canvas and a workflow builder, an Agent is assembled from ready-made parts in a guided, section-by-section builder - persona in, working agent out.
Think of an Agent as:
- A customer concierge that greets visitors, answers product questions, and books demos.
- A domain advisor - for example, an HR assistant that explains your company policies and routes deeper questions to a person.
- A specialist that hands work off to Flows you've built, or that leads an App of several Agents and Flows.
Agents live under Agents in the sidebar's Assets group, which opens your Library filtered to Agents.
Agent or Flow?
| If you want to... | Build a(n)... |
|---|---|
| Ship a conversational agent quickly with sensible defaults | Agent |
| Design a precise, branching workflow with full control over every node | Flow (chatbot or form) |
| Capture structured input through fields, then run AI | Flow (form) |
| Combine a persona, voice, knowledge, and tools without wiring nodes | Agent |
The two compose: an Agent can be one piece of a bigger picture, and both can sit side by side in the same Suite.
Naming note - An Agent (this page) is a product you build and share. The Agent node is a step inside a Flow's workflow that calls an AI model. They're related but different things; see the glossary.
What an Agent is made of
- Identity - name, role, summary, persona, vibe, and an optional voice.
- Goals - what the Agent is for and what success looks like.
- Knowledge - the Knowledgebases it can read at runtime.
- Model - how much reasoning it uses, plus built-in tools like web search and image generation.
- Integrations - apps it can act in through Composio, and which of their actions it may use.
- Orchestration - Flows it can hand work off to.
- Guardrails - what it should never do, plus clarifying questions and approval rules.
Sharing Agents
A published Agent can be shared and embedded on its own, bundled with Flows into a Suite, or offered through a Portal (beta) with sign-in, plans, and metered credits.
When the page or link that opens the Agent already knows who the visitor is, it can pass those details in so the Agent starts the conversation informed. See Session context.