Skip to main content
Instead of building one agent with every connector and a massive system prompt, split the work across specialized agents. A coordinator agent talks to the user and delegates to specialists as needed.
Multi-agent vs. workflows: Multi-agent is for conversations where a user asks a question and agents collaborate to answer. Workflows are for backend automation triggered by events with no user in the loop.

​
Attach agents to enable delegation

Open any agent’s General tab and scroll to Multi-Agent. Click Attach agents to open a searchable panel listing every agent in your workspace. When you attach Agent B to Agent A, Agent B appears as a callable tool in Agent A’s tool list. The coordinator doesn’t need to know how to query Salesforce directly. It just calls the Salesforce specialist tool, which runs that agent with the delegated task and returns the result.

​
Set up a coordinator

1. Build specialists first. Each one gets its own system prompt, connectors, and knowledge base scoped to one domain. You’ll see them listed on the Agents page alongside your other agents.
Agents list page

The Agents page with Custom, Personal, and Supervised tabs. Both specialists (Chatbot, Starter Kit) are listed with their status and metadata.

2. Build the coordinator. Go to the Instructions tab and write a system prompt that describes when to delegate:
Agent Instructions tab with delegation prompt

The Instructions tab with a delegation prompt filled in: the coordinator knows when to call the Salesforce, Jira, and Slack specialists.

3. Attach specialists in the coordinator’s General tab. Scroll to Multi-Agent, click Attach agents, and select the specialist agents from the panel.
Attach agents panel

The Multi-Agent section expanded with the Attach agents panel. Workspace agents (here, Starter Kit) appear on the right, searchable.

4. Deploy the coordinator through any channel. The Channels tab shows all available deployment options: API, SDK, Chat, Slack, Webhook, Task, MCP, and A2A.
Agent Channels tab

The Channels tab with API, SDK, Chat, and more. Deploy the coordinator and users interact through any of these.

​
A2A protocol for cross-platform delegation

For agents that need to communicate across organizations, Xpander supports Google’s Agent2Agent (A2A) protocol. Enable it in the Channels tab to get an A2A URL and agent card.
A2A agent card

The A2A agent card modal with the agent's URL, name, and version.

External A2A-compatible agents can invoke your agent at that URL, and your agent can invoke theirs.
A2A vs. attached agents: Attached agents coordinate within your Xpander workspace. A2A is for cross-platform communication between agents on different systems.

​
When to use multi-agent

Use it when:
  • The coordinator’s system prompt is getting too long because it handles too many domains
  • Different domains need different tool sets, and combining them confuses the model
  • You want reusable specialists (one Salesforce agent attached to multiple coordinators)
A single agent is fine when the task stays within one domain. Don’t add multi-agent complexity unless the single-agent approach is struggling.

​
What’s next

Multi-Model Reasoning

Select the right model for each agent and task type.

Building Workflows

Backend automation on the visual canvas.