# A2A Connector - Full Documentation

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# Using Anypoint Code Builder to Configure A2A Connector 2.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Cloud IDE (Beta) is scheduled for retirement on August 31, 2026. August 30, 2026 is the last day you
can access Cloud IDE (Beta). Download your projects to work from Desktop IDE. Learn more in
[Migrate a Project from Cloud IDE to Desktop IDE](../../anypoint-code-builder/int-import-mule-project#migrate-cloud-to-desktop).

To use Anypoint Code Builder to configure a connector or module, create a basic integration project
in Anypoint Code Builder, add connectors and other components to your Mule application to process
your business logic, and configure the attributes.

## Before You Begin

Before creating an integration project, you must:

- [Set up and access the Anypoint Code Builder web or desktop IDE](../../anypoint-code-builder/start-acb)
- Have credentials to access the connector’s API
- Ensure that the Visual Studio Code Extension Pack for Java is installed.

To use this connector, you must be familiar with:

- The connector’s API
- Anypoint Connectors
- Mule runtime engine (Mule)

## Create a New Integration Project

To create a new integration project:

1.  In the activity bar of the IDE, click the
    ![Anypoint Code Builder icon](../../connectors/_images/acb-icon-ms-logo.png) (**Anypoint Code
    Builder**) icon.
2.  From **Quick Actions**, click **Develop an Integration**:

    ![Develop an Integration link highlighted in the Getting started section](../../anypoint-code-builder/_images/develop-integration-option-mat.png)

3.  Complete the following in the **Develop an Integration** form:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Attribute</th><th>Value</th></tr></thead><tbody><tr><td><div><div><p><strong>Project Name</strong></p></div></div></td><td><div><div><p>Unique name for your project.</p></div><div><p>This name is used as the title and name of the integration project file. For example, if the project name is "Salesforce Integration," the project file name is <code>salesforce-integration</code>.</p></div></div></td></tr><tr><td><div><div><p><strong>Project Location</strong></p></div></div></td><td><div><div><p>Your home directory or another directory you create. Click <strong>Browse</strong> to select a different directory for the integration project.</p></div><div><p>Don’t create the project within another project directory.</p></div><div><p>See <a href="../../anypoint-code-builder/start-add-folders">Adding Folders to Your Home Directory</a>.</p></div></div></td></tr></tbody></table>

4.  Select the type of project to create by selecting either the **Empty Project** or **Template or
    Example** card.
5.  Select the **Mule runtime** and **Java Version** for your app.
6.  Click **Create Project**.

## Add the Connector to Your Integration Project

Anypoint Connectors provide operations for retrieving, modifying, and sending data to and from
systems.

In addition to the
[built-in connectors](../../anypoint-code-builder/acb-reference#builtin-connectors) that Anypoint
Code Builder provides, you can download many other connectors from Anypoint Exchange.

To import a connector from Exchange and add it to your configuration:

1.  In the Explorer view, open the configuration XML file for your project, such as
    `my-project-name.xml`.
2.  Click the
    ![Show Mule graphical mode icon](../../anypoint-code-builder/_images/icon-tree-view.png) (**Show
    Mule graphical mode**) icon in the activity bar to open the canvas UI if it doesn’t open
    automatically.
3.  Add the connector the same way you added other components from the canvas UI:
    1.  In the canvas UI, click the
        ![Add component icon](../../anypoint-code-builder/_images/icon-plus.png) (**Add component**)
        icon.
    2.  In the **Add Component** panel, click **Connectors**.
    3.  Click the connector name and then click the operation to add, such as **Publish**:

        ![Add Publish operation from Anypoint MQ Connector](../../anypoint-code-builder/_images/int-add-connector-operation.png)

        If the connector is not available locally, click the
        ![Search in Exchange icon](../../anypoint-code-builder/_images/icon-search-exchange.png)
        (**Search in Exchange**) toggle:

        ![Search in Exchange toggle](../../anypoint-code-builder/_images/int-connector-search-exchange.png)

        <table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Search locally</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Search in Exchange</td></tr></tbody></table>

    4.  Select the connector to add to your project.
    5.  Select the operation from the **Add Component** panel.

Adding a connector to an integration project does not make that connector available to other
projects in your Anypoint Code Builder workspace.

## Configure the Source For the Flow

A source (trigger) starts the flow when specified conditions are met. You can configure these
sources for A2A Connector:

- **A2A Server - Task Authorizer Listener**

  A2A Server authorization listener that gates auth-required operations before they execute. It runs
  for both the JSON-RPC and HTTP+JSON transport bindings. If the flow completes successfully, the
  request is authorized. If the flow raises an error, the request is denied and an
  `A2A:UNAUTHORIZED` error is returned to the caller. The current operation name is available on
  `attributes.operationName` so a single listener can gate multiple operations. This source
  supersedes the **A2A Server - Authorization Listener** from earlier versions.

- **A2A Server - Task Listener**

  Listens for and receives incoming A2A protocol-compliant requests from other AI agents, enabling
  the Mule-based agent to act as an A2A server and respond to tasks. This unified source serves
  blocking, non-blocking, and streaming `SendMessage` requests over both transport bindings; there
  is no separate stream listener.

- **A2A Server - On Async Request Listener**

  Server-side listener that customizes the initial `Task` returned for streaming
  (`SendStreamingMessage`) and non-blocking (`SendMessage` with `returnImmediately=true`) requests.
  Use this source in conjunction with **A2A Server - Task Listener**.

- **A2A Server - On Push Notification Set Listener**

  Validates the push notification configuration before routing the request to the **A2A Server -
  Task Listener** source.

For example, to configure an **A2A Server - Task Listener** source, follow these steps:

1.  Click the **A2A Server - Task Listener** component on the canvas.
2.  (Optional) Click the edit icon to change the name of the **A2A Server - Task Listener**
    component.
3.  In the **General** tab, configure the connection for the A2A Server. See
    [A2A Server Configuration](a2a-connector-reference#Server).
4.  Select the **Advanced** tab to configure these attributes:

    <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Attribute</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Primary node only</p></td><td><p>Select this option to execute the <strong>A2A Server - Task Listener</strong> source on the primary node only when running in a cluster.</p></td><td><p>No</p></td></tr><tr><td><p>Redelivery policy</p></td><td><p>Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.</p></td><td><p>No</p></td></tr><tr><td><p>Reconnection strategy</p></td><td><p>Retry strategy in case of connectivity errors. When an operation in a Mule application fails to connect to an external server, the default behavior is for the operation to fail immediately and return a connectivity error. You can modify the default behavior by configuring the reconnection strategy for the operation.</p></td><td><p>No</p></td></tr></tbody></table>

## Add Components to Your Project

Add components to your integration project to build a flow:

1.  In the **Explorer** view, open the XML file for your project, such as `my-project-name.xml`.
2.  Select **Build a Flow** from the start card to create an empty flow:

    ![Anypoint Code Builder canvas with starting cards with the options to start from scratch, build a flow, or build a subflow](../../connectors/_images/acb-build-flow.png)

3.  Change the name of the flow:
    1.  Click **Flow**.
    2.  Click the edit icon.

        ![Arrow pointing to the flow name edit pencil icon](../../connectors/_images/acb-change-flow-name.png)

    3.  Enter the flow name, and click the checkmark.
    4.  In the canvas UI, click the
        ![Add component icon](../../anypoint-code-builder/_images/icon-plus.png) (**Add component**)
        icon.
    5.  In the **Add Component** panel, search for and select your component from the results. The
        following example shows the **Listener** component from the **HTTP** search results:

        ![Listener component highlighted in the Add Component section](../../anypoint-code-builder/_images/main-tutorial-add-first-listener.png)

        The configuration XML file now includes the XML for the HTTP Listener into the `<flow/>`
        element, for example:

        ```XML
        <flow name="getFlights" >
          <http:listener path="" config-ref="" doc:name="Listener" doc:id="ojzfry" />
        </flow>
        ```

## Configure the Component Attributes

After you add components to your integration project, configure the attributes in the component UI,
or configure the attributes directly in the XML code editor.

Connector XML tags start with a namespace followed by an operation, following the syntax
`namespace:operation`, such as `<db:select/>` for a **Select** operation in Anypoint Connector for
Database (Database Connector).

You can use autocomplete from an expression (**fx**) field for a component to select DataWeave
functions from the Core module and other values accepted in this field.

## Create a New Configuration XML File

Anypoint Code Builder creates the initial Mule configuration XML file in `src/main/mule` within the
Mule project. This file contains global configurations and flow structures.

You can create additional configuration files, for example, to store global configurations.

To create a new XML configuration file:

1.  In the Explorer view, right-click the **mule** folder (`src/main/mule`) and select **New File**.

    Alternatively, use the menu.

    Show me how

    Select the `mule` folder, and then:
    - In the desktop IDE, select **File** > **New Mule Configuration File**.
    - In the cloud IDE, click the ![](../../anypoint-code-builder/_images/icon-menu.png) (menu)
      icon, and select **File** > **New File**.

2.  Enter a name for the new file with the `.xml` extension.
3.  In the Editor view for the new file, press Ctrl+Space to display available options.
4.  Select **Empty mule configuration**:

    ![New Mule configuration option in auto-correct](../../anypoint-code-builder/_images/int-new-mule-config.png)

    This command adds the following code to the file:

    ```xml
    <?xml version="1.0" encoding="UTF-8"?>
    <mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
        xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
        http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

    </mule>
    ```

## Debug the App

Debug your Mule application using the embedded debugger in Anypoint Code Builder.

See [Debugging Mule Applications](../../anypoint-code-builder/int-debug-mule-apps).

## See Also

- [Anypoint Code Builder Overview](../../anypoint-code-builder/)
- [Creating Integrations](../../anypoint-code-builder/int-create-integrations)
- [Using Anypoint Code Builder to Configure a Connector](../../connectors/introduction/intro-config-use-acb)
- [Anypoint Code Builder Components and Commands Reference](../../anypoint-code-builder/acb-reference)
- [Defining and Securing Properties for a Mule Application](../../anypoint-code-builder/int-create-secure-configs)
- [Triggering Flows in Your Development Environment](../../anypoint-code-builder/int-trigger-flows)
- [Configuring Components](../../anypoint-code-builder/int-configure-components)
- [Debugging Mule Applications](../../anypoint-code-builder/int-debug-mule-apps)
- [Salesforce Help](https://help.salesforce.com)
- [Deployment Options](../../runtime-manager/deployment-strategies)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# A2A Connector 2.0 - Examples

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

A2A Connector 2.0 speaks A2A protocol 1.0.0. An A2A server exposes an agent to the world through an
agent card and one or more transport bindings. Client A2A agents use the card to determine:

- When to use the agent (based on description, skills, and capabilities)
- Where to contact the agent (based on `supportedInterfaces[].url` and `protocolBinding`)
- Whether the endpoint is multi-tenant (based on `supportedInterfaces[].tenant`)

## Configure an A2A Server

An A2A server serves each agent over one or more transport bindings. The two supported bindings are
`JSONRPC` and `HTTP_JSON` (gRPC is out of scope for this release). Every binding you register in the
DSL must be advertised by the agent card, and every card entry must be registered in the DSL.
Startup validates this bijection.

```xml
<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config">
    <http:listener-connection host="0.0.0.0" port="8081" />
</http:listener-config>

<a2a:server-config name="A2A_Server_config" doc:name="A2A Server config">
    <a2a:connection listenerConfig="HTTP_Listener_config" agentPath="/stock-summarizer">
        <a2a:interfaces>
            <a2a:interface protocol="JSONRPC"   path="/jsonrpc"/>
            <a2a:interface protocol="HTTP_JSON" path="/rest"/>
        </a2a:interfaces>
    </a2a:connection>
    <a2a:agent-card file="${app.home}/agent-card.json" />
</a2a:server-config>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td><code>a2a:server-config</code> defines the A2A server configuration.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td><code>a2a:connection</code> binds the server to an HTTP listener and specifies the base <code>agentPath</code>. The agent card is served at <code>{agentPath}/.well-known/agent-card.json</code>, and each transport binding is registered under <code>{agentPath}{interface.path}</code>.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td><code>a2a:interfaces</code> declares one or more transport bindings, each with a <code>protocol</code> (<code>JSONRPC</code> or <code>HTTP_JSON</code>) and a <code>path</code> segment. There is no <code>tenant</code> attribute on <code>&lt;a2a:interface&gt;</code>. Tenant identities live only in the agent card.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td><code>a2a:agent-card</code> points to the JSON file that describes the agent. On CloudHub, use <code>${app.home}/agent-card.json</code>.</td></tr></tbody></table>

If you register an `<a2a:interface>` whose `(protocol, path)` is not advertised in the card (or vice
versa), startup fails with an error naming the offending entry, so misconfiguration surfaces at
deployment time instead of as runtime 404s.

## Choose a Transport: JSON-RPC vs HTTP+JSON

The two bindings deliver the same agent over different wire shapes. A client that talks A2A can use
either.

- JSON-RPC 2.0 (protocol `JSONRPC`): Every operation is a `POST` to a single URL with a JSON-RPC
  envelope. The `method` field identifies the operation (`SendMessage`, `SendStreamingMessage`,
  `GetTask`, `CancelTask`, `SubscribeToTask`, `ListTasks`, `CreateTaskPushNotificationConfig`,
  `GetTaskPushNotificationConfig`, `ListTaskPushNotificationConfigs`,
  `DeleteTaskPushNotificationConfig`).
- HTTP+JSON (protocol `HTTP_JSON`): Each operation has its own URL and HTTP method:
  `POST /message:send`, `POST /message:stream` (SSE), `GET /tasks/{id}`, `GET /tasks`,
  `POST /tasks/{id}:cancel`, `POST /tasks/{id}:subscribe` (SSE),
  `POST /tasks/{id}/pushNotificationConfigs`, `GET /tasks/{id}/pushNotificationConfigs/{configId}`,
  `GET /tasks/{id}/pushNotificationConfigs`,
  `DELETE /tasks/{id}/pushNotificationConfigs/{configId}`.

The connector’s server-side flow logic is transport-agnostic. The same **A2A Server - Task
Listener** flow serves both. You only need to advertise the bindings you actually register.

## A2A Request Format

The minimum required JSON-RPC 2.0 request for `SendMessage`:

```json
{
  "jsonrpc": "2.0",
  "method": "SendMessage",
  "id": "test-001",
  "params": {
    "message": {
      "messageId": "550e8400-e29b-41d4-a716-446655440000",
      "role": "ROLE_USER",
      "parts": [{ "text": "Hello, this is my message" }]
    }
  }
}
```

The equivalent HTTP+JSON request is `POST {agentPath}{interface.path}/message:send` with only the
`params` body:

```json
{
  "message": {
    "messageId": "550e8400-e29b-41d4-a716-446655440000",
    "role": "ROLE_USER",
    "parts": [{ "text": "Hello, this is my message" }]
  }
}
```

You can use metadata types in Anypoint Studio to ensure your payloads conform to the A2A schema. The
connector ships JSON schema definitions for `MessageSendParams`, `Task`, `TaskStatusUpdateEvent`,
`TaskArtifactUpdateEvent`, `ListTasksParams`, and other A2A objects.

> [!NOTE] The wire-level JSON-RPC method names in A2A 1.0.0 are PascalCase (`SendMessage`,
> `GetTask`, and so on), not the slash-form (`message/send`, `tasks/get`) used in the older 0.3.0
> spec. Clients written against 0.3.0 must update their method strings.

## Write a Task Listener

The **A2A Server - Task Listener** source is now unified. The same flow serves blocking
`SendMessage`, non-blocking `SendMessage` (with `returnImmediately=true`), and
`SendStreamingMessage` over both JSON-RPC and HTTP+JSON. There is no separate **A2A Server - On Task
Stream Listener** element anymore.

```xml
<flow name="a2aTaskFlow">
    <a2a:task-listener doc:name="Task Listener" config-ref="A2A_Server_config" />

    <set-variable variableName="user_prompt" value="#[payload.message.parts[0].text]" />
    <set-variable variableName="taskId"      value="#[attributes.taskId]" />
    <set-variable variableName="contextId"   value="#[attributes.contextId]" />
    <set-variable variableName="tenant"      value="#[attributes.tenant]" />
</flow>
```

Task and context identifiers are surfaced on `attributes` (`attributes.taskId`,
`attributes.contextId`), along with the resolved tenant (`attributes.tenant`, which is an empty
string when the client did not send one). Use these for direct addressing rather than deriving them
from the request body.

### Example Response

The **A2A Server - Task Listener** flow does not return a `Task` payload directly. It emits one or
more update events via the **A2A Server - Update Task Status** and **A2A Server - Update Task
Artifact** operations, and the connector materializes the client response automatically from the
persisted task state after a terminal or interrupted status update is dispatched.

Each update event follows the A2A `StreamResponse` shape: a single root key (`statusUpdate` for
status events, `artifactUpdate` for artifact events) whose value carries `taskId`, `contextId`, and
the update body. A typical successful sequence is an intermediate `statusUpdate` (working), an
`artifactUpdate` for the result, and a final `statusUpdate` in a terminal state:

```xml
<!-- 1. Progress update — non-terminal state; does not complete the response. -->
<a2a:update-task-status doc:name="Working" config-ref="A2A_Server_config">
    <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    status: {
      state: "TASK_STATE_WORKING",
      message: {
        messageId: uuid(),
        role: "ROLE_AGENT",
        parts: [{ text: "Working on it..." }]
      }
    }
  }
}]]]></a2a:status-content>
</a2a:update-task-status>

