About the Agent 2 Agent connector

Integration Service connector for the Agent2Agent (A2A) protocol, used to call remote A2A agents from UiPath Maestro and to authenticate remote agents registered in Agent Gateway.

The Agent 2 Agent connector lets the UiPath Platform call remote agents that implement the Agent2Agent (A2A) protocol. A2A is an open protocol for communication between AI agents, so one connector can reach agents built on different platforms and hosted by different vendors.

Remarque :

The Agent 2 Agent connector is in preview.

Ways to use the connector

An Agent 2 Agent connection can call a remote agent in two ways:

Où	How the connection is used
MaestroTM	The Invoke an Agent activity calls the agent through the Start and wait for external agent task action. The agent takes part in the process like any other task, and its response is available to the steps that follow.
Passerelle d’agent	The connection authenticates calls to a remote agent registered in Agent Gateway > A2A Agents. All seven authentication types are supported, and Agent Gateway reads the credentials from the connection on every call. The registered agent can be used in Maestro flows, Maestro BPMN processes, and agents built with Agent Builder. For details, refer to Outbound (UiPath to external).

Authentification

Each connection points to one remote agent. The connector supports seven authentication types, so it can match the security scheme declared by the agent. For details, refer to Agent 2 Agent authentication.

Events

The connector uses the InvokeAgent Task Completed event to detect when a long-running agent task finishes. For details, refer to Agent 2 Agent events.

Activités

You can use the connection to enable the Invoke an Agent activity. For details, refer to About the Agent 2 Agent activities.

Remote agent requirements

The following requirements apply when you call the agent with the Invoke an Agent activity. For agents registered in Agent Gateway, refer to the Agent Gateway requirements instead.

The activity calls the agent over the HTTP+JSON (REST) transport of the A2A protocol. All paths are relative to the Service URL of the connection. The remote agent must meet the following requirements:

Prérequis	Détails (Details)
Agent Card	Served at /.well-known/agent-card.json without authentication. The connector reads it to validate the connection, to name the connection after the agent, and to list the agent skills.
HTTP+JSON transport	The agent accepts messages at POST /v1/message:send. Agents that only expose the JSON-RPC transport aren't supported.
Response envelope	The response to message:send is wrapped in a message object for an immediate reply, or in a task object for long-running work.
Task status endpoint	For long-running work, the agent returns the task at GET /v1/tasks:get?id={id}.
Task states	The task status.state uses the state values from the A2A specification. While the state is TASK_STATE_SUBMITTED, TASK_STATE_WORKING, or TASK_STATE_UNSPECIFIED, the task is considered in progress. Any other state completes the task.