A2A Agent Component

Estimated reading: 6 minutes

The A2A Agent component is a connector that lets a workflow communicate with, and get help from, another agent workflow that is exposed through the A2A Server in RobilityFlow. The component sends the input message to that workflow and returns its output for downstream steps.

Note: The A2A Agent component lists and runs only workflows that have been added to the A2A Server. To learn how to add a workflow, see A2A Server.

Coming soon: You’ll be able to use the A2A Agent component to call external A2A-compatible agents by entering their URL.

Roles

a. A2A Server (the provider): A separate workflow published with Serve as an A2A Agent enabled.
b. A2A Agent component (the caller): The block inside a workflow that sends a request to the A2A Server and receives the reply.

Key capabilities

a. Connect to internal agents: Any published A2A Agent workflow within the same RobilityFlow project and its environments can be selected and connected.
b. Preview external agents: The Agent Card (capabilities and details) of an external third-party A2A agent can be looked up and inspected using its URL.
c. Use as a step or an AI tool: The component can run as a fixed step in a workflow, or Tool Mode can be enabled so the main AI Agent decides on its own when to call the specialist agent.

How the A2A Agent component works in RobilityFlow

1. Connection modes: Internal mode connects to a published A2A Agent within the same RobilityFlow project. External mode connects to an external A2A-compatible agent.
2. Execution modes: As a workflow step, the component receives a message and exposes a Response output for use in subsequent steps. With Tool Mode enabled, an AI Agent can invoke the component whenever needed.
3. Message and response exchange: The component sends the input message to the connected agent and returns the response generated by that agent.
4. Capability reuse: Published agents can be reused across multiple workflows without recreating the same prompts, tools, or configurations.
5. Centralized maintenance: Changes made to a published agent are automatically available to every workflow that uses it, which reduces duplication and simplifies maintenance.

Example: A Customer Support workflow receives the question “Where is my package?” and needs live shipping data. Instead of building order-tracking logic inside the support flow, an A2A Agent component is added and connected to a separate Order Tracking Agent workflow. The component sends the order number to that agent, and the Order Tracking Agent replies with the live status.

Note: Sending live tasks to external third-party A2A agents is currently in development.

Connection Modes Overview

 Internal: Connects to a published A2A Agent flow within the same RobilityFlow project.
External: Retrieves and displays the Agent Card details of an external A2A-compatible agent. (Sending requests to external agents is currently under development.)

When to Use the A2A Agent Component

Use the A2A Agent component when a workflow needs to communicate with another Agent flow that has been published and configured with the A2A server, and reuse its capabilities without recreating the same functionality.

Prerequisites

Before configuring the component, ensure the following requirements are met:

Internal Mode: Both the target A2A Agent flow and the flow containing the A2A Agent component must belong to the same RobilityFlow project. The target flow must have Serve as an A2A Agent enabled and must be published.

Configuration

1. Connection Mode: Select the required mode to establish a connection with an A2A Agent: Internal or External.

2. Internal Mode: When Internal mode is selected, the component displays the available published A2A Agent flows within the same RobilityFlow project.

Parameter Description
Agent Select the published A2A Agent flow to connect to. The dropdown displays available A2A Agent flows within the same RobilityFlow project.

Note: Only published flows with Serve as an A2A Agent enabled are available for selection and execution.

Common Parameters

Parameter Description
Message* Enter the message to send to the selected A2A Agent. During supported Internal execution, the selected Agent processes the message and returns a response.

Outputs

Output Description
Response Returns the text response received from the selected internal A2A Agent. Connect this output to subsequent components for further processing.

Tool Mode

The A2A Agent component supports Tool Mode, which allows its functionality to be exposed as a callable tool to an AI Agent.

Purpose of Tool Mode

Tool Mode allows an AI Agent to use another A2A Agent’s capabilities whenever they are required to complete a task. Instead of executing the A2A Agent as a fixed step in the workflow, the calling AI Agent decides when to invoke it based on the task context and its instructions.

For example, an AI Agent handling customer queries may need order information to respond to a customer. It can invoke a separate A2A Agent that handles order tracking, pass the required message dynamically, and use the returned response to continue processing the query.

Execution Approach Behavior
Without Tool Mode The A2A Agent component executes sequentially as a fixed step in the configured workflow pipeline.
With Tool Mode The calling AI Agent autonomously decides when to invoke the A2A Agent as a tool and passes the message dynamically.

How Tool Mode Works

1. When Tool Mode is enabled, the A2A Agent component becomes available under Toolset → Agent Tools.
2. The calling AI Agent invokes the component when required and passes the message dynamically.
3. For Internal connections, the selected A2A Agent flow processes the message received from the calling AI Agent and returns its response for further processing.

Tool Mode Connection Options

Internal: Select the required published A2A Agent flow from the Agent The selected flow must belong to the same RobilityFlow project.
External agent execution through Tool Mode is currently under development.

Usage

Internal Mode

1. Add the A2A Agent component to the flow.
2. Select Internal as the mode.
3. Select the required published A2A Agent flow from the Agent dropdown.
4. Enter the message to send to the selected agent in the Message field.
5. Connect the Response output to the required downstream component.

During workflow execution, the component sends the configured message to the selected Agent flow and receives its response through the Response output.

Tool Mode

1. Add the A2A Agent component to the flow.
2. Enable Tool Mode.
3. Select the required connection mode (Internal to choose a published A2A Agent flow from the Agent dropdown)
4. Configure the calling AI Agent with the required language model and instructions.
5. Make the A2A Agent available to the calling AI Agent through Toolset → Agent Tools.
6. Run the flow—the calling AI Agent can invoke the A2A Agent and pass the required message dynamically.

Note: Internal connections can be only be used for Tool Mode execution.

Share this Doc

A2A Agent Component

Or copy link

CONTENTS
Robility Chatbot
Robility Assistant
Online