<!-- 2. Artifact carrying the answer. -->
<a2a:update-task-artifact doc:name="Answer" config-ref="A2A_Server_config">
    <a2a:artifact-content><![CDATA[#[%dw 2.0
output application/json
---
{
  artifactUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    artifact: {
      artifactId: "artifact-" ++ vars.taskId,
      name: "answer",
      parts: [{ text: "Task completed successfully." }]
    }
  }
}]]]></a2a:artifact-content>
</a2a:update-task-artifact>

<!-- 3. Terminal status — this event triggers response emission. -->
<a2a:update-task-status doc:name="Completed" config-ref="A2A_Server_config">
    <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    status: { state: "TASK_STATE_COMPLETED" }
  }
}]]]></a2a:status-content>
</a2a:update-task-status>
```

When the terminal (or interrupted) `statusUpdate` is dispatched, the connector materializes the
current `Task` from the task store, carrying every `artifactUpdate` and message history persisted
along the way, and delivers it to the caller:

- Blocking `SendMessage`: Returned synchronously as a `StreamResponse` with a `task` root key.
- `SendStreamingMessage` and `SubscribeToTask`: The same terminal event also closes the SSE stream.
  The exception is `TASK_STATE_AUTH_REQUIRED`, which does not close the stream so the agent can
  resolve auth out of band.

Terminal states are `TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`, `TASK_STATE_CANCELED`, and
`TASK_STATE_REJECTED`. Interrupted states are `TASK_STATE_INPUT_REQUIRED` and
`TASK_STATE_AUTH_REQUIRED`.

## Mule App Example

This example shows a financial A2A agent that answers queries about US companies by combining an
MCP-tool lookup with an LLM prompt.

```xml
<flow name="financeAgentFlow">
    <a2a:task-listener doc:name="Task Listener" config-ref="A2A_Server_config" /> #(1)
    <logger level="INFO" message="Triggering MCP Tools"/>                          #(2)
    <set-variable value="#[attributes.taskId]"     variableName="task_id"/>        #(3)
    <set-variable value="#[attributes.contextId]"  variableName="context_id"/>     #(4)
    <set-variable value="#[payload.message.parts[0].text]" variableName="user_prompt"/> #(5)

    <ms-inference:mcp-tools-native-template config-ref="MuleSoft_Inference_config"> #(6)
        <ms-inference:template><![CDATA[You are a specialized assistant that performs financial analysis based on stock market data using stock market symbols]]></ms-inference:template>
        <ms-inference:instructions><![CDATA[Your sole purpose is to use the tools "get_company_symbol" and "get_company_financials" to answer financial questions about US based companies. Response Format: JSON with { message, status, sentiment, reasoning }.]]></ms-inference:instructions>
        <ms-inference:data><![CDATA[#[vars.user_prompt]]]></ms-inference:data>
    </ms-inference:mcp-tools-native-template>

    <set-variable value="#[payload.response]" variableName="mcp_tooling_results"/>  #(7)

    <ms-inference:agent-define-prompt-template config-ref="MuleSoft_Inference_config"> #(8)
        <ms-inference:template><![CDATA[#["You are a specialized assistant for financial analysis. Use the following context to answer.
Context: $(vars.mcp_tooling_results)"]]]></ms-inference:template>
        <ms-inference:instructions><![CDATA[Response Format: JSON with { message, status, sentiment, reasoning }.]]></ms-inference:instructions>
        <ms-inference:data><![CDATA[#[vars.user_prompt]]]></ms-inference:data>
    </ms-inference:agent-define-prompt-template>

    <a2a:update-task-artifact doc:name="Answer Artifact" config-ref="A2A_Server_config">   #(9)
        <a2a:artifact-content><![CDATA[#[%dw 2.0
output application/json
---
{
  artifactUpdate: {
    taskId: vars.task_id,
    contextId: vars.context_id,
    artifact: {
      artifactId: "artifact-" ++ vars.task_id,
      name: "Answer",
      parts: [{ text: payload.response }]
    }
  }
}]]]></a2a:artifact-content>
    </a2a:update-task-artifact>

    <a2a:update-task-status doc:name="Completed (Final)" config-ref="A2A_Server_config">   #(10)
        <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: vars.task_id,
    contextId: vars.context_id,
    status: { state: "TASK_STATE_COMPLETED" }
  }
}]]]></a2a:status-content>
    </a2a:update-task-status>
</flow>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>The <strong>A2A Server - Task Listener</strong> waits for an incoming <code>SendMessage</code> (blocking, non-blocking, or streaming) from any registered transport binding.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>The <code>logger</code> component records a diagnostic entry.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td><code>attributes.taskId</code> is captured to <code>task_id</code>. Prefer <code>attributes</code> over deriving IDs from <code>payload</code>. The attribute is authoritative for both JSON-RPC and HTTP+JSON.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td><code>attributes.contextId</code> is captured to <code>context_id</code>. Reuse it in subsequent event payloads so the client can correlate.</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td>The user prompt is extracted from <code>payload.message.parts[0].text</code>.</td></tr><tr><td><i data-value="6"></i><b>6</b></td><td>The <code>ms-inference:mcp-tools-native-template</code> calls the LLM with the tools configured for financial analysis.</td></tr><tr><td><i data-value="7"></i><b>7</b></td><td>The tool-augmented response is captured to <code>mcp_tooling_results</code>.</td></tr><tr><td><i data-value="8"></i><b>8</b></td><td>A second inference pass converts the tool output into the user-facing JSON structure.</td></tr><tr><td><i data-value="9"></i><b>9</b></td><td>The <strong>A2A Server - Update Task Artifact</strong> operation emits the LLM answer as an artifact event. The DataWeave payload uses the <code>artifactUpdate</code> root key required by the A2A <code>StreamResponse</code> shape. Artifact events do not close the response by themselves. They are streamed to SSE subscribers and merged into the persisted <code>Task</code>.</td></tr><tr><td><i data-value="10"></i><b>10</b></td><td>The <strong>A2A Server - Update Task Status</strong> operation with <code>state: "TASK_STATE_COMPLETED"</code> is the terminal event that triggers the connector to materialize the current <code>Task</code> from the store and deliver it to the caller (or close the SSE stream). Emit exactly one terminal or interrupted status per invocation.</td></tr></tbody></table>

## Configure the A2A Client to Call Other A2A Agents

The client connection provider is transport-specific. Choose the one that matches the target agent
card’s `supportedInterfaces[].protocolBinding`.

```xml
<!-- JSON-RPC target -->
<a2a:client-config name="A2A_Client_JsonRpc">
    <a2a:jsonrpc-client-connection agentUrl="https://fqdn.com/stock-summarizer" />
</a2a:client-config>

<!-- HTTP+JSON target -->
<a2a:client-config name="A2A_Client_HttpJson">
    <a2a:http-json-client-connection agentUrl="https://fqdn.com/stock-summarizer" />
</a2a:client-config>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>The config parameter is now <code>agentUrl</code> (previously <code>serverUrl</code>). The connector discovers the target agent via <code>{agentUrl}/.well-known/agent-card.json</code>.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Every outbound request automatically sends <code>A2A-Version: 1.0</code> as a default header, unless overridden via <code>&lt;a2a:default-headers&gt;</code>. Agent-card discovery (connect-time and the <strong>A2A Client - Get Card</strong> operation) is exempt from the header.</td></tr></tbody></table>

A minimal flow that listens for an A2A task and forwards it to a remote agent:

```xml
<flow name="forwardToRemoteAgentFlow">
    <a2a:task-listener config-ref="A2A_Server_config"/>
    <a2a:send-message config-ref="A2A_Client_JsonRpc">
        <a2a:message><![CDATA[#[payload]]]></a2a:message>
    </a2a:send-message>
</flow>
```

## Non-Blocking Send Message (`returnImmediately=true`)

Clients that don’t want to hold a connection open for the entire compute can send
`configuration.returnImmediately=true`. The server acknowledges immediately with an initial `Task`
(typically in `TASK_STATE_SUBMITTED` or `TASK_STATE_WORKING`) and continues processing
asynchronously. The client can later call the **A2A Client - Subscribe To Task** operation to stream
events for the ongoing task.

To customize the initial `Task` response, add an **A2A Server - On Async Request Listener** flow to
the same server config:

```xml
<flow name="asyncInitialTaskFlow">
    <a2a:on-async-request-listener doc:name="On Async Request Listener" config-ref="A2A_Server_config"/>

    <ee:transform doc:name="Author Initial Task">
        <ee:message>
            <ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{
  task: {
    id: attributes.taskId,
    contextId: attributes.contextId,
    status: { state: "TASK_STATE_SUBMITTED" }
  }
}]]></ee:set-payload>
        </ee:message>
    </ee:transform>
</flow>

<flow name="asyncComputeFlow">
    <a2a:task-listener config-ref="A2A_Server_config"/>
    <!-- Long-running compute; emit progress via <a2a:update-task-status> / <a2a:update-task-artifact>. -->
</flow>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>The <strong>A2A Server - On Async Request Listener</strong> runs for <code>SendStreamingMessage</code> requests and for <code>SendMessage</code> with <code>returnImmediately=true</code>. It receives the incoming <code>MessageSendParams</code> as payload and <code>attributes.taskId</code> / <code>attributes.contextId</code> / <code>attributes.tenant</code> / request headers on attributes.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>The flow must return the initial task as a <code>StreamResponse</code> with a <code>task</code> root key (matching the same envelope shape used for <code>statusUpdate</code> and <code>artifactUpdate</code> events). Missing or unparseable output is rejected with <code>A2A:INTERNAL_ERROR</code>.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>The <code>Task</code> under <code>task</code> can already be in a terminal state (<code>TASK_STATE_COMPLETED</code>, <code>TASK_STATE_FAILED</code>, <code>TASK_STATE_CANCELED</code>, or <code>TASK_STATE_REJECTED</code>) or an interrupted state (<code>TASK_STATE_INPUT_REQUIRED</code> or <code>TASK_STATE_AUTH_REQUIRED</code>) to short-circuit the request. In that case, the <strong>A2A Server - Task Listener</strong> compute flow is not invoked.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>The flow can raise a Mule error to reject the request outright. The raised error type propagates on the wire.</td></tr></tbody></table>

