Set up Agent-to-Agent (A2A)

Back to protocols channel

Supports the Google A2A protocol for inter-agent communication with task lifecycle management.

To configure an Agent-to-Agent (A2A) channel, go to Deployments > Channels > Agent-to-Agent (A2A) > + New and complete the following steps in order.

1. Set Up the Connection

   On the New Agent-to-Agent (A2A) Connection page, provide the following fields.

   Field	Description
   Display Name	A label for the connection. Up to 255 characters.
   Agent Endpoint Name	A system name for the A2A endpoint, for example booking-agent-a2a. Up to 255 characters.
   Environment	The deployment the connection binds to. Select an environment to follow its active deployment automatically, or leave the default to use the working copy.
   Provider Verification Strength	Controls how strictly the platform trusts the provider’s identity assertions for session continuity and linking. Weak is the default. Choose Strong only for channels/providers whose identity assertions you trust for stronger continuity and linking decisions.
   Initial Status	Active connections can be used immediately. Inactive connections stay saved but disabled until you activate them.

   Click Create.

Manage an existing Agent-to-Agent (A2A) channel

Open a channel from Deployments > Channels > Agent-to-Agent (A2A) shows three tabs: Overview, Configuration, and Deployment.

Overview

The Connection Summary shows these fields.

Field	Description
Status	for example: Active
Created	Timestamp the channel was created
Updated	Timestamp of the last change
Environment	for example: dev
Source Type	Channel Connection
Source ID	Unique channel identifier (UUID)

Setup Instructions shows the Agent Endpoint Name configured for this connection, with a copy icon to copy it into your integration code.

Configuration

General

Field	Description
Display Name	The connection’s label. Editable at any time.
Provider Verification Strength	Same setting described in Set up Agent-to-Agent (A2A) above.

Agent-to-Agent (A2A) Settings

Protocol channels are configured through the SDK integration — no additional settings are needed here.

Click Save Changes to apply changes.

Deployment

The Deployment tab shows these fields.

Field	Description
Agent Version	An Environment dropdown (for example: Development) that selects which deployed version handles incoming messages.
Active Deployment	Shows the bound deployment version and when it was deployed.

Click Save Changes after switching the environment/version.