Attach specialized agents to a coordinator so they can delegate tasks to each other during conversations.
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.
User │ ▼ ┌─────────────┐ │ Coordinator │ ← talks to the user, decides who to call └──────┬──────┘ │ ┌─────┼──────┐ ▼ ▼ ▼ ┌─────┐ ┌────┐ ┌─────┐ │ CRM │ │Jira│ │Slack│ ← specialists with scoped tools └─────┘ └────┘ └─────┘
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.
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.
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.
2. Build the coordinator. Go to the Instructions tab and write a system prompt that describes when to delegate:
You are a support triage agent. When a user asks about:- Sales pipeline or deal status: delegate to the Salesforce agent- Open tickets or project status: delegate to the Jira agent- Recent conversations or mentions: delegate to the Slack agentSynthesize results from specialists into a single answer.
3. Attach specialists in the coordinator’s General tab. Scroll to Multi-Agent, click Attach agents, and select the specialist agents from the panel.
4. Deploy the coordinator through any channel. The Channels tab shows all available deployment options: API, SDK, Chat, Slack, Webhook, Task, MCP, and A2A.
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.
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.