> [!NOTE] Concurrency and terminal-state safety on `SendMessage`:
>
> - In-flight rejection: Cluster-wide, only one active `SendMessage` (blocking, non-blocking, or
>   streaming) may run against a given `taskId` at any time. A duplicate concurrent submission is
>   rejected with `A2A:INVALID_REQUEST` ("Another SendMessage is already in flight for taskId {id};
>   retry once it completes."), so a task’s message-history ordering holds under concurrency. Orphan
>   claims from a crashed worker auto-clear via the multi-replica claim store’s 5-minute TTL.
> - Terminal-sticky rejection: Once a task reaches a terminal state (`TASK_STATE_COMPLETED` /
>   `TASK_STATE_FAILED` / `TASK_STATE_CANCELED` / `TASK_STATE_REJECTED`), further `SendMessage` /
>   `SendStreamingMessage` requests against that `taskId` are rejected with
>   `A2A:UNSUPPORTED_OPERATION` ("Task has reached terminal state."). The same rejection also fires
>   when a legitimate terminal transition (typically an out-of-replica `CancelTask` or the **A2A
>   Server - Task Listener** flow’s own terminal **A2A Server - Update Task Status** operation)
>   commits while a concurrent write is mid-flight, so racing and non-racing multi-turn attempts
>   look identical to the client.

## Streaming with the Unified Task Listener

Streaming (`SendStreamingMessage`, wire `POST /message:stream` on HTTP+JSON) uses the same **A2A
Server - Task Listener** flow as non-streaming. No separate **A2A Server - On Task Stream Listener**
is needed. Emit intermediate status and artifact events via the **A2A Server - Update Task Status**
and **A2A Server - Update Task Artifact** operations. The connector delivers them over SSE to the
connected client. Each event’s DataWeave payload uses the `StreamResponse` root key (`statusUpdate`
or `artifactUpdate`) with `taskId`, `contextId`, and body under it. There is no explicit `final`
boolean. The connector derives finality from `TaskStatus.state.isFinal()`.

```xml
<flow name="a2aStreamFlow">
    <a2a:task-listener doc:name="Task Listener" config-ref="A2A_Server_config"/>

    <set-variable variableName="taskId"    value="#[attributes.taskId]"/>
    <set-variable variableName="contextId" value="#[attributes.contextId]"/>

    <a2a:update-task-status doc:name="Working" config-ref="A2A_Server_config">
        <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    status: {
      state: "TASK_STATE_WORKING",
      message: {
        messageId: uuid(),
        role: "ROLE_AGENT",
        parts: [{ text: "Task accepted and processing started" }]
      }
    }
  }
}]]]></a2a:status-content>
    </a2a:update-task-status>

    <a2a:update-task-artifact doc:name="Partial Answer" config-ref="A2A_Server_config">
        <a2a:artifact-content><![CDATA[#[%dw 2.0
output application/json
---
{
  artifactUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    artifact: {
      artifactId: "artifact-" ++ vars.taskId,
      name: "partial-answer",
      parts: [{ text: "Here is an incremental result chunk." }]
    }
  }
}]]]></a2a:artifact-content>
    </a2a:update-task-artifact>

    <a2a:update-task-status doc:name="Completed" config-ref="A2A_Server_config">
        <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: vars.taskId,
    contextId: vars.contextId,
    status: { state: "TASK_STATE_COMPLETED" }
  }
}]]]></a2a:status-content>
    </a2a:update-task-status>
</flow>
```

### Expected SSE Event Format

The stream is delivered as standard server-sent events. Every event carries a JSON payload in
`data:`, but the wire envelope depends on the protocol binding that received the streaming request:

- HTTP+JSON: Each `data:` payload is the bare A2A `StreamResponse` envelope. The oneof discriminator
  is the root key: `task` for the initial task snapshot, `statusUpdate` for status events, and
  `artifactUpdate` for artifact events.
- JSON-RPC: Each `data:` payload wraps the same `StreamResponse` inside a JSON-RPC 2.0 success
  response: `{"jsonrpc":"2.0","id":<originalRequestId>,"result":<StreamResponse>}`. The `id` echoes
  the client’s `SendStreamingMessage` or `SubscribeToTask` request id.

HTTP+JSON (`POST /message:stream` or `POST /tasks/{id}:subscribe`):

```text
event: task
data: {"task":{"id":"task-123","contextId":"context-task-123","status":{"state":"TASK_STATE_WORKING"}}}

event: artifact-update
data: {"artifactUpdate":{"taskId":"task-123","contextId":"context-task-123","artifact":{"artifactId":"artifact-task-123","name":"partial-answer","parts":[{"text":"Here is an incremental result chunk."}]}}}

event: status-update
data: {"statusUpdate":{"taskId":"task-123","contextId":"context-task-123","status":{"state":"TASK_STATE_COMPLETED"}}}
```

JSON-RPC (`method: "SendStreamingMessage"` or `method: "SubscribeToTask"`, request id `"req-1"`):

```text
event: task
data: {"jsonrpc":"2.0","id":"req-1","result":{"task":{"id":"task-123","contextId":"context-task-123","status":{"state":"TASK_STATE_WORKING"}}}}

event: artifact-update
data: {"jsonrpc":"2.0","id":"req-1","result":{"artifactUpdate":{"taskId":"task-123","contextId":"context-task-123","artifact":{"artifactId":"artifact-task-123","name":"partial-answer","parts":[{"text":"Here is an incremental result chunk."}]}}}}

event: status-update
data: {"jsonrpc":"2.0","id":"req-1","result":{"statusUpdate":{"taskId":"task-123","contextId":"context-task-123","status":{"state":"TASK_STATE_COMPLETED"}}}}
```

Finality is derived from `TaskStatus.state`, not a separate `final` field. The stream closes
automatically on:

- Any terminal state (`TASK_STATE_COMPLETED` / `TASK_STATE_FAILED` / `TASK_STATE_CANCELED` /
  `TASK_STATE_REJECTED`).
- `TASK_STATE_INPUT_REQUIRED`: The client must submit more input before the task can proceed.

`TASK_STATE_AUTH_REQUIRED` does not close the stream. The agent can resolve auth out of band and
continue on the same stream.

### Error Handling for Streaming Flows

Wrap stream-processing logic in error handling and always send a terminal status update on failures:

```xml
<flow name="a2aStreamFlowWithErrors">
    <a2a:task-listener config-ref="A2A_Server_config"/>

    <try>
        <!-- Business logic -->
        <raise-error type="A2A:INTERNAL_ERROR" description="Simulated downstream failure"/>
        <error-handler>
            <on-error-continue enableNotifications="true" logException="true">
                <a2a:update-task-status config-ref="A2A_Server_config">
                    <a2a:status-content><![CDATA[#[%dw 2.0
output application/json
---
{
  statusUpdate: {
    taskId: attributes.taskId,
    contextId: attributes.contextId,
    status: {
      state: "TASK_STATE_FAILED",
      message: {
        messageId: uuid(),
        role: "ROLE_AGENT",
        parts: [{ text: error.description default "Unexpected server error" }]
      }
    }
  }
}]]]></a2a:status-content>
                </a2a:update-task-status>
            </on-error-continue>
        </error-handler>
    </try>
</flow>
```

## Subscribe to an Ongoing Task

The **A2A Client - Subscribe To Task** operation (previously known as _Task Resubscribe_) reconnects
to a task that is already running on the server and streams its remaining events. It reuses the same
`On Task Status Update` and `On Task Artifact Update` route callbacks as the **A2A Client - Send
Stream Message** operation. The task can be created by any of the three _SendMessage_ variants:
blocking **A2A Client - Send Message**, non-blocking **A2A Client - Send Message**
(`returnImmediately=true`), or **A2A Client - Send Stream Message**. All three attach a subscribable
event stream at task creation, so a client can subscribe to any non-terminal task regardless of how
it was originally submitted.

```xml
<a2a:subscribe-to-task doc:name="Subscribe to Task" config-ref="A2A_Client_JsonRpc">
    <a2a:task-id-params><![CDATA[#[{ "id": vars.taskId }]]]></a2a:task-id-params>
    <a2a:on-task-status-update>
        <logger level="INFO" message="Status update: #[payload]"/>
    </a2a:on-task-status-update>
    <a2a:on-task-artifact-update>
        <logger level="INFO" message="Artifact update: #[payload]"/>
    </a2a:on-task-artifact-update>
</a2a:subscribe-to-task>
```

If the target task is already in a terminal state at subscribe time, the server rejects with
`A2A:UNSUPPORTED_OPERATION` ("Cannot subscribe to task in terminal state …​"). Otherwise, the
connector replays all previously buffered events for the task to the late subscriber before live
event delivery resumes. It replays the current `task` snapshot first, then every `statusUpdate` and
`artifactUpdate` published before the subscribe point. Buffering keeps growing as long as the task
is still open. After the task reaches a terminal state (`TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`,
`TASK_STATE_CANCELED`, or `TASK_STATE_REJECTED`) or `TASK_STATE_INPUT_REQUIRED`, the stream closes
and no further events flow through it. `TASK_STATE_AUTH_REQUIRED` does not close the stream.

## Multi-Tenant Configuration

A single `(protocol, path)` endpoint can serve multiple logically distinct tenants. Tenant
identities are advertised in the agent card, not in the DSL. Each request carries its tenant in one
canonical location:

- JSON-RPC: Always in `params.tenant` on the request body.
- HTTP+JSON POST-with-body operations (`SendMessage`, `SendStreamingMessage`, and
  `CreateTaskPushNotificationConfig`): In `params.tenant` on the body.
- HTTP+JSON GET, DELETE, and POST-custom-method operations: In the `?tenant=` query parameter.

Every request is validated against the tenants advertised for the endpoint’s `(protocol, path)`.
Unknown tenants are rejected with `A2A:INVALID_PARAMS`. Missing or blank tenants are normalized to
the empty string sentinel (`""`) on both transports.

Every source (**A2A Server - Task Listener**, **A2A Server - On Async Request Listener**, **A2A
Server - On Push Notification Set Listener**, **A2A Server - Task Authorizer Listener**) surfaces
`attributes.tenant` for per-tenant branching:

```xml
<flow name="multiTenantFlow">
    <a2a:task-listener config-ref="A2A_Server_config"/>

    <choice doc:name="Route by tenant">
        <when expression="#[attributes.tenant == 'us-east']">
            <flow-ref name="usEastRoutingFlow"/>
        </when>
        <when expression="#[attributes.tenant == 'eu-west']">
            <flow-ref name="euWestRoutingFlow"/>
        </when>
        <otherwise>
            <flow-ref name="defaultRoutingFlow"/>
        </otherwise>
    </choice>
</flow>
```

The corresponding agent card advertises the tenants:

```json
{
  "supportedInterfaces": [
    {
      "protocolBinding": "JSONRPC",
      "url": "https://fqdn.com/stock-summarizer/rpc",
      "protocolVersion": "1.0",
      "tenant": "us-east"
    },
    {
      "protocolBinding": "JSONRPC",
      "url": "https://fqdn.com/stock-summarizer/rpc",
      "protocolVersion": "1.0",
      "tenant": "eu-west"
    },
    {
      "protocolBinding": "HTTP_JSON",
      "url": "https://fqdn.com/stock-summarizer/",
      "protocolVersion": "1.0",
      "tenant": "us-east"
    }
  ]
}
```

## Task Authorization

The **A2A Server - Task Authorizer Listener** source (which supersedes the older **A2A Server -
Authorization Listener** source) gates every auth-required operation before it executes. It runs on
both JSON-RPC and HTTP+JSON. The payload is the A2A operation’s params object (transport-agnostic),
and its concrete shape depends on the operation being authorized:

- `ListTasks`: The flow receives a JSON array of `{taskId, contextId}` candidates for the current
  page. It must return the authorized subset (return the same shape with the entries to keep, or an
  empty array to deny the whole page). This is the only operation that expects a return payload from
  the flow.
- `SendMessage` and `SendStreamingMessage`: Payload is `MessageSendParams`
  (`{ message: { messageId, role, parts, …​ }, configuration?, metadata? }`).
- `GetTask`, `CancelTask`, and `SubscribeToTask`: Payload is `TaskIdParams` (`{ id, metadata? }`).
- `CreateTaskPushNotificationConfig`: Payload is `TaskPushNotificationConfig`
  (`{ taskId, pushNotificationConfig: { url, id?, token?, authentication? }, metadata? }`).
- `GetTaskPushNotificationConfig` and `DeleteTaskPushNotificationConfig`: Payload is
  `GetTaskPushNotificationConfigParams` or `DeleteTaskPushNotificationConfigParams`
  (`{ id, pushNotificationConfigId, metadata? }`).
- `ListTaskPushNotificationConfigs`: Payload is `ListTaskPushNotificationConfigParams`
  (`{ id, pageSize?, pageToken?, metadata? }`).

For every operation except `ListTasks`, successful completion of the flow authorizes the request.
Raising an error denies it (mapped to `A2A:UNAUTHORIZED`).

The current operation name is exposed on `attributes.operationName` so a single listener flow can
multiplex all the payload shapes.

```xml
<flow name="taskAuthorizerFlow">
    <a2a:task-authorizer-listener doc:name="Task Authorizer" config-ref="A2A_Server_config"/>

    <choice>
        <when expression="#[attributes.operationName == 'ListTasks']">
            <ee:transform>
                <ee:message>
                    <ee:set-payload><![CDATA[%dw 2.0
output application/json
---
payload filter (
  (attributes.tenant == 'us-east' and $.taskId startsWith 'us-')
  or (attributes.tenant == 'eu-west' and $.taskId startsWith 'eu-')
)]]></ee:set-payload>
                </ee:message>
            </ee:transform>
        </when>
        <otherwise>
            <flow-ref name="validateTaskOwnershipFlow"/>
        </otherwise>
    </choice>
</flow>
```

## Server-Side Batch Read and Metadata

### A2A Server - Get Tasks: Resolve Tasks Referenced by an Incoming Message

A server-side operation that fetches a batch of tasks from the task store by ID. The primary use
case is resolving `referenceTaskIds` on incoming A2A messages: when a client’s `SendMessage` /
`SendStreamingMessage` request carries `params.message.referenceTaskIds: ["taskA", "taskB", …​]`,
the agent flow needs the full task objects (status, artifacts, history) to have proper
conversational context. Drop the **A2A Server - Get Tasks** operation into the **A2A Server - Task
Listener** flow with those IDs to load them in a single call.

```xml
<a2a:task-listener config-ref="A2A_Server_config"/>

<a2a:get-tasks doc:name="Load Referenced Tasks" config-ref="A2A_Server_config" historyLength="10">
    <a2a:task-ids><![CDATA[#[payload.message.referenceTaskIds default []]]]></a2a:task-ids>
</a2a:get-tasks>

<set-variable variableName="referencedTasks" value="#[payload.tasks]"/>
```

`taskIds` is a JSON array of task IDs. `historyLength` caps the number of history entries returned
per task (`0` omits history, default `0`). Tasks that cannot be found are not treated as errors.
They are reported separately in `nonExistentTaskIds`.

The response is a `GetTasksResponse` object with two arrays:

```json
{
  "tasks": [
    {
      "id": "task-a",
      "contextId": "ctx-a",
      "status": { "state": "TASK_STATE_COMPLETED" },
      "artifacts": [ ... ],
      "history": [ ... ],
      "metadata": { ... }
    }
  ],
  "nonExistentTaskIds": [ "task-b" ]
}
```

`tasks[]` carries the full `Task` object for every ID that resolved. `nonExistentTaskIds[]` lists
the input IDs that could not be resolved because they were not found in the store or failed to load.
The server logs the underlying reason.

### A2A Server - Get Tasks By Context: Recover a Conversational Session

A server-side operation that fetches every task belonging to a `contextId`, oldest first. A2A 1.0.0
treats a `contextId` as a conversational session that groups multiple task and message objects, so
this operation lets an agent flow recover that session in a single call. Unlike the **A2A Client -
List Tasks** operation, the full ordered task list is returned rather than paged, and tasks are
never truncated. Use **History Length** to bound the message history embedded within each task
(default is all history). A blank or unknown `contextId` returns an empty list rather than an error.

```xml
<a2a:task-listener config-ref="A2A_Server_config"/>

<a2a:get-tasks-by-context doc:name="Load Context Tasks" config-ref="A2A_Server_config" historyLength="10">
    <a2a:context-id><![CDATA[#[attributes.contextId]]]></a2a:context-id>
</a2a:get-tasks-by-context>

<set-variable variableName="contextTasks" value="#[payload]"/>
```

The response is an array of the full `Task` objects recorded for the context, oldest first.

### A2A Server - Set Task Metadata: Replace Metadata

Full-replace (no merge) of the persisted ``Task’s `metadata`` field. Pass an empty JSON object
(`{}`) to clear. Typical use is inside an **A2A Server - Task Listener** flow to stamp
workflow-tracking or annotation data on the task as it progresses, so downstream `GetTask` /
`ListTasks` reads (and the eventual terminal response materialized for a blocking `SendMessage`)
reflect it. Because the operation persists straight to the task store and does not dispatch a
`statusUpdate` / `artifactUpdate` event, streaming subscribers do not receive it out-of-band.

```xml
<flow name="taskFlowWithMetadata">
    <a2a:task-listener config-ref="A2A_Server_config"/>

    <set-variable variableName="taskId"        value="#[attributes.taskId]"/>
    <set-variable variableName="workflowRunId" value="#[uuid()]"/>

    <!-- Stamp workflow-tracking metadata onto the task before doing the actual work. -->
    <a2a:set-task-metadata doc:name="Stamp Workflow Metadata" config-ref="A2A_Server_config" taskId="#[vars.taskId]">
        <a2a:metadata><![CDATA[#[%dw 2.0
output application/json
---
{
  "workflowRunId": vars.workflowRunId,
  "receivedAt": now() as String,
  "annotations": { "source": "task-listener-flow" }
}]]]></a2a:metadata>
    </a2a:set-task-metadata>

    <!-- ... business logic and <a2a:update-task-status> / <a2a:update-task-artifact> calls ... -->
</flow>
```

Rejected for tasks already in a terminal state (`A2A:INTERNAL_ERROR`). Other errors:
`A2A:PARSE_ERROR` (payload not valid JSON), `A2A:TASK_NOT_FOUND` (unknown `taskId`).

## Client-Side List Operations

### A2A Client - List Tasks: List Tasks from the Server

The **A2A Client - List Tasks** operation returns the tasks from the target A2A server as a list
(`Array of Any`) with a configurable streaming strategy, so it can be iterated from a `<foreach>` in
the flow.

```xml
<a2a:list-tasks config-ref="A2A_Client_HttpJson">
    <a2a:list-tasks-params><![CDATA[{ "pageSize": 50 }]]></a2a:list-tasks-params>
</a2a:list-tasks>

<foreach doc:name="Iterate Tasks" collection="#[payload]">
    <logger level="INFO" message="Task: #[payload]"/>
</foreach>
```

### A2A Client - List Push Notification Configs: List Configs from the Server

Now returns its results as a list (`Array of Any`) with a configurable streaming strategy too:

```xml
<a2a:list-push-notification-configs config-ref="A2A_Client_HttpJson">
    <a2a:list-push-config-params><![CDATA[{ "id": vars.taskId, "pageSize": 20 }]]></a2a:list-push-config-params>
</a2a:list-push-notification-configs>
```

### A2A Client - Get Card: Fetch Public or Extended Agent Card

The extended agent card is fetched via the **Use Extended Card** boolean parameter on the existing
**A2A Client - Get Card** operation:

```xml
<a2a:get-card config-ref="A2A_Client_JsonRpc"/>                              <!-- public card -->
<a2a:get-card config-ref="A2A_Client_JsonRpc" useExtendedCard="true"/>       <!-- authenticated extended card -->
```

Agent-card discovery (both connect-time and the **A2A Client - Get Card** operation) is exempt from
the default `A2A-Version: 1.0` request header.

## JSON-RPC 2.0 Request and Response Patterns

### Non-Streaming Send (`SendMessage`)

```json
{
  "jsonrpc": "2.0",
  "id": "req-1001",
  "method": "SendMessage",
  "params": {
    "message": {
      "messageId": "550e8400-e29b-41d4-a716-446655440000",
      "role": "ROLE_USER",
      "parts": [{ "text": "Summarize the latest task status." }]
    }
  }
}
```

Response, where the `result` object is an A2A `Task`:

```json
{
  "jsonrpc": "2.0",
  "id": "req-1001",
  "result": {
    "id": "task-1001",
    "contextId": "context-task-1001",
    "status": { "state": "TASK_STATE_COMPLETED" },
    "artifacts": [
      {
        "artifactId": "artifact-task-1001",
        "name": "answer",
        "parts": [{ "text": "Task completed successfully." }]
      }
    ],
    "history": []
  }
}
```

### Non-Blocking Send (`SendMessage` + `returnImmediately`)

```json
{
  "jsonrpc": "2.0",
  "id": "req-2001",
  "method": "SendMessage",
  "params": {
    "message": {
      "messageId": "...",
      "role": "ROLE_USER",
      "parts": [{ "text": "Run a long-running analysis." }]
    },
    "configuration": {
      "returnImmediately": true
    }
  }
}
```

The response comes back synchronously with an initial `Task` (typically in `TASK_STATE_SUBMITTED` or
`TASK_STATE_WORKING`). The server continues compute asynchronously. Follow up with `SubscribeToTask`
to stream the remaining events.

### Streaming Send (`SendStreamingMessage`)

```json
{
  "jsonrpc": "2.0",
  "id": "req-stream-3001",
  "method": "SendStreamingMessage",
  "params": {
    "message": {
      "messageId": "...",
      "role": "ROLE_USER",
      "parts": [{ "text": "Generate a step-by-step answer." }]
    }
  }
}
```

The response is an SSE stream shaped as in
[Streaming with the Unified Task Listener](#configure-streaming-with-unified-task-listener).

### Multi-Tenant Request

To target a specific tenant, add `params.tenant`:

```json
{
  "jsonrpc": "2.0",
  "id": "req-4001",
  "method": "SendMessage",
  "params": {
    "tenant": "us-east",
    "message": { "messageId": "...", "role": "ROLE_USER", "parts": [{ "text": "..." }] }
  }
}
```

## HTTP+JSON Request and Response Patterns

The HTTP+JSON binding uses one URL per operation. The body carries only the `params` (no JSON-RPC
envelope). Base path is `{agentPath}{interface.path}`.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Operation</th><th>HTTP method + URL</th><th>Body / query</th></tr></thead><tbody><tr><td><p><code>SendMessage</code></p></td><td><p><code>POST /message:send</code></p></td><td><p>Body = <code>MessageSendParams</code> JSON</p></td></tr><tr><td><p><code>SendStreamingMessage</code></p></td><td><p><code>POST /message:stream</code> (SSE)</p></td><td><p>Body = <code>MessageSendParams</code> JSON</p></td></tr><tr><td><p><code>GetTask</code></p></td><td><p><code>GET /tasks/{id}</code></p></td><td><p><code>?historyLength=&amp;tenant=</code></p></td></tr><tr><td><p><code>CancelTask</code></p></td><td><p><code>POST /tasks/{id}:cancel</code></p></td><td><p>Body = <code>TaskIdParams</code> JSON</p></td></tr><tr><td><p><code>SubscribeToTask</code></p></td><td><p><code>POST /tasks/{id}:subscribe</code> (SSE)</p></td><td><p>No body. <code>?tenant=</code></p></td></tr><tr><td><p><code>CreateTaskPushNotificationConfig</code></p></td><td><p><code>POST /tasks/{id}/pushNotificationConfigs</code></p></td><td><p>Body = <code>TaskPushNotificationConfig</code> JSON</p></td></tr><tr><td><p><code>GetTaskPushNotificationConfig</code></p></td><td><p><code>GET /tasks/{id}/pushNotificationConfigs/{configId}</code></p></td><td><p><code>?tenant=</code></p></td></tr><tr><td><p><code>ListTaskPushNotificationConfigs</code></p></td><td><p><code>GET /tasks/{id}/pushNotificationConfigs</code></p></td><td><p><code>?pageSize=&amp;pageToken=&amp;tenant=</code></p></td></tr><tr><td><p><code>DeleteTaskPushNotificationConfig</code></p></td><td><p><code>DELETE /tasks/{id}/pushNotificationConfigs/{configId}</code></p></td><td><p><code>?tenant=</code></p></td></tr><tr><td><p><code>ListTasks</code></p></td><td><p><code>GET /tasks</code></p></td><td><p><code>?pageSize=&amp;pageToken=&amp;tenant=</code></p></td></tr><tr><td><p><code>GetPublicAgentCard</code></p></td><td><p><code>GET /.well-known/agent-card.json</code></p></td><td><p>No headers required. Discovery is exempt from the <code>A2A-Version</code> header.</p></td></tr><tr><td><p><code>GetExtendedAgentCard</code></p></td><td><p><code>GET /extendedAgentCard</code></p></td><td><p><code>?tenant=</code></p></td></tr></tbody></table>

Example `POST /message:send`:

```json
{
  "message": {
    "messageId": "550e8400-e29b-41d4-a716-446655440000",
    "role": "ROLE_USER",
    "parts": [{ "text": "Hello, this is my message" }]
  }
}
```

The response body is a plain A2A `Task` (no JSON-RPC envelope).

## Sample `agent-card.json` for A2A 1.0.0

Use this as a starting point for cards that advertise both JSON-RPC and HTTP+JSON transports, plus
streaming, push notifications, and tenants:

```json
{
  "name": "Finance Streaming Agent",
  "description": "Handles financial analysis tasks with streaming progress updates and push notifications.",
  "version": "2.0.0",
  "protocolVersion": "1.0",
  "provider": {
    "organization": "Example Org",
    "url": "https://example.org"
  },
  "supportedInterfaces": [
    {
      "protocolBinding": "JSONRPC",
      "url": "https://example.org/stock-summarizer/rpc",
      "protocolVersion": "1.0",
      "tenant": ""
    },
    {
      "protocolBinding": "HTTP_JSON",
      "url": "https://example.org/stock-summarizer/",
      "protocolVersion": "1.0",
      "tenant": ""
    }
  ],
  "capabilities": {
    "streaming": true,
    "pushNotifications": true,
    "extendedAgentCard": false
  },
  "skills": [
    {
      "id": "financial-analysis",
      "name": "Financial Analysis",
      "description": "Analyzes public company financial performance."
    }
  ],
  "defaultInputModes": ["application/json", "text/plain"],
  "defaultOutputModes": ["application/json", "text/plain"]
}
```

The card is the single source of truth for tenants. To add a tenant, add another entry with the same
`(protocolBinding, url)` and a distinct `tenant` value. No DSL rewrite or redeploy is needed for the
transport wiring.

## Complete Mule App Example

A full example combining a multi-transport server, an initial-task customizer, a unified task
listener, push-notification config handling, and a client **A2A Client - List Tasks** call:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<mule
    xmlns:a2a="http://www.mulesoft.org/schema/mule/a2a"
    xmlns:http="http://www.mulesoft.org/schema/mule/http"
    xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
    xmlns="http://www.mulesoft.org/schema/mule/core"
    xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/a2a http://www.mulesoft.org/schema/mule/a2a/current/mule-a2a.xsd
http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

    <http:listener-config name="HTTP_Listener_config" basePath="/v1">
        <http:listener-connection host="0.0.0.0" port="${http.port}"/>
    </http:listener-config>

    <a2a:server-config name="A2A_Server">
        <a2a:connection listenerConfig="HTTP_Listener_config" agentPath="/stock-summarizer">
            <a2a:interfaces>
                <a2a:interface protocol="JSONRPC"   path="/rpc"/>
                <a2a:interface protocol="HTTP_JSON" path="/"/>
            </a2a:interfaces>
        </a2a:connection>
        <a2a:agent-card>
            <a2a:json><![CDATA[{
  "name": "Stock Summarizer Agent",
  "version": "2.0.0",
  "protocolVersion": "1.0",
  "description": "Summarizes stock-related questions; supports streaming and push notifications.",
  "supportedInterfaces": [
    { "protocolBinding": "JSONRPC",   "url": "http://localhost:8082/v1/stock-summarizer/rpc", "protocolVersion": "1.0", "tenant": "" },
    { "protocolBinding": "HTTP_JSON", "url": "http://localhost:8082/v1/stock-summarizer/",    "protocolVersion": "1.0", "tenant": "" }
  ],
  "capabilities": {
    "streaming": true,
    "pushNotifications": true,
    "extendedAgentCard": false
  },
  "skills": [
    {
      "id": "stock-summary",
      "name": "Stock Earnings Summary",
      "description": "Summarizes stock earnings and financial highlights.",
      "inputModes":  ["application/json", "text/plain"],
      "outputModes": ["application/json", "text/plain"]
    }
  ],
  "provider": { "organization": "MuleSoft", "url": "https://www.mulesoft.com" },
  "defaultInputModes":  ["application/json", "text/plain"],
  "defaultOutputModes": ["application/json", "text/plain"]
}]]></a2a:json>
        </a2a:agent-card>
    </a2a:server-config>

    <a2a:client-config name="A2A_Client">
        <a2a:jsonrpc-client-connection agentUrl="http://localhost:8082/v1/stock-summarizer"/>
    </a2a:client-config>

    <http:request-config name="OpenAI_config" basePath="/v1">
        <http:request-connection host="api.openai.com" port="443" protocol="HTTPS"/>
    </http:request-config>

    <!-- Optional: customize the initial Task response for streaming and non-blocking sends. -->
    <flow name="initialTaskFlow">
        <a2a:on-async-request-listener config-ref="A2A_Server"/>
        <ee:transform>
            <ee:message>
                <ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{
  task: {
    id: attributes.taskId,
    contextId: attributes.contextId,
    status: { state: "TASK_STATE_SUBMITTED" }
  }
}]]></ee:set-payload>
            </ee:message>
        </ee:transform>
    </flow>

    <!-- Unified task-listener: serves blocking, non-blocking, and streaming SendMessage. -->
    <flow name="a2aServerFlow">
        <a2a:task-listener config-ref="A2A_Server"/>

        <ee:transform doc:name="OpenAI Request">
            <ee:message>
                <ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{
  model: "gpt-4.1",
  messages: [ { role: "user", content: payload.message.parts[0].text } ]
}]]></ee:set-payload>
            </ee:message>
            <ee:variables>
                <ee:set-variable variableName="taskId">#[attributes.taskId]</ee:set-variable>
                <ee:set-variable variableName="contextId">#[attributes.contextId]</ee:set-variable>
            </ee:variables>
        </ee:transform>

        <http:request method="POST" config-ref="OpenAI_config" path="/chat/completions" responseTimeout="20000">
            <http:headers><![CDATA[#[%dw 2.0
output application/java
---
{ Authorization: "Bearer " ++ p("secure::openai.token") }]]]></http:headers>
        </http:request>

        <ee:transform doc:name="A2A Task Response">
            <ee:message>
                <ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{
  id: vars.taskId,
  contextId: vars.contextId,
  status: {
    state: "TASK_STATE_COMPLETED",
    message: {
      role: "ROLE_AGENT",
      messageId: uuid(),
      parts: [{ text: payload.choices[0].message.content }]
    }
  },
  artifacts: [
    {
      artifactId: uuid(),
      name: "answer",
      parts: [{ text: payload.choices[0].message.content }]
    }
  ]
}]]></ee:set-payload>
            </ee:message>
        </ee:transform>
    </flow>

    <!-- Push-notification config authoring (unchanged listener; 1.0.0 TaskPushNotificationConfig shape on payload). -->
    <flow name="pushNotificationConfigFlow">
        <a2a:push-notification-config-listener config-ref="A2A_Server"/>
        <logger level="INFO" message="Push notification config: #[payload]"/>
    </flow>

    <flow name="pushNotificationCallbackFlow">
        <http:listener config-ref="HTTP_Listener_config" path="/update/notification"/>
        <logger level="INFO" message="Push notification callback received: #[payload]"/>
    </flow>

    <!-- Example client caller: submit a task then iterate the server's task list. -->
    <flow name="a2aClientFlow">
        <http:listener config-ref="HTTP_Listener_config" path="/stock/summarize"/>
        <a2a:send-message config-ref="A2A_Client">
            <a2a:message><![CDATA[#[%dw 2.0
output application/json
---
{
  message: {
    role: "ROLE_USER",
    messageId: uuid(),
    parts: [{ text: "Summarize the stock earnings for " ++ attributes.queryParams.stock ++ " in Q4 2024" }]
  },
  configuration: {
    pushNotificationConfig: {
      url: "http://localhost:8082/v1/update/notification"
    }
  }
}]]></a2a:message>
        </a2a:send-message>
    </flow>

    <flow name="listAllTasksFlow">
        <http:listener config-ref="HTTP_Listener_config" path="/admin/tasks"/>
        <foreach batchSize="1">
            <a2a:list-tasks config-ref="A2A_Client">
                <a2a:list-tasks-params><![CDATA[{ "pageSize": 50 }]]></a2a:list-tasks-params>
            </a2a:list-tasks>
            <logger level="INFO" message="Task page: #[payload]"/>
        </foreach>
    </flow>

</mule>
```

## See Also

- [A2A Connector Troubleshooting](a2a-connector-troubleshooting)
- [A2A Connector Reference](a2a-connector-reference)
- [MuleSoft Inference Connector Documentation](../../mulesoft-inference-connector/latest/)
- [Introduction to Anypoint Connectors](../../connectors/introduction/introduction-to-anypoint-connectors)
- [Salesforce Help](https://help.salesforce.com)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# A2A Connector 2.0 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Agent2Agent (A2A) (A2A Connector) provides A2A protocol support for LLM
agents, enabling your agents to talk to other agents.

## Configurations

### Client

The application or AI system that initiates requests and consumes services offered by A2A servers.
This allows Mule apps to act as A2A brokers between non A2A “head” agents and A2A “node” agents.

#### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>Name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><ul><li><p><a href="#HttpJsonClientConnection">Http Json Client Connection</a></p></li><li><p><a href="#JsonrpcClientConnection">Jsonrpc Client Connection</a></p></li></ul></div></div></td><td><p>The connection types to provide to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Name</p></td><td><div><div><p>String</p></div></div></td><td><p>ID used to reference this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy</a></p></div></div></td><td><p>Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></td><td></td><td></td></tr></tbody></table>

#### Connection Types

##### Http Json Client Connection

###### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Agent Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL for the target A2A agent, used for agent card discovery via <code>/.well-known/agent-card.json</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Request Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Sets the duration to wait for server responses before timing out requests.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Request Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Request Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Authentication</p></td><td><div><div><p>HttpRequestAuthentication</p></div></div></td><td><p>Authentication method used when sending requests to the target A2A agent.</p></td><td></td><td></td></tr><tr><td><p>Default Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Default headers.</p></td><td></td><td></td></tr><tr><td><p>Tls Context</p></td><td><div><div><p><a href="#Tls">TLS</a></p></div></div></td><td><p>Configures TLS for secure communication with the target A2A agent.</p></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

##### Jsonrpc Client Connection

###### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Agent Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL for the target A2A agent, used for agent card discovery via <code>/.well-known/agent-card.json</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Request Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Sets the duration to wait for server responses before timing out requests.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Request Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Request Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Authentication</p></td><td><div><div><p>HttpRequestAuthentication</p></div></div></td><td><p>Authentication method used when sending requests to the target A2A agent.</p></td><td></td><td></td></tr><tr><td><p>Default Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Default headers.</p></td><td></td><td></td></tr><tr><td><p>Tls Context</p></td><td><div><div><p><a href="#Tls">TLS</a></p></div></div></td><td><p>Configures TLS for secure communication with the target A2A agent.</p></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

#### Associated Operations

- [A2A Client - Cancel Task](#CancelTask)
- [A2A Client - Create Push Notification Config](#CreatePushNotificationConfig)
- [A2A Client - Delete Push Notification Config](#DeletePushNotificationConfig)
- [A2A Client - Get Card](#GetCard)
- [A2A Client - Get Push Notification Config](#GetPushNotificationConfig)
- [A2A Client - Get Task](#GetTask)
- [A2A Client - List Push Notification Configs](#ListPushNotificationConfigs)
- [A2A Client - List Tasks](#ListTasks)
- [A2A Client - Send Message](#SendMessage)
- [A2A Client - Send Stream Message](#SendStreamMessage)
- [A2A Client - Subscribe To Task](#SubscribeToTask)

---

### Server

The A2A server acts as a remote agent that exposes an HTTP(S) endpoint and implements the A2A
protocol methods for interacting with other AI agents. This allows Mule-based agents to receive and
respond to A2A protocol-compliant requests.

#### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>Name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><p><a href="#ServerConnection">Connection</a></p></div></div></td><td><p>The connection types to provide to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Name</p></td><td><div><div><p>String</p></div></div></td><td><p>ID used to reference this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy</a></p></div></div></td><td><p>Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></td><td></td><td></td></tr><tr><td><p>Card Json</p></td><td><div><div><p>String</p></div></div></td><td><p>Agent card as a JSON string.</p></td><td></td><td></td></tr><tr><td><p>Card Path</p></td><td><div><div><p>String</p></div></div></td><td><p>The absolute path of a JSON file to load the agent card.</p></td><td></td><td></td></tr><tr><td><p>Task History Enabled</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Set to <code>true</code> to enable retrieval of task history. Task history is stored as message objects.</p></td><td><p>true</p></td><td></td></tr><tr><td><p>Default Max History Length</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of task history objects to store.</p></td><td></td><td></td></tr><tr><td><p>Task Repository Object Store</p></td><td><div><div><p>ObjectStore</p></div></div></td><td><p>Object store used to persist tasks and their history. If not set, the default object store is used.</p></td><td></td><td></td></tr></tbody></table>

#### Connection Types

##### Server Connection

###### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Listener Config</p></td><td><div><div><p>String</p></div></div></td><td><p>Reference to the <code>&lt;http:listener-config&gt;</code> used to expose the task listener endpoints.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Agent Path</p></td><td><div><div><p>String</p></div></div></td><td><p>Base HTTP path for this agent. The agent card is served at <code>{agentPath}/.well-known/agent-card.json</code>. Each interface’s JSON-RPC or HTTP+JSON routes are registered at the agent path plus that interface’s path.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Interfaces</p></td><td><div><div><p>Array of <a href="#Interface">Interface</a></p></div></div></td><td><p>Interfaces the agent supports.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Tls Context Ref</p></td><td><div><div><p>String</p></div></div></td><td><p>Reference to the TLS context used to secure the inbound endpoint.</p></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

#### Associated Operations

- [A2A Server - Get Tasks](#GetTasks)
- [A2A Server - Get Tasks By Context](#GetTasksByContext)
- [A2A Server - Send Push Notification](#SendPushNotification)
- [A2A Server - Set Task Metadata](#SetTaskMetadata)
- [A2A Server - Update Task Artifact](#UpdateTaskArtifact)
- [A2A Server - Update Task Status](#UpdateTaskStatus)

#### Associated Sources

- [A2A Server - On Async Request Listener](#OnAsyncRequestListener)
- [A2A Server - On Push Notification Set Listener](#PushNotificationConfigListener)
- [A2A Server - Task Authorizer Listener](#TaskAuthorizerListener)
- [A2A Server - Task Listener](#TaskListener)

## A2A Client - Cancel Task

`<a2a:cancel-task>`

Cancels the task specified by its unique identifier. It’s used to stop a previously initiated task.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task Id</p></td><td><div><div><p>Any</p></div></div></td><td><p>Unique identifier for the task.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - Create Push Notification Config

`<a2a:create-push-notification-config>`

Creates a push notification configuration for a specified task.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task Push Notification Config</p></td><td><div><div><p>Any</p></div></div></td><td><p>Associates a push notification configuration with a specific task.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - Delete Push Notification Config

`<a2a:delete-push-notification-config>`

Deletes an associated push notification configuration for a task.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Get Push Config Params</p></td><td><div><div><p>Any</p></div></div></td><td><p>Object for fetching the push notification configuration for a task.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - Get Card

`<a2a:get-card>`

Gets the agent card.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Use Extended Card</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>When true, fetches the authenticated extended agent card instead of the normal agent card.</p></td><td><p>false</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:EXTENDED_CARD_UNCONFIGURED
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_CARD
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION
- A2A:VERSION_UNSUPPORTED

## A2A Client - Get Push Notification Config

`<a2a:get-push-notification-config>`

Retrieves the current push notification configuration for a specified task.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Get Push Config Params</p></td><td><div><div><p>Any</p></div></div></td><td><p>Object for fetching the push notification configuration for a task.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - Get Task

`<a2a:get-task>`

Retrieves information about a task based on a provided query. This enables you to fetch the status
or details of a task from another agent.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task Query</p></td><td><div><div><p>Any</p></div></div></td><td><p>Query object identifying the task to retrieve (TaskQueryParams schema).</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - List Push Notification Configs

`<a2a:list-push-notification-configs>`

Retrieves the associated push notification configurations for a specified task.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>List Push Config Params</p></td><td><div><div><p>Any</p></div></div></td><td><p>Object for listing the push notification configurations for a task.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>The MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryIterable">Repeatable In Memory Iterable</a></p></li><li><p><a href="#RepeatableFileStoreIterable">Repeatable File Store Iterable</a></p></li><li><p>non-repeatable-iterable</p></li></ul></div></div></td><td><p>Configures whether repeatable streams are used, and their behavior.</p></td><td></td><td></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Any</p></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - List Tasks

`<a2a:list-tasks>`

Retrieves a list of tasks from the target agent.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>List Tasks Params</p></td><td><div><div><p>Any</p></div></div></td><td><p>Object for listing tasks from the target agent.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>The MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryIterable">Repeatable In Memory Iterable</a></p></li><li><p><a href="#RepeatableFileStoreIterable">Repeatable File Store Iterable</a></p></li><li><p>non-repeatable-iterable</p></li></ul></div></div></td><td><p>Configures whether repeatable streams are used, and their behavior.</p></td><td></td><td></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Any</p></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Client - Send Message

`<a2a:send-message>`

Sends a message.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Message</p></td><td><div><div><p>Any</p></div></div></td><td><p>Message to send.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#ResponseAttributes">Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:CONTENT_TYPE_UNSUPPORTED
- A2A:EXTENSION_SUPPORT_REQUIRED
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION
- A2A:VERSION_UNSUPPORTED

## A2A Client - Send Stream Message

`<a2a:send-stream-message>`

Sends a message to the A2A agent and establishes an SSE streaming connection to receive real-time
status updates, artifacts, and error notifications as the agent processes the request.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Stream Message</p></td><td><div><div><p>Any</p></div></div></td><td><p>Message to send (MessageSendParams schema).</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#StreamingResponseAttributes">Streaming Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:CONTENT_TYPE_UNSUPPORTED
- A2A:EXTENSION_SUPPORT_REQUIRED
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION
- A2A:VERSION_UNSUPPORTED

## A2A Client - Subscribe To Task

`<a2a:subscribe-to-task>`

Reconnects to an existing SSE streaming session for an ongoing task to receive buffered events and
continue receiving real-time updates from where the connection was lost.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task Id Params</p></td><td><div><div><p>Any</p></div></div></td><td><p>Task ID to resubscribe to (TaskIdParams schema).</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Additional Properties</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional properties to include with the request. Use this field to specify custom key-value pairs that are sent with the A2A connector request. This field is optional and null-safe.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#StreamingResponseAttributes">Streaming Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Client](#Client)

### Throws

- A2A:CONNECTIVITY
- A2A:CONTENT_TYPE_UNSUPPORTED
- A2A:EXTENSION_SUPPORT_REQUIRED
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION
- A2A:VERSION_UNSUPPORTED

## A2A Server - Get Tasks

`<a2a:get-tasks>`

Retrieves a batch of tasks from the server’s internal task store. Resolved tasks are returned in
`tasks`; task IDs that the store doesn’t have are reported in `nonExistentTaskIds`. Genuine failures
(such as a corrupt store entry, an ObjectStore IO failure, or an unexpected serialization error) are
surfaced as A2A errors rather than reported as nonexistent. This is a blocking operation because
each lookup performs synchronous IO against the underlying ObjectStore (often Object Store v2).
Lookups run sequentially on the calling thread to avoid uncontrolled fan-out against a remote,
rate-limited store. The primary use case is resolving `referenceTaskIds` on incoming A2A messages so
the agent flow has the full context of referenced tasks.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task IDs</p></td><td><div><div><p>Array of String</p></div></div></td><td><p>Task identifiers to retrieve.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>History Length</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of most recent history entries to include per task. <code>0</code> (default) omits history; a positive value caps history at that many entries. See A2A spec section 3.2.4.</p></td><td><p>0</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:RETRY_EXHAUSTED

## A2A Server - Get Tasks By Context

`<a2a:get-tasks-by-context>`

Retrieves every task belonging to a `contextId`, oldest first, from the server’s internal task
store. A2A 1.0.0 treats a `contextId` as a conversational session that groups multiple task and
message objects, so this operation lets an agent flow recover that session by reading all tasks
recorded for the context in a single call. The full ordered task list is returned and isn’t paged,
because the underlying object store offers no ranged or cursored read: the per-context index loads
as a single entry regardless. Tasks are never truncated, because dropping tasks would give the agent
an incomplete conversation. Use the **History Length** field to bound the message history embedded
within each task. Lookups are synchronous IO against the underlying object store, resolved
sequentially to avoid uncontrolled fan-out against a remote, rate-limited store. Genuine internal
failures (such as an object store IO error or corrupt stored task JSON) are logged server-side with
full detail and surfaced as a generic A2A:INTERNAL_ERROR. A blank or unknown `contextId` returns an
empty task list rather than an error.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Context Id</p></td><td><div><div><p>String</p></div></div></td><td><p>The conversational context whose tasks are retrieved.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>History Length</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of most recent history entries to include per task. Defaults to all history, for full context reconstruction.</p></td><td><p>2147483647</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong> field.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Any</p></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:RETRY_EXHAUSTED

## A2A Server - Send Push Notification

`<a2a:send-push-notification>`

Sends a push notification with the provided streaming event payload. This operation allows sending
asynchronous updates at various stages of a task, not just at the end. The body sent to the push URL
is the StreamResponse JSON, as specified in A2A spec section 4.3.3. This is a non-blocking operation
that uses a completion callback for asynchronous result handling.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Notification Message</p></td><td><div><div><p>Any</p></div></div></td><td><p>JSON for a single streaming event (task, message, status update, or artifact update).</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:INVALID_AGENT_RESPONSE
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:VERSION_UNSUPPORTED

## A2A Server - Set Task Metadata

`<a2a:set-task-metadata>`

Fully replaces (does not merge) the task’s metadata. Pass an empty JSON object (`{}`) to clear it.
This operation doesn’t dispatch an event; subsequent Get Task or blocking responses return whatever
metadata the persisted task carries.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Task Id</p></td><td><div><div><p>String</p></div></div></td><td><p>The ID of the task whose metadata is being replaced.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Metadata</p></td><td><div><div><p>Any</p></div></div></td><td><p>The JSON object to persist as task-level metadata. Pass <code>{}</code> to clear existing metadata.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:INTERNAL_ERROR
- A2A:PARSE_ERROR
- A2A:RETRY_EXHAUSTED
- A2A:TASK_NOT_FOUND

## A2A Server - Update Task Artifact

`<a2a:update-task-artifact>`

Updates a task artifact and dispatches the update through the event dispatcher. Artifacts are
progress updates and never close responses. An unknown task ID returns A2A:TASK_NOT_FOUND.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Artifact Update Content</p></td><td><div><div><p>Any</p></div></div></td><td><p>TaskArtifactUpdateEvent content following A2A specification.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:CONTENT_TYPE_UNSUPPORTED
- A2A:EXTENSION_SUPPORT_REQUIRED
- A2A:INTERNAL_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:TASK_NOT_FOUND
- A2A:UNSUPPORTED_OPERATION

## A2A Server - Update Task Status

`<a2a:update-task-status>`

Updates a task status and dispatches the update through the event dispatcher. Rejects transitions
out of terminal states (A2A spec section 3.1.1). An unknown task ID returns A2A:TASK_NOT_FOUND.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Status Update Content</p></td><td><div><div><p>Any</p></div></div></td><td><p>TaskStatusUpdateEvent content following A2A specification.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

### Throws

- A2A:CONNECTIVITY
- A2A:CONTENT_TYPE_UNSUPPORTED
- A2A:EXTENSION_SUPPORT_REQUIRED
- A2A:INTERNAL_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:RETRY_EXHAUSTED
- A2A:TASK_NOT_FOUND
- A2A:UNSUPPORTED_OPERATION

## Sources

## A2A Server - On Async Request Listener

`<a2a:on-async-request-listener>`

Lets the agent flow customize the initial Task emitted for streaming (Send Stream Message) and
non-blocking (Send Message with `returnImmediately=true`) requests. The flow receives
MessageSendParams as the payload (with `taskId` and `contextId` as attributes) and must return a
Task, which is used to seed initial state, attach artifacts, or gate the request. Returning a
terminal or interrupted Task, or raising an error, rejects the request up front. A missing or
unparseable Task is a server-side fault: the client sees A2A:INTERNAL_ERROR with a generic message,
while the location and parse detail are logged server-side. Push notification configuration is
handled by the [A2A Server - On Push Notification Set Listener](#PushNotificationConfigListener)
source, not this listener.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Primary Node Only</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Determines whether to execute this source on only the primary node when running Mule instances in a cluster.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Redelivery Policy</p></td><td><div><div><p><a href="#RedeliveryPolicy">Redelivery Policy</a></p></div></div></td><td><p>Defines a policy for processing the redelivery of the same message.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr><tr><td><p>Task</p></td><td><div><div><p>Binary</p></div></div></td><td><p><code>@Content</code> defaults the value to the flow’s final <code>#[payload]</code>, so on-async-request-listener flows can express the initial Task by setting the payload (for example, via an <code>&lt;ee:transform&gt;</code>) without wiring <code>&lt;a2a:initial-task&gt;&lt;a2a:task&gt;</code> explicitly. An explicit DSL expression overrides the default.</p></td><td><p>#[payload]</p></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#RequestAttributes">Request Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

## A2A Server - On Push Notification Set Listener

`<a2a:push-notification-config-listener>`

Validates the push notification configuration before routing the request to the **Task Listener**
source.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Primary Node Only</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Determines whether to execute this source on only the primary node when running Mule instances in a cluster.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Redelivery Policy</p></td><td><div><div><p><a href="#RedeliveryPolicy">Redelivery Policy</a></p></div></div></td><td><p>Defines a policy for processing the redelivery of the same message.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr><tr><td><p>Additional Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Additional HTTP headers to include with each request.</p></td><td></td><td></td></tr><tr><td><p>Authentication</p></td><td><div><div><p>HttpRequestAuthentication</p></div></div></td><td><p>Authentication method used when sending push notification requests.</p></td><td></td><td></td></tr><tr><td><p>Push notification request timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Duration to wait for a push notification request to complete before timing out.</p></td><td><p>60</p></td><td></td></tr><tr><td><p>Request Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Push notification request timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Proxy Config</p></td><td><div><div><p>HttpProxyConfig</p></div></div></td><td><p>Proxy configuration.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#RequestAttributes">Request Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

## A2A Server - Task Authorizer Listener

`<a2a:task-authorizer-listener>`

A2A Server task authorizer listener. Gates every auth-required operation before it executes. The
flow’s payload shape depends on the operation. For List Tasks, the flow receives a JSON array of
candidate `{taskId, contextId}` pairs for the current page and must return a JSON array of the
authorized subset (each entry with `taskId` and `contextId`); an empty array denies the entire page.
For other auth-required operations (Get Task, Cancel Task, Subscribe To Task, and the push
notification config Get, List, and Delete operations), the flow receives the raw JSON-RPC request
params as the payload. Successful completion of the flow authorizes the request; the returned
payload isn’t inspected. To deny a request, raise an error from the flow, which is mapped to
UNAUTHORIZED. The current operation is available on `attributes.operationName`.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Primary Node Only</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Determines whether to execute this source on only the primary node when running Mule instances in a cluster.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Redelivery Policy</p></td><td><div><div><p><a href="#RedeliveryPolicy">Redelivery Policy</a></p></div></div></td><td><p>Defines a policy for processing the redelivery of the same message.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr><tr><td><p>Authorized Tasks</p></td><td><div><div><p>Array of Any</p></div></div></td><td><p>For List Tasks, the authorized subset of tasks the flow returns (each entry with <code>taskId</code> and <code>contextId</code>). An empty array denies the entire page.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#RequestAttributes">Request Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

## A2A Server - Task Listener

`<a2a:task-listener>`

Allows a Mule application to listen for and receive incoming A2A protocol-compliant requests from
other AI agents, enabling the Mule-based agent to act as an A2A server and respond to tasks.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Primary Node Only</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Determines whether to execute this source on only the primary node when running Mule instances in a cluster.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Redelivery Policy</p></td><td><div><div><p><a href="#RedeliveryPolicy">Redelivery Policy</a></p></div></div></td><td><p>Defines a policy for processing the redelivery of the same message.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>Retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#RequestAttributes">Request Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Server](#Server)

## Types

### TLS

Configures TLS to provide secure communications for the Mule app.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Enabled Protocols</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Comma-separated list of protocols enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Enabled Cipher Suites</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Comma-separated list of cipher suites enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Trust Store</strong></p></td><td><div><div><p><a href="#TrustStore">Truststore</a></p></div></div></td><td><div><div><p>Configures the TLS truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Store</strong></p></td><td><div><div><p><a href="#KeyStore">Keystore</a></p></div></div></td><td><div><div><p>Configures the TLS keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Revocation Check</strong></p></td><td><div><div><ul><li><p><a href="#StandardRevocationCheck">Standard Revocation Check</a></p></li><li><p><a href="#CustomOcspResponder">Custom OCSP Responder</a></p></li><li><p><a href="#CrlFile">CRL File</a></p></li></ul></div></div></td><td><div><div><p>Configures a revocation checking mechanism.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Truststore

Configures the truststore for TLS.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the truststore. Mule resolves the path relative to the current classpath and file system.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of store.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Encryption algorithm that the truststore uses.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Insecure</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>true</code>, Mule stops performing certificate validations. Setting this to <code>true</code> can make connections vulnerable to attacks.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Keystore

Configures the keystore for the TLS protocol. The keystore you generate contains a private key and a
public certificate.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the keystore. Mule resolves the path relative to the current classpath and file system.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of store.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Alias of the key to use when the keystore contains multiple private keys. By default, Mule uses the first key in the file.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the private key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Encryption algorithm that the keystore uses.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Standard Revocation Check

Configures standard revocation checks for TLS certificates.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Only End Entities</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Which elements to verify in the certificate chain:</p></div><div><ul><li><p><code>true</code></p></li></ul></div><div><p>Verify only the last element in the certificate chain.</p></div><div><ul><li><p><code>false</code></p></li></ul></div><div><p>Verify all elements in the certificate chain.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Prefer Crls</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>How to check certificate validity:</p></div><div><ul><li><p><code>true</code></p></li></ul></div><div><p>Check the Certification Revocation List (CRL) for certificate validity.</p></div><div><ul><li><p><code>false</code></p></li></ul></div><div><p>Use the Online Certificate Status Protocol (OCSP) to check certificate validity.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>No Fallback</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Whether to use the secondary method to check certificate validity:</p></div><div><ul><li><p><code>true</code></p></li></ul></div><div><p>Use the method that wasn’t specified in the <strong>Prefer Crls</strong> field (the secondary method) to check certificate validity.</p></div><div><ul><li><p><code>false</code></p></li></ul></div><div><p>Don’t use the secondary method to check certificate validity.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Soft Fail</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>What to do if the revocation server can’t be reached or is busy:</p></div><div><ul><li><p><code>true</code></p></li></ul></div><div><p>Avoid verification failure.</p></div><div><ul><li><p><code>false</code></p></li></ul></div><div><p>Allow the verification to fail.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Custom OCSP Responder

Configures a custom OCSP responder for certification revocation checks.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Url</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>URL of the OCSP responder.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Cert Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Alias of the signing certificate for the OCSP response. If specified, the alias must be in the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### CRL File

Specifies the location of the certification revocation list (CRL) file.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the CRL file.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnection

Configures a reconnection strategy for an operation.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Fails Deployment</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Reconnection Strategy</strong></p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><div><div><p>Reconnection strategy to use.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect

Configures a standard reconnection strategy, which specifies how often to reconnect and how many
reconnection attempts the connector source or operation can make.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often to attempt to reconnect, in milliseconds.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>false</code>, the reconnection strategy runs in a separate, non-blocking thread.</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How many reconnection attempts the Mule app can make.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

Configures a forever reconnection strategy by which the connector source or operation attempts to
reconnect at a specified frequency for as long as the Mule app runs.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often to attempt to reconnect, in milliseconds.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>false</code>, the reconnection strategy runs in a separate, non-blocking thread.</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr></tbody></table>

### Expiration Policy

Configures an expiration policy strategy.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Max Idle Time</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Configures the maximum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Time Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><div><div><p>Time unit for the <strong>Max Idle Time</strong> field.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Response Attributes

In A2A Connector 1.0 and later, this represents the HTTP response attributes for an A2A request.
This type encapsulates HTTP response metadata, including status code, headers, and reason phrase,
that are sent as part of an A2A protocol response.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Status Code</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>HTTP status code of the response.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div><div><p>Map of HTTP headers in the message.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Reason Phrase</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>HTTP reason phrase of the response.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Error Mapping

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Source</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ANY</p></li><li><p>REDELIVERY_EXHAUSTED</p></li><li><p>TRANSFORMATION</p></li><li><p>EXPRESSION</p></li><li><p>SECURITY</p></li><li><p>CLIENT_SECURITY</p></li><li><p>SERVER_SECURITY</p></li><li><p>ROUTING</p></li><li><p>CONNECTIVITY</p></li><li><p>RETRY_EXHAUSTED</p></li><li><p>TIMEOUT</p></li></ul></div></div></td><td><div><div><p>Type of error to map to the target error type.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Target</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Custom error type to map the source error to.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Repeatable In Memory Iterable

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Initial Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Number of instances initially allowed in memory to consume the stream and provide random access to it. If the stream contains more data than the buffer can hold, the buffer expands according to the <strong>Buffer Size Increment</strong> field, up to the <strong>Max Buffer Size</strong> limit. The default is 100 instances.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Size Increment</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>By how much the buffer size expands if it exceeds its initial size. A value of <code>0</code> or lower means the buffer doesn’t expand, and a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised when the buffer is full. The default is 100 instances.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Max Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum amount of memory used. If exceeded, a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised. A value of <code>0</code> or lower means no limit.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Repeatable File Store Iterable

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>In Memory Objects</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum number of instances kept in memory. If more are required, the content is buffered on disk.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>Unit in which <strong>In Memory Objects</strong> is expressed.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Streaming Response Attributes

In A2A Connector 1.0 and later, this represents the HTTP response attributes for A2A streaming
operations (SSE). This specialized type extends [Response Attributes](#ResponseAttributes) with
streaming-specific metadata, including information about final events received during the SSE
session. This final event information is not related to the A2A protocol final event, but the
connector’s.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Final Event Found</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Whether a final event was found during SSE session.</p></div></div></td><td><div><div><p>false</p></div></div></td><td><div></div></td></tr><tr><td><p><strong>Status Code</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>HTTP status code of the response.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div><div><p>Map of HTTP headers in the message.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Reason Phrase</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>HTTP reason phrase of the response.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Interface

One entry under `<a2a:interfaces>`: a protocol binding that specifies a transport and a path segment
appended to the connection’s agent path for that binding. For example, with agent path `/my-agent`
and path `/rpc`, JSON-RPC is exposed at `/my-agent/rpc/`. Use
`<a2a:interface protocol="JSONRPC" path="/rpc"/>`.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Protocol</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>JSONRPC</p></li><li><p>HTTP_JSON</p></li></ul></div></div></td><td><div><div><p>Protocol binding (transport) that the interface uses.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path segment appended to the connection’s agent path for this binding.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Request Attributes

In A2A Connector 1.0 and later, this represents the HTTP request attributes for an A2A incoming
request. This type encapsulates the HTTP request metadata, including query parameters and headers,
that are received as part of an A2A protocol request.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Task Id</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The ID assigned to this task, either provided by the client or auto-generated by the connector.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Context Id</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The context ID assigned to this task, either provided by the client or auto-generated by the connector.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Query Params</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div><div><p>The query parameters received in the HTTP request.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div><div><p>The HTTP headers received in the request.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Version</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>HTTP version of the request. Former <code>http.version</code>.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Scheme</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>HTTP scheme of the request. Former <code>http.scheme</code>.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Method</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>HTTP method of the request. Former <code>http.method</code>.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Local Address</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Local host address from the server.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Remote Address</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Remote host address from the sender. Former <code>http.remote.address</code>.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Operation Name</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>SendMessage</p></li><li><p>SendStreamingMessage</p></li><li><p>GetTask</p></li><li><p>CancelTask</p></li><li><p>SubscribeToTask</p></li><li><p>CreateTaskPushNotificationConfig</p></li><li><p>GetTaskPushNotificationConfig</p></li><li><p>ListTaskPushNotificationConfigs</p></li><li><p>ListTasks</p></li><li><p>DeleteTaskPushNotificationConfig</p></li></ul></div></div></td><td><div><div><p>The A2A operation being processed (for example, GetTask or ListTasks). Populated by the binding layer so flow authors can distinguish which operation is running without parsing the JSON-RPC method themselves. The enum constants match the A2A spec section 3 wire names.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Tenant</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Optional tenant routing key from the A2A request. The tenant parameter is used for agent routing per A2A spec section 3.1.2, allowing a single endpoint URL to host multiple agent implementations. For example, <code>/assistant/message:send</code> routes to the "assistant" agent.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Client Certificate</strong></p></td><td><div><div><p><a href="#CertificateData">Certificate Data</a></p></div></div></td><td><div><div><p>Client certificate (if 2 way TLS is enabled). Former <code>http.client.cert</code>.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Certificate Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Basic Constraints</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Basic constraints extension value indicating if the certificate can be used to sign other certificates.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Critical Extension OI Ds</strong></p></td><td><div><div><p>Array of String</p></div></div></td><td><div><div><p>Object identifiers (OIDs) of critical extensions in the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Encoded</strong></p></td><td><div><div><p>Binary</p></div></div></td><td><div><div><p>The encoded form of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Extended Key Usage</strong></p></td><td><div><div><p>Array of String</p></div></div></td><td><div><div><p>Extended key usage extension indicating specific purposes for which the certificate public key can be used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Extensions</strong></p></td><td><div><div><p>Array of <a href="#CertificateExtension">Certificate Extension</a></p></div></div></td><td><div><div><p>Certificate extensions providing additional information about the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Issuer Alternative Names</strong></p></td><td><div><div><p>Array of <a href="#AlternativeNameData">Alternative Name Data</a></p></div></div></td><td><div><div><p>Alternative names for the certificate issuer.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Issuer DN</strong></p></td><td><div><div><p><a href="#PrincipalData">Principal Data</a></p></div></div></td><td><div><div><p>Distinguished name of the certificate issuer.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Issuer Unique ID</strong></p></td><td><div><div><p>Array of Boolean</p></div></div></td><td><div><div><p>Unique identifier for the certificate issuer.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Issuer X500 Principal</strong></p></td><td><div><div><p><a href="#X500PrincipalData">X500 Principal Data</a></p></div></div></td><td><div><div><p>X.500 principal information for the certificate issuer.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Usage</strong></p></td><td><div><div><p>Array of Boolean</p></div></div></td><td><div><div><p>Key usage extension indicating the purposes for which the certificate public key can be used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name associated with the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Non Critical Extension OI Ds</strong></p></td><td><div><div><p>Array of String</p></div></div></td><td><div><div><p>Object identifiers (OIDs) of non-critical extensions in the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Not After</strong></p></td><td><div><div><p>Date</p></div></div></td><td><div><div><p>Expiration date of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Not Before</strong></p></td><td><div><div><p>Date</p></div></div></td><td><div><div><p>Date from which the certificate is valid.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Public Key</strong></p></td><td><div><div><p><a href="#PublicKeyData">Public Key Data</a></p></div></div></td><td><div><div><p>Public key information from the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Serial Number</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Serial number of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Serial Number Object</strong></p></td><td><div><div><p><a href="#SerialNumberData">Serial Number Data</a></p></div></div></td><td><div><div><p>Serial number object containing detailed serial number information.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Sig Alg Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the signature algorithm used to sign the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Sig Alg OID</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Object identifier (OID) of the signature algorithm.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Sig Alg Params</strong></p></td><td><div><div><p>Binary</p></div></div></td><td><div><div><p>Parameters for the signature algorithm.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Signature</strong></p></td><td><div><div><p>Binary</p></div></div></td><td><div><div><p>Digital signature of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Subject Alternative Names</strong></p></td><td><div><div><p>Array of <a href="#AlternativeNameData">Alternative Name Data</a></p></div></div></td><td><div><div><p>Alternative names for the certificate subject.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Subject DN</strong></p></td><td><div><div><p><a href="#PrincipalData">Principal Data</a></p></div></div></td><td><div><div><p>Distinguished name of the certificate subject.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Subject X500 Principal</strong></p></td><td><div><div><p><a href="#X500PrincipalData">X500 Principal Data</a></p></div></div></td><td><div><div><p>X.500 principal information for the certificate subject.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Version</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Version number of the certificate format.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Certificate Extension

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Criticality</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Indicates whether the extension is critical. If <code>true</code>, the extension must be processed by the certificate user.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Oid</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Object identifier (OID) that uniquely identifies the extension type.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>Binary</p></div></div></td><td><div><div><p>The extension value in its encoded form.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Alternative Name Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The alternative name value.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>The type of alternative name.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Principal Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Common Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The common name (CN) component of the distinguished name.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The full distinguished name string representation.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### X500 Principal Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The X.500 distinguished name in string format.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Public Key Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The algorithm used for the public key (for example, RSA, DSA, EC).</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Encoded</strong></p></td><td><div><div><p>Binary</p></div></div></td><td><div><div><p>The encoded form of the public key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Modulus</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>The modulus value for RSA public keys.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Params</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Algorithm-specific parameters for the public key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Public Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The public key value in string representation.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Serial Number Data

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Serial Number</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>The serial number value of the certificate.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Redelivery Policy

Configures the redelivery policy for executing requests that generate errors. You can add a
redelivery policy to any source in a flow.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Max Redelivery Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum number of times to process a redelivered request unsuccessfully before returning a REDELIVERY_EXHAUSTED error.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Message Digest Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Secure hashing algorithm to use if the <strong>Use Secure Hash</strong> field is <code>true</code>. If the payload of the message is a Java object, Mule ignores this value and returns the value that the payload’s <code>hashCode()</code> returned.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Message Identifier</strong></p></td><td><div><div><p><a href="#RedeliveryPolicyMessageIdentifier">Redelivery Policy Message Identifier</a></p></div></div></td><td><div><div><p>One or more expressions that determine if a message was redelivered. This property can be set only if the <strong>Use Secure Hash</strong> field is <code>false</code>.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Object Store</strong></p></td><td><div><div><p>ObjectStore</p></div></div></td><td><div><div><p>Configures the object store that stores the redelivery counter for each message.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Redelivery Policy Message Identifier

Configures how to identify a redelivered message and how to find out when the message was
redelivered.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Use Secure Hash</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>true</code>, Mule uses a secure hash algorithm to identify a redelivered message.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Id Expression</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>One or more expressions that determine when a message was redelivered. You can set this property only if the <strong>Use Secure Hash</strong> field is <code>false</code>.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

## See Also

- [Using Anypoint Code Builder to Configure a Connector](../../connectors/introduction/intro-config-use-acb)
- [Using Studio to Configure a Connector](../../connectors/introduction/intro-config-use-studio)
- [A2A Connector Overview](./)
- [Salesforce Help](https://help.salesforce.com)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# Using Anypoint Studio to Configure A2A Connector 2.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).
2.  [Add the connector to your Mule project](#add-connector-to-project).
3.  [Configure a source for the connector’s flow](#configure-source).
4.  [Add a connector operation to the flow](#add-connector-operation).
5.  [Configure a global element for the connector](#configure-global-element).
6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](../../connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[A2A Connector Reference](a2a-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure Anypoint Connector for A2A (A2A
Connector):

1.  In Studio, select **File > New > Mule Project**.
2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add A2A Connector to your Mule project to automatically populate the XML code with the connector’s
namespace and schema location and add the required dependencies to the project’s `pom.xml` file:

1.  In **Mule Palette**, click **(X) Search in Exchange**.
2.  In **Add Dependencies to Project**, type `a2a` in the search field.
3.  Click **A2A Connector** in **Available modules**.
4.  Click **Add**.
5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met.

You can configure connector-specific sources, or other sources to use with A2A Connector, such as:

- **HTTP > Listener**

  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**

  Initiates a flow when a time-based condition is met

For example, to configure an **HTTP > Listener** source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.
2.  Drag **Listener** to the Studio canvas.
3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.
4.  Specify a value for the **Path** field.
5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of the **HTTP > Listener** source in the app.
6.  On the **General** tab, specify the connection information for the connector.
7.  On the **TLS** tab, optionally specify the TLS information for the connector.
8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.
9.  Click **Test Connection** to confirm that Mule can connect with the specified server.
10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for A2A Connector, follow these steps:

1.  In **Mule Palette**, select **A2A** and then select the desired operation.
2.  Drag the operation onto the Studio canvas, next to the source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target A2A system.

You can reference a configuration file that contains ANT-style property placeholders (recommended),
or you can enter your authorization credentials in the global configuration properties. For
information about the benefits of using property placeholders and how to configure them, see
[Anypoint Connector Configuration](../../connectors/introduction/intro-connector-configuration-overview).

To configure the global element for A2A Connector, follow these steps:

1.  Select the operation in the Studio canvas.
2.  On the properties screen for the operation, click the Add (**+**) icon to access the global
    element configuration fields.
3.  In the **General** tab, in **Connection**, select the authentication method to configure:
    - [Expression or Bean Reference](#expression-or-bean-ref)
    - [Basic Authentication](#basic_authentication)
    - [Digest](#digest)
    - [NTLM](#ntlm)

4.  On the **TLS** tab, optionally specify the TLS information for the connector.
5.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.
6.  Click **Test Connection** to confirm that Mule can connect with the specified server.
7.  Click **OK**.

### Expression or Bean Reference

Uses a DataWeave expression or bean reference to define authentication.

Enter the authentication information in the **Global Element Properties** screen:

1.  Select **General > Authentication > Expression or Bean reference** and enter the DataWeave
    expression.
2.  Click **OK**.

### Basic Authentication

Basic authentication is a simple (less secure) authentication scheme where the client sends the
username and password in plain text (encoded in Base64) in the HTTP Authorization header.

Enter the Basic authentication information in the **Global Element Properties** screen:

1.  Select **General > Authentication > Basic authentication** and enter or set the values for these
    fields:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Username</strong></p></td><td><div><div><p>Username used to initialize the session.</p></div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>Password used to authenticate the user.</p></div></div></td></tr><tr><td><p><strong>Preemptive</strong></p></td><td><div><div><p>If set to true, the client sends its authentication credentials (username and password) with the initial HTTP request to the server, rather than waiting for the server to challenge (401 Unauthorized) the client.</p></div></div></td></tr></tbody></table>

2.  Click **OK**.

### Digest

Digest is an HTTP authentication scheme that uses a challenge-response mechanism to avoid sending
passwords in plain text.

Enter the Digest authentication information in the **Global Element Properties** screen:

1.  Select **General > Authentication > Digest authentication** and enter or set the values for
    these fields:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Username</strong></p></td><td><div><div><p>Username used to initialize the session.</p></div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>Password used to authenticate the user.</p></div></div></td></tr><tr><td><p><strong>Preemptive</strong></p></td><td><div><div><p>If set to true, the client sends its authentication credentials (username and password) with the initial HTTP request to the server, rather than waiting for the server to challenge (401 Unauthorized) the client.</p></div></div></td></tr></tbody></table>

2.  Click **OK**.

### NTLM

NTLM authentication is a Microsoft authentication protocol used primarily in Windows environments.
It uses a challenge-response mechanism and is commonly used for network authentication.

Enter the NTLM authentication information in the **Global Element Properties** screen:

1.  Select **General > Authentication > Ntlm authentication** and enter or set the values for these
    fields:

    <table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Domain</strong></p></td><td><div><div><p>Name of the proxy domain.</p></div></div></td></tr><tr><td><p><strong>Workstation</strong></p></td><td><div><div><p>Name of the proxy workstation.</p></div></div></td></tr><tr><td><p><strong>Username</strong></p></td><td><div><div><p>Username used to initialize the session.</p></div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>Password used to authenticate the user.</p></div></div></td></tr><tr><td><p><strong>Preemptive</strong></p></td><td><div><div><p>If set to true, the client sends its authentication credentials (username and password) with the initial HTTP request to the server, rather than waiting for the server to challenge (401 Unauthorized) the client.</p></div></div></td></tr></tbody></table>

2.  Click **OK**.

## Configure Additional Connector Fields

After you configure a global element for A2A Connector, configure the other required fields for the
connector. The required fields vary depending on which connector operation you use.

## View the Application Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible on the Anypoint
  Studio console window.
- If you’re running the app using Mule from the command line, the app log output is visible in your
  operating system console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](../../connectors/introduction/introduction-to-anypoint-connectors)
- [Using Studio to Configure a Connector](../../connectors/introduction/intro-config-use-studio)
- [A2A Connector Reference](a2a-connector-reference)
- [Salesforce Help](https://help.salesforce.com)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# A2A Connector 2.0 Troubleshooting

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Anypoint Connector for A2A (A2A Connector), become familiar with the information
about performing general troubleshooting, addressing specific common errors, and interpreting
commonly thrown exception messages.

## Error Unmarshalling String JSON Payload into Type io.a2a.spec.Task. Cause: Argument "content" is Null

Likely cause:

- The payload maps to a task or message schema that expects a non-null text content field, but
  received `null`.

Resolution checklist:

- Ensure every text part includes a non-empty `text` value.
- Avoid sending `content: null` or equivalent nullable fields in message or task parts.
- Validate outbound JSON in Studio using connector metadata types before sending.
- Confirm your DataWeave transformation outputs JSON objects, not quoted JSON strings.

## Failed to Establish SSE Connection

Likely causes:

- Request is sent as a non-streaming `SendMessage` instead of `SendStreamingMessage` (JSON-RPC), or
  to `POST /message:send` instead of `POST /message:stream` (HTTP+JSON).
- The server app doesn’t include an active **A2A Server - Task Listener** flow.
- The agent card does not advertise `capabilities.streaming: true`.
- Reverse proxy or gateway strips `text/event-stream` semantics or closes long-lived HTTP
  connections.

Resolution checklist:

- Verify the method is `SendStreamingMessage` (JSON-RPC) or the request targets
  `POST /message:stream` (HTTP+JSON).
- Verify the server flow includes an **A2A Server - Task Listener**. The unified task listener
  serves streaming requests. There is no separate **A2A Server - On Task Stream Listener** in 2.0.
- Confirm the agent card advertises `capabilities.streaming: true`.
- Confirm HTTP 200 response with `Content-Type: text/event-stream`.
- Check timeout and keepalive settings in intermediary proxies and load balancers.

## A2A Server Config Errors Despite Correct Configuration

Likely causes:

- Invalid **Agent Path** to listener route binding.
- Card file path not found at runtime.
- Agent card JSON is malformed or missing capability metadata expected by clients.

Resolution checklist:

- Use `${app.home}/agent-card.json` when deploying to CloudHub.
- Validate card JSON syntax and required top-level fields.
- Confirm `<a2a:connection listenerConfig="…​" agentPath="…​"/>` references a valid
  `http:listener-config`.
- Check app startup logs for binding or card parsing errors before runtime requests.

## See Also

- [A2A Connector Examples](a2a-connector-examples)
- [A2A Connector Reference](a2a-connector-reference)
- [Salesforce Help](https://help.salesforce.com)
- [Known Issues](https://help.salesforce.com/s/issues)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# Upgrading and Migrating A2A Connector to Version 2.x

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Upgrade Anypoint Connector for Agent2Agent (A2A) (A2A Connector) to version 2.x.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>1.x</p></div></div></td><td><div><div><p>2.x</p></div></div></td></tr></tbody></table>

## Changes in 2.0

A2A Connector 2.0 uplifts the connector from A2A protocol 0.3.0 to A2A protocol 1.0.0. This is a
breaking change: wire method names, transport configuration, client and listener elements, and the
error palette all change. Review the changes below and update your apps before upgrading.

### Protocol and Transports

- A2A Connector now uses A2A protocol 1.0.0 instead of 0.3.0. Wire JSON-RPC method names change from
  slash-form to PascalCase. For example, `message/send` becomes `SendMessage`, `message/stream`
  becomes `SendStreamingMessage`, `tasks/get` becomes `GetTask`, `tasks/cancel` becomes
  `CancelTask`, and `tasks/resubscribe` becomes `SubscribeToTask`. Clients written against 0.3.0
  must update their method strings.
- An A2A Server can expose the same agent over both the JSON-RPC and the new HTTP+JSON transport
  bindings on a single connection (gRPC is out of scope for this release).
- You can now send a non-blocking `SendMessage` request by setting `returnImmediately` to `true` in
  the request configuration. The A2A Server acknowledges the request with the initial `Task` and
  continues processing asynchronously, and the **A2A Server - On Async Request Listener** source
  authors that initial response.
- At most one active `SendMessage` request (blocking, non-blocking, or streaming) can run against a
  given `taskId` at a time. A duplicate concurrent submission is rejected with `A2A:INVALID_REQUEST`
  ("Another SendMessage is already in flight for taskId {id}; retry once it completes."), which
  preserves the ordering of a task’s message history under concurrency.
- Tasks in a terminal state (`TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`, `TASK_STATE_CANCELED`, or
  `TASK_STATE_REJECTED`) are immutable. A `SendMessage` or `SendStreamingMessage` request against a
  terminal task is rejected with `A2A:UNSUPPORTED_OPERATION` ("Task has reached terminal state.").
- Task states now use the `TASK_STATE_*` constants (for example, `TASK_STATE_WORKING`,
  `TASK_STATE_COMPLETED`) instead of the lowercase 0.3.0 states.
- Streaming events use the A2A `StreamResponse` envelope shape with a single root key (`task`,
  `statusUpdate`, or `artifactUpdate`). There is no explicit `final` boolean. Finality is derived
  from `TaskStatus.state`.

### Server Configuration

- New required `<a2a:interfaces>` block on `<a2a:connection>`. One or more `<a2a:interface>` entries
  select the **Protocol** (`JSONRPC` or `HTTP_JSON`) and the **Path** segment appended to **Agent
  Path**. This is what enables multi-transport agents on a single connection.
- **Agent Path** on `<a2a:connection>` is now the base HTTP path for both the agent card (served at
  `{agentPath}/.well-known/agent-card.json`) and every configured interface
  (`{agentPath}{interface.path}`), rather than a single fixed agent endpoint.
- Startup validates a bijection between the configured `<a2a:interface>` entries and
  `agentCard.supportedInterfaces`. Mismatched `(protocol, path)` pairs fail initialization instead
  of surfacing as runtime 404s.
- Multi-tenant support: A single connection can serve multiple tenants at the same
  `{agentPath}{interface.path}` surface. Each request’s tenant (the `params.tenant` field on the
  request body, or `?tenant=` on GET/DELETE) is validated against
  `agentCard.supportedInterfaces[].tenant` and surfaced to flows as `attributes.tenant`.

### Client Configuration

- The **Client Connection** provider is replaced by two transport-specific connection providers,
  **Jsonrpc Client Connection** and **Http Json Client Connection**, chosen via the **Connection**
  dropdown in Studio. The transport must match one of the entries in the target
  `agentCard.supportedInterfaces`.
- The **Server Url** connection parameter is renamed to **Agent Url**, the base URL of the target
  A2A agent that the connector discovers via `{agentUrl}/.well-known/agent-card.json`.
- Every outbound request now sends `A2A-Version: 1.0` as a default header unless you override it via
  `<a2a:default-headers>`. If overridden, the value is validated to be a `1.x` version. Agent-card
  discovery (both connect-time and the **A2A Client - Get Card** operation) is exempt from this
  header.

### Sources

- The **A2A Server - Task Listener** source is now a unified listener. The same flow serves blocking
  `SendMessage`, non-blocking `SendMessage` (`returnImmediately=true`), and `SendStreamingMessage`
  over both JSON-RPC and HTTP+JSON, with no DSL change to distinguish the modes. The standalone
  **A2A Server - On Task Stream Listener** source is removed.
- The new **A2A Server - On Async Request Listener** source lets the flow customize the initial
  `Task` response emitted for streaming and non-blocking `SendMessage` requests. The flow receives
  the incoming `MessageSendParams` as payload and must return a `Task` (or raise an error to reject
  the request, or return a terminal or interrupted-state `Task` to short-circuit and skip the **A2A
  Server - Task Listener** flow entirely).
- The **A2A Server - Authorization Listener** source is replaced by the **A2A Server - Task
  Authorizer Listener** source, which uses a per-operation authorization contract and exposes the
  current operation name on `attributes.operationName`.
- The **A2A Server - On Push Notification Set Listener** source output payload is now the resolved
  `TaskPushNotificationConfig` JSON rather than the raw request params.
- SSE streams now close on terminal states (`TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`,
  `TASK_STATE_CANCELED`, `TASK_STATE_REJECTED`) and on the interrupted state
  `TASK_STATE_INPUT_REQUIRED`. `TASK_STATE_AUTH_REQUIRED` does not close the stream.

### Operations

- The new **A2A Client - List Tasks** operation is a client operation that returns the tasks from
  the target A2A server as a list (`Array of Any`) with a configurable streaming strategy,
  consumable from `<foreach>`.
- The new **A2A Server - Get Tasks** operation is a server-side batch read of stored tasks by ID.
  The flow supplies a **Task IDs** list and an optional **History Length** per task.
- The new **A2A Server - Get Tasks By Context** operation is a server-side read of every stored task
  that belongs to a **Context Id**, returned oldest first. The flow supplies a **Context Id** and an
  optional **History Length** per task.
- The new **A2A Server - Set Task Metadata** operation is a full-replace (no merge) of the persisted
  ``Task’s `metadata`` field. Pass `{}` to clear. It’s rejected for tasks in a terminal state.
- The **Task Resubscribe** operation is renamed to **A2A Client - Subscribe To Task**.
- The **A2A Client - Set Push Notification Config** operation is renamed to **A2A Client - Create
  Push Notification Config** (`<a2a:create-push-notification-config>`).
- The extended agent card is now fetched via a new **Use Extended Card** boolean parameter on the
  existing **A2A Client - Get Card** operation (defaults to `false`). No separate operation was
  added.
- The **A2A Client - List Push Notification Configs** operation now returns its results as a list
  (`Array of Any`) with a configurable streaming strategy, also consumable from `<foreach>`.
- The **A2A Server - Send Push Notification** operation now accepts a full
  `StreamingMessageResponse` payload (Task, Message, `TaskStatusUpdateEvent`, or
  `TaskArtifactUpdateEvent`).
- The **A2A Server - Update Task Status** and **A2A Server - Update Task Artifact** operations are
  uplifted to the A2A 1.0.0 event schemas, and each now declares only the concrete error types it
  raises.

### Errors

- Added: `A2A:CONTENT_TYPE_UNSUPPORTED`, `A2A:INVALID_AGENT_RESPONSE`,
  `A2A:EXTENDED_CARD_UNCONFIGURED`, `A2A:EXTENSION_SUPPORT_REQUIRED`, and `A2A:VERSION_UNSUPPORTED`.
- Updated: The `A2A:UNAUTHORIZED` JSON-RPC code moved from `-32005` to `-32099` (`-32005` is now the
  code for `CONTENT_TYPE_UNSUPPORTED`). Every error type now also carries a `google.rpc.ErrorInfo`
  reason string.
- Dropped: `A2A:JSON_RPC_ERROR` (the umbrella parent type), `A2A:METHOD_NOT_FOUND`, and
  `A2A:REQUEST_TIMEOUT`. Each operation now declares only the concrete error types it actually
  raises, so verify your error handling after upgrading.

## Requirements

Ensure your system meets the following compatibility requirements before you perform the upgrade:

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.9.8 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>17</p></td></tr><tr><td><p>A2A protocol</p></td><td><p>1.0.0</p></td></tr></tbody></table>

A2A Connector requires Mule Maven Plugin 4.6.0 or later to support Server-Sent Events (SSE) for
streaming operations. See [A2A Connector XML and Maven Support](a2a-connector-xml-maven).

## Upgrade Prerequisites

Before you perform the upgrade, create a backup of your files, data, and configuration in case you
need to restore to the previous version.

Because 2.0 is a breaking change, plan to update your Mule apps for the following before or
immediately after upgrading:

- Add the required `<a2a:interfaces>`/`<a2a:interface>` block and ensure **Agent Path** is set on
  every `<a2a:connection>`, and that your agent card’s `supportedInterfaces` matches it exactly.
- Replace the **Client Connection** provider with **Jsonrpc Client Connection** or **Http Json
  Client Connection**, and rename **Server Url** to **Agent Url**.
- Replace any **A2A Server - On Task Stream Listener** source with the unified **A2A Server - Task
  Listener** source.
- Replace the **A2A Server - Authorization Listener** source with the **A2A Server - Task Authorizer
  Listener** source.
- Update client method strings and event payloads to A2A 1.0.0 (PascalCase methods, `TASK_STATE_*`
  states, `StreamResponse` envelopes).
- Update error handling for the added, renamed, and dropped `A2A:` error types.

## Upgrade Steps

Follow these steps to perform the upgrade to version 2.x:

1.  In Anypoint Studio, create a Mule project.
2.  In the **Mule Palette** view, click **Search in Exchange**.
3.  In **Add Dependencies to Project**, enter `a2a` in the search field.
4.  In **Available modules**, select **A2A Connector** and click **Add**.
5.  Click **Finish**.
6.  Verify that the A2A Connector dependency version is 2.x in the `pom.xml` file in the Mule
    project.

Studio upgrades the connector automatically.

## Post-Upgrade Steps

After you install the latest version of the connector, verify that your app reflects the breaking
changes listed in [Upgrade Prerequisites](#upgrade-prerequisites): transport configuration, client
connection elements, unified task listener, authorizer listener, protocol 1.0.0 method names and
payloads, and the updated error palette.

## Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.
2.  Verify that there are no problems in the project `pom.xml` file.
3.  Confirm the app starts without an interface/agent-card bijection error.
4.  Test the connection to verify that the operations work.

## Revert the Upgrade

If it is necessary to revert to the previous version of A2A Connector, change the A2A Connector
dependency version in the project’s `pom.xml` file to the previous version.

You must update the project’s `pom.xml` file in Anypoint Studio.

## See Also

- [A2A Connector Reference](a2a-connector-reference)
- [A2A Connector Examples](a2a-connector-examples)
- [Introduction to Anypoint Connectors](../../connectors/introduction/introduction-to-anypoint-connectors)
- [Salesforce Help](https://help.salesforce.com)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# A2A Connector 2.0 XML and Maven Support

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Code Builder
or Studio:

- If you manually code a Mule runtime engine (Mule) app in XML, either from the Anypoint Code
  Builder or Studio XML editor, or from a text editor, you can access the connector from your app by
  adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
- If you add the connector in Anypoint Code Builder or Studio, the XML is automatically populated
  the code with the connector’s namespace and schema location and it also adds a dependency to the
  `pom.xml` file.

## Add a Namespace for the Connector

Paste the following code inside the `mule` tag of the header of your configuration XML:

```xml
http://www.mulesoft.org/schema/mule/a2a
http://www.mulesoft.org/schema/mule/a2a/current/mule-a2a.xsd
```

This example shows how the namespace statements are placed in the `<mule>` XML block:

```xml
<mule xmlns:a2a="http://www.mulesoft.org/schema/mule/a2a"
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns:file="http://www.mulesoft.org/schema/mule/file"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/file
	http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd
	http://www.mulesoft.org/schema/mule/http
	http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
	http://www.mulesoft.org/schema/mule/ee/core
	http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
	http://www.mulesoft.org/schema/mule/a2a
	http://www.mulesoft.org/schema/mule/a2a/current/mule-a2a.xsd">
```

## Add a POM File Dependency

The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app.
If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to
this connector:

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule4-a2a-connector</artifactId>
  <version>x.x.x</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information:

1.  Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/).
2.  In Exchange, click **Login** and supply your Anypoint Platform username and password.
3.  In Exchange, search for `a2a`.
4.  Select the connector.
5.  Click **Dependency Snippets** near the upper right of the screen.

## Update Maven Plugin Version

A2A Connector requires Mule Maven Plugin 4.6.0 or later to support Server-Sent Events (SSE) for
streaming operations. Update your project’s `pom.xml` file to include this version:

```xml
<properties>
    <app.runtime>4.9.8</app.runtime>
    <mule.maven.plugin.version>4.6.0</mule.maven.plugin.version>
</properties>
```

Without this update, you might encounter classloading errors related to
`org.mule.runtime.http.api.sse.server.SseClient` when deploying applications that use streaming
features.

## Next Step

After completing your namespace and pom.xml file, you can try the
[Examples](a2a-connector-examples).

## See Also

- [Introduction to Anypoint Connectors](../../connectors/introduction/introduction-to-anypoint-connectors)
- [Salesforce Help](https://help.salesforce.com)

---
product: A2A Connector
version: 2.0
is-latest-version: true
---

# A2A Connector 2.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Agent2Agent (A2A) (A2A Connector) facilitates inter-agent communication for
Large Language Model (LLM) agents and other applications by implementing the A2A protocol. This
enables agents to interact and delegate specialized tasks to other agents.

The A2A protocol is an open standard that supports:

- Capability discovery

  Identifies the functions and services offered by agents.

- Interaction negotiation

  Establishes communication methods between agents.

- Secure information exchange

  Transmits data between agent systems without requiring direct internal access.

A2A Connector provides Mule app integration that functions as both A2A servers and A2A clients.

For information about compatibility and fixed issues, see the A2A Connector Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- Anypoint Connectors
- Mule runtime engine (Mule)
- Elements and global elements in a Mule flow
- How to create a Mule app using Anypoint Code Builder or Anypoint Studio

Before creating an app, you must have:

- Java 17
- Apache Maven
- Anypoint Platform
- Credentials to connect with the target resource
- The latest versions of Anypoint Code Builder or Anypoint Studio

## Common Use Cases for the Connector

Build specialized domain specific agents each for Customer Service, Sales, or Marketing and have
other agents interact with these agents using the A2A protocol.

A2A Connector also provides distributed tracing support, enabling comprehensive monitoring and
observability of A2A interactions across distributed systems.

## Connection Types

A2A Connector supports these connection types:

- A2A server
- A2A client

## Next Step

After you complete the prerequisites, you’re ready to create an app and configure the connector
using [Anypoint Studio](a2a-connector-studio) or [Anypoint Code Builder](a2a-connector-acb).

## See Also

- [Anypoint Connectors Overview](../../connectors/introduction/introduction-to-anypoint-connectors)
- [Using Anypoint Code Builder to Configure a Connector](../../connectors/introduction/intro-config-use-acb)
- [Using Anypoint Studio to Configure a Connector](../../connectors/introduction/intro-config-use-studio)
- [A2A Connector Reference](a2a-connector-reference)
- [Salesforce Help](https://help.salesforce.com)