# A2A Connector - Full Documentation

# Using Anypoint Code Builder to Configure A2A Connector 1.1

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

**Open Beta Release**: The **cloud IDE is in open beta**. Any use of Anypoint Code Builder in its
beta state is subject to the applicable beta services terms and conditions, available from the IDE.

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 - Authorization Listener**

  A2A Server authorization listener that gates JSON-RPC methods which don’t have a dedicated
  listener. If the flow completes successfully, the request is authorized. If the flow raises an
  error, the request is denied and a `403 Forbidden` response is returned to the caller.

- **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.

- **A2A Server - On Task Stream Listener**

  Server-side listener for streaming task requests. Activates when clients send streaming requests
  to trigger server-side flows and enable real-time SSE event delivery. 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 **Task Listener** component on the canvas.
2.  (Optional) Click the edit icon to change the name of the **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>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><tr><td><p>Response</p></td><td><p>The response payload to return. Defaults to <code>#[payload]</code>.</p></td><td><p>No</p></td></tr><tr><td><p>Response Headers</p></td><td><p>HTTP response headers to include with the response.</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)
---

# A2A Connector 1.1 - Examples

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

This A2A server configuration uses an agent card JSON file that contains metadata about the agent.
Client A2A agents use this information to determine:

- When to use the agent (based on description and skills)
- Where to contact the agent (based on the url property)

## Configure an A2A Server

This is an example A2A server configuration using an absolute path:

```xml
<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config" doc:id="9fd53f88-b7c5-4175-9480-db313b27f9fd">
    <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="/" />
    <a2a:agent-card file="/Users/mule.user/Downloads/agent-card.json" />
</a2a:server-config>
```

When deploying your application to CloudHub, absolute or relative local paths may not resolve
correctly. To ensure the connector can locate your agent card in a deployed environment, use the
`${app.home}` variable:

```xml
<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config" doc:id="9fd53f88-b7c5-4175-9480-db313b27f9fd">
    <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="/" />
    <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> specifies the path to use to listen for requests.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td><code>a2a:agent-card</code> specifies the agent card. Use the <code>file</code> attribute to point to the absolute path of the JSON file on disk. For CloudHub use cases, if the file is located in the home directory of the CloudHub instance, you can reference it using <code>${app.home}/agent-card.json</code>.</td></tr></tbody></table>

## A2A Request Format

When sending requests to the **A2A Server - Task Listener** source from external clients (such as
Postman or other A2A agents), you must use the correct JSON-RPC format. Incorrectly formatted
requests result in unmarshalling errors such as:

```text
Error unmarshalling string json payload into type io.a2a.spec.SendMessageRequest. Cause: Invalid params
```

The minimum required JSON-RPC request format for the `message/send` method is:

```json
{
  "jsonrpc": "2.0",
  "method": "message/send",
  "id": "test-001",
  "params": {
    "message": {
      "kind": "message",
      "messageId": "550e8400-e29b-41d4-a716-446655440000",
      "role": "user",
      "parts": [
        {
          "kind": "text",
          "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 includes JSON schema definitions for `MessageSendParams` and other A2A objects. For
additional schema references, see the [A2A Java SDK](https://github.com/a2aproject/a2a-java).

## Write a Listener That Receives the A2A Request

This example shows how a listener is created. The user prompt that’s sent from the client agent is
extracted to a variable `user_prompt`:

```xml
<flow name="a2sfinancialagent" doc:id="fcd9c8be-94c2-4543-9eff-7f3e2b2f58fb" >
<a2a:task-listener doc:name="Task Listener" doc:id="c86ea98a-ae50-43be-a7ae-7bb60df17f8e" config-ref="A2A_Server">
	</a2a:task-listener>

	<set-variable value="#[payload.message.parts[0].text]" doc:name="Set task user prompt" doc:id="0f017d97-1761-4fc7-8b6b-13f3557a4b28" variableName="user_prompt"/>
</flow>
```

### Example Response

The response is formatted as an A2A task, which is then returned to the client:

```xml
<ee:transform doc:name="Transform Message" doc:id="32fd4cee-9380-4f0a-839d-880a7f25ea7f">
			<ee:message>
				<ee:set-payload><![CDATA[%dw 2.0
output application/json
var generatedId = uuid()
---
{
  "contextId": correlationId,
  "history": [
    {
      "contextId": correlationId,
      "kind": "message",
      "messageId": payload.message.messageId,
      "metadata": {},
      "parts": payload.message.parts,
      "role": "user",
      "taskId": generatedId
    }
  ],
  "id": generatedId,
  "kind": "task",
  "status": {
    "state": "submitted"
  },
  "validation_errors": []
}]]></ee:set-payload>
			</ee:message>
		</ee:transform>
```

## Mule App Example

This example shows how a financial A2A agent Mule app that can answer queries related to US
companies and their financial standings listens to A2A requests and passes the user prompt to an LLM
using MuleSoft Inference Connector.

You can paste this code into the Studio XML editor to quickly load the flow for this example into
your Mule app:

```xml
<flow name="sranana2aconnectorFlow" doc:id="fcd9c8be-94c2-4543-9eff-7f3e2b2f58fb" >
		<a2a:task-listener doc:name="Task Listener" doc:id="c86ea98a-ae50-43be-a7ae-7bb60df17f8e" config-ref="A2A_Server">
		</a2a:task-listener> #(1)
		<logger level="INFO" doc:name="Logger" doc:id="08d7c476-ed04-4775-be88-ed2c143851e6" message="Triggering MCP Tools"/> #(2)
		<set-variable value="#[payload.id]" doc:name="Set Task Id" doc:id="3b1702ea-88c1-4c06-a4ef-971ef8138504" variableName="task_id"/> #(3)
		<set-variable value='#[(payload.sessionId) default ""]' doc:name="Set Session Id" doc:id="d0790291-fb71-4a10-a953-1b68fa8bbb47" variableName="session_id"/> #(4)
		<set-variable value="#[payload.message.parts[0].text]" doc:name="Set task user prompt" doc:id="0f017d97-1761-4fc7-8b6b-13f3557a4b28" variableName="user_prompt"/> #(5)
		<ms-inference:mcp-tools-native-template doc:name="[MCP] Tooling" doc:id="55e0960a-5795-4223-adf4-dfb23365dc3e" config-ref="MuleSoft_Inference_Text_generation_config">
			<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> #(6)
			<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. If the user asks about anything other than stock market or financial aspects of public US companies, politely state that you cannot help with that topic and can only assist with companies financial data. Do not attempt to answer unrelated questions or use tools for other purposes.

Response Format: should be a JSON with 3 properties message, status (consist of "input_required", "completed", “error”) and sentiment with values (“Buy”, “Sell” or “Hold”) and reasoning (indicating in 2-3 sentences as to how the sentiment was decided)

Example queries: “Should I buy CRM stock?”, “Should I sell MSFT?”, “How is AAPL doing?”]]></ms-inference:instructions>
			<ms-inference:data ><![CDATA[#[payload.message.parts[0].text]]]></ms-inference:data>
		</ms-inference:mcp-tools-native-template>
		<set-variable value="#[payload.response]" doc:name="MCP Tooling Response" doc:id="60810200-5643-477c-8a45-76f1e0dcc9e0" variableName="mcp_tooling_results"/> #(7)
		<ms-inference:agent-define-prompt-template doc:name="Finance Agent" doc:id="b25e375b-f3be-45c1-a545-4f93690f98ce" config-ref="MuleSoft_Inference_Text_generation_config"> #(8)
			<ms-inference:template ><![CDATA[#["You are a specialized assistant for performing financial analysis based on stock market data using stock market symbols.

Use the following context to answer

Context: $(vars.mcp_tooling_results)"]]]></ms-inference:template>
			<ms-inference:instructions ><![CDATA[Your sole purpose is to answer questions about the financial information of US based companies. If the user asks anything other than stock market or financial aspects of public companies, politely state that you cannot help with that topic and can only assist with companies financial data. Do not attempt to answer unrelated questions or use tools for other purposes.

Response Format: Should be JSON with 3 properties, including message, status ("input_required", "completed", “error”), and sentiment with values (“Buy”, “Sell” or “Hold”) and reasoning (tell in 2-3 sentences how the sentiment was decided)

Example queries: “Should I buy CRM stock?”, “Should I sell MSFT?”, “How is AAPL doing?”]]></ms-inference:instructions>
			<ms-inference:data ><![CDATA[#[vars.user_prompt]]]></ms-inference:data>
		</ms-inference:agent-define-prompt-template>
		<ee:transform doc:name="Transform Message" doc:id="32fd4cee-9380-4f0a-839d-880a7f25ea7f"> #(9)
			<ee:message>
				<ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{
    "id": vars.task_id,
    "contextId": "context-" ++ vars.task_id,
    "status": {
      "state": "completed"
    },
    "artifacts": [
      {
        "name": "Answer",
        "artifactId": "artifact-" ++ vars.task_id,
        "parts": [
          {
            "kind": "text",
            "text": payload.response
          }
        ]
      }
    ],
    "kind": "task"
  }]]></ee:set-payload>
			</ee:message>
		</ee:transform>
	</flow>
```

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>The <code>a2a:task-listener</code> component acts as the entry point, waiting to receive a task from an A2A server. This task contains a user’s query about stock market data.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>The <code>logger</code> component outputs an informational message <code>Triggering MCP Tools</code> to the MuleSoft logs.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>The <code>set-variable</code> component extracts the ID from the incoming payload (the task received in step 1) and stores it in a flow variable named <code>task_id</code>.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>Another <code>set-variable</code> component extracts the <code>sessionId</code> from the payload. If <code>sessionId</code> isn’t present, it defaults to an empty string. This value is stored in a flow variable named <code>session_id</code>.</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td>This <code>set-variable</code> extracts the actual user query from the payload. Specifically, it takes the text from the first part of the message within the payload and stores it in a flow variable named <code>user_prompt</code>.</td></tr><tr><td><i data-value="6"></i><b>6</b></td><td>The <code>ms-inference:mcp-tools-native-template</code> configures an LLM to act as a specialized financial analysis assistant.</td></tr><tr><td><i data-value="7"></i><b>7</b></td><td>This <code>set-variable</code> component takes the response generated by the <code>ms-inference:mcp-tools-native-template</code> (from step 6) and stores it in a flow variable named <code>mcp_tooling_results</code>.</td></tr><tr><td><i data-value="8"></i><b>8</b></td><td>The <code>ms-inference:agent-define-prompt-template</code> component processes the results from the previous AI interaction to generate a user-friendly response.</td></tr><tr><td><i data-value="9"></i><b>9</b></td><td>The <code>ee:transform</code> (DataWeave transformation) component takes the <code>payload.response</code> from the previous AI interaction and transforms it into a structured JSON output.</td></tr></tbody></table>

## Configure the A2A Client to Call Other A2A Agents

This minimal flow listens for an A2A task and forwards the same payload to a remote agent using your
A2A client configuration.

```xml
<flow name="sranana2aconnectorFlow1" doc:id="973b8e26-66e6-449e-809d-9ae42125c693" >
	<a2a:task-listener doc:name="Task Listener" doc:id="974a49ae-98a7-4f1c-a216-1b66f0a77b71" config-ref="A2A_Server"/>
	<a2a:send-message doc:name="Send Message to A2A Agent" doc:id="1814db20-45b7-43e2-81e0-68211f1ae9af" config-ref="A2A_Client">
		<a2a:message ><![CDATA[#[payload]]]></a2a:message>
	</a2a:send-message>
</flow>
```

## Configure On Task Stream Listener (SSE) End to End

Use this pattern when your A2A server must return incremental task updates through SSE
(`message/stream`) instead of a single response (`message/send`).

### Server Configuration for Streaming

Use the same HTTP listener and A2A server pattern as non-streaming setups, with an agent card path
appropriate for your deployment (for example `${app.home}/agent-card.json` on CloudHub).

```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="/" />
    <a2a:agent-card file="${app.home}/agent-card.json" />
</a2a:server-config>
```

### Streaming Flow Example

The streaming process first emits a Task event, then emits intermediate status and artifact events,
and finally closes the stream with a final status event.

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

    <set-variable variableName="taskId" value="#[(payload.id) default uuid()]" />
    <set-variable variableName="contextId" value="#[(payload.contextId) default ('context-' ++ vars.taskId)]" />

    <a2a:update-task-status doc:name="Update Task Status - Working" config-ref="A2A_Server_config">
        <a2a:status-content><![CDATA[#[{
            id: vars.taskId,
            contextId: vars.contextId,
            kind: "status-update",
            status: { state: "working", message: { kind: "text", text: "Task accepted and processing started" } },
            final: false
        }]]]></a2a:status-content>
    </a2a:update-task-status>

    <a2a:update-task-artifact doc:name="Update Task Artifact" config-ref="A2A_Server_config">
        <a2a:artifact-content><![CDATA[#[{
            id: vars.taskId,
            contextId: vars.contextId,
            kind: "artifact-update",
            artifact: {
                artifactId: "artifact-" ++ vars.taskId,
                name: "partial-answer",
                parts: [{ kind: "text", text: "Here is an incremental result chunk." }]
            }
        }]]]></a2a:artifact-content>
    </a2a:update-task-artifact>

    <a2a:update-task-status doc:name="Update Task Status - Final" config-ref="A2A_Server_config">
        <a2a:status-content><![CDATA[#[{
            id: vars.taskId,
            contextId: vars.contextId,
            kind: "status-update",
            status: { state: "completed" },
            final: true
        }]]]></a2a:status-content>
    </a2a:update-task-status>
</flow>
```

### Expected SSE Event Format

The stream is delivered as standard server-sent events. Each event contains a JSON payload in
`data:`.

```text
event: task
data: {"id":"task-123","contextId":"context-task-123","kind":"task","status":{"state":"working"},"final":false}

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

event: status-update
data: {"id":"task-123","contextId":"context-task-123","kind":"status-update","status":{"state":"completed"},"final":true}
```

> [!NOTE] To close the SSE stream gracefully, set `final: true` on the last status update. If
> `final` isn’t emitted, clients can remain subscribed waiting for additional events.

### Error Handling Pattern 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-stream-listener doc:name="On Task Stream 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-update-content><![CDATA[#[{
                        id: (payload.id default uuid()),
                        contextId: (payload.contextId default "context-error"),
                        kind: "status-update",
                        status: { state: "failed", message: { kind: "text", text: error.description default "Unexpected server error" } },
                        final: true
                    }]]]></a2a:status-update-content>
                </a2a:update-task-status>
            </on-error-continue>
        </error-handler>
    </try>
</flow>
```

## JSON-RPC 2.0 Request and Response Patterns

The snippets below illustrate JSON-RPC for `message/send` and `message/stream`, a sample
completed-task result, and how fields map to Mule task payloads.

### Non-Streaming Request

Clients send this when invoking `message/send` and expecting one task result (not an SSE stream).

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

### Non-Streaming Response (Task Shape)

The JSON-RPC `result` object follows the A2A task structure, including `status`, `artifacts`, and
optional `history`.

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

### Streaming Request (`message/stream`)

Clients use this method and parameters when they open an SSE stream and consume multiple task,
artifact, and status events.

```json
{
  "jsonrpc": "2.0",
  "id": "req-stream-2001",
  "method": "message/stream",
  "params": {
    "message": {
      "kind": "message",
      "messageId": "6f4e31f8-5a4d-4a54-9fa3-31c9c0d10a1b",
      "role": "user",
      "parts": [
        {
          "kind": "text",
          "text": "Generate a step-by-step answer."
        }
      ]
    }
  }
}
```

### Mapping JSON-RPC Payload to `io.a2a.spec.Task`

In server flows, Mule payload fields map directly to task structures:

- `payload.id` maps to task ID.
- `payload.contextId` maps to context ID.
- `payload.message` carries the incoming user message.
- `payload.message.parts` contains content segments for extraction (for example,
  `payload.message.parts[0].text`).
- `payload.status` and `payload.artifacts` are used to build task updates in responses.

## Sample `agent-card.json` for Streaming and Push Notifications

Use this sample as a starting point for cards that advertise both SSE streaming and push
notification support:

```json
{
  "name": "Finance Streaming Agent",
  "description": "Handles financial analysis tasks with streaming progress updates and push notifications.",
  "url": "https://example.org/a2a",
  "provider": {
    "organization": "Example Org"
  },
  "version": "1.0.0",
  "capabilities": {
    "streaming": true,
    "pushNotifications": true
  },
  "skills": [
    {
      "id": "financial-analysis",
      "name": "Financial Analysis",
      "description": "Analyzes public company financial performance."
    }
  ],
  "defaultInputModes": ["text"],
  "defaultOutputModes": ["text"]
}
```

## Complete Mule App Example for Non-Streaming Tasks and Push Notifications

Use this full example when you want request-response processing with `message/send` and optional
push notification callbacks, without SSE streaming.

> [!NOTE] This pattern complements, but does not replace, the
> [Configure On Task Stream Listener (SSE) End to End](#configure-on-task-stream-listener-sse-end-to-end)
> section. Use this section for non-streaming flows, and the SSE section for incremental stream
> updates.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<mule
	xmlns:test="http://www.mulesoft.org/schema/mule/test"
	xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
	xmlns:a2a="http://www.mulesoft.org/schema/mule/a2a"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	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://www.mulesoft.org/schema/mule/test http://www.mulesoft.org/schema/mule/test/current/mule-test.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:agent-card>
			<a2a:json><![CDATA[{
  "name": "Stock Summarizer Agent",
  "url": "http://localhost:8082/v1/stock-summarizer",
  "version": "1.2.0",
  "protocolVersion": "0.3.0",
  "description": "Summarizes stock-related questions and supports task push notifications.",
  "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"]
    }
  ],
  "capabilities": {
    "streaming": false,
    "pushNotifications": true,
    "stateTransitionHistory": false
  },
  "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>

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

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

	<flow name="a2a-serverFlow">
		<a2a:task-listener config-ref="A2A_Server">
			<a2a:response>
				<a2a:response><![CDATA[#[payload]]]></a2a:response>
				<a2a:response-headers><![CDATA[#[%dw 2.0
output application/java
---
{
  "Content-Type": "application/json"
}]]]></a2a:response-headers>
			</a2a:response>
		</a2a:task-listener>

		<ee:transform doc:name="Chat Request Transformer">
			<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"><![CDATA[attributes.taskId]]></ee:set-variable>
				<ee:set-variable variableName="contextId"><![CDATA[attributes.contextId]]></ee:set-variable>
			</ee:variables>
		</ee:transform>

		<http:request method="POST" config-ref="HTTP_Request_configuration" 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 Transformer">
			<ee:message>
				<ee:set-payload><![CDATA[%dw 2.0
import * from dw::Runtime
output application/json
---
{
  id: vars.taskId,
  contextId: vars.contextId,
  status: {
    state: "completed",
    message: {
      role: "agent",
      parts: [
        {
          kind: "text",
          text: payload.choices[0].message.content
        }
      ],
      messageId: uuid(),
      kind: "message"
    }
  },
  artifacts: [
    {
      artifactId: uuid(),
      parts: [
        {
          kind: "text",
          text: payload.choices[0].message.content
        }
      ],
      index: 0
    }
  ],
  kind: "task"
}]]></ee:set-payload>
			</ee:message>
		</ee:transform>
	</flow>

	<flow name="pushNotificationValidationFlow">
		<a2a:push-notification-config-listener doc:name="On Push Notification Set Listener" config-ref="A2A_Server" />
		<logger level="INFO" message="Push notification config payload: #[payload]" />
	</flow>

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

	<flow name="a2a-clientSendTaskFlow">
		<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: "user",
    kind: "message",
    messageId: uuid(),
    parts: [
      {
        kind: "text",
        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>

</mule>
```

## See Also

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

# A2A Connector 1.1 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><p><a href="#ClientConnection">Client 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></tbody></table>

#### Connection Types

##### 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>Server Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL of the target A2A server.</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></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></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 - 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 - Send Message](#SendMessage)
- [A2A Client - Send Stream Message](#SendStreamMessage)
- [A2A Client - Set Push Notification Config](#SetPushNotificationConfig)
- [A2A Client - Task Resubscribe](#TaskResubscribe)

---

### 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>false</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></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 inbound endpoint.</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>Path at which the agent is available.</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></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 - Send Push Notification](#SendPushNotification)
- [A2A Server - Update Task Artifact](#UpdateTaskArtifact)
- [A2A Server - Update Task Status](#UpdateTaskStatus)

#### Associated Sources

- [A2A Server - Authorization Listener](#AuthorizationListener)
- [A2A Server - On Push Notification Set Listener](#PushNotificationConfigListener)
- [A2A Server - Task Listener](#TaskListener)
- [A2A Server - On Task Stream Listener](#TaskStreamListener)

## 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><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>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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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:INVALID_AGENT_CARD
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:UNAUTHORIZED

## 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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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></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>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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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>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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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><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>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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## 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><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>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:INTERNAL_ERROR
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## A2A Client - Set Push Notification Config

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

Sets or updates the 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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## A2A Client - Task Resubscribe

`<a2a:task-resubscribe>`

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><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>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:INTERNAL_ERROR
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## A2A Server - Send Push Notification

`<a2a:send-push-notification>`

Sends a push notification with the provided task or message payload. This operation allows sending
async updates at various stages or steps of a task, not just at the end. The notification message is
automatically wrapped in JSON-RPC format. This is a non-blocking operation that uses
CompletionCallback for async 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>The JSON notification message (task or message object). This value is automatically wrapped in JSON-RPC format.</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_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## A2A Server - Update Task Artifact

`<a2a:update-task-artifact>`

Updates a task artifact and broadcasts the update to all connected SSE clients.

### 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:INTERNAL_ERROR
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## A2A Server - Update Task Status

`<a2a:update-task-status>`

Updates a task status and broadcasts the update to all connected SSE clients. This operation only
works when there is an active streaming context, such as one established by the
[A2A Server - On Task Stream Listener](#TaskStreamListener) source.

> [!NOTE] When using this operation in a TaskStreamListener flow, the flow’s final payload is
> ignored. To close the SSE connection, include `final: true` in the TaskStatusUpdateEvent JSON
> payload.

### 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:INTERNAL_ERROR
- A2A:INVALID_PARAMS
- A2A:INVALID_REQUEST
- A2A:JSON_RPC_ERROR
- A2A:METHOD_NOT_FOUND
- A2A:PARSE_ERROR
- A2A:PUSH_NOTIFICATION_UNSUPPORTED
- A2A:REQUEST_TIMEOUT
- A2A:RETRY_EXHAUSTED
- A2A:SERVER_ERROR
- A2A:TASK_NOT_CANCELABLE
- A2A:TASK_NOT_FOUND
- A2A:UNAUTHORIZED
- A2A:UNSUPPORTED_OPERATION

## Sources

## A2A Server - Authorization Listener

`<a2a:authorization-listener>`

A2A Server authorization listener that gates JSON-RPC methods which don’t have a dedicated listener.
If the flow completes successfully, the request is authorized. If the flow raises an error, the
request is denied and a `403 Forbidden` response is returned to the caller.

### 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><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td></tr><tr><td><p><strong>Attributes Type</strong></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></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></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="#ResponseAttributes">Response 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><tr><td><p>Response</p></td><td><div><div><p>Any</p></div></div></td><td></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Response Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>HTTP response header.</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 - On Task Stream Listener

`<a2a:task-stream-listener>`

Server-side listener for streaming task requests. Activated when clients send streaming requests
(messages/stream) to trigger server-side flows and enable real-time SSE event delivery.

This source is a prerequisite for applications to support streaming. This source is to be used in
conjunction with [A2A Server - Task Listener](#TaskListener).

### 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></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></td><td><div></div></td><td><div><div><p>x</p></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>

### 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>Json Rpc Method</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The JSON-RPC method name from the A2A request (for example, <code>message/send</code>, <code>tasks/get</code>).</p></div></div></td><td><div></div></td><td><div><div><p>x</p></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)
---

# Using Anypoint Studio to Configure A2A Connector 1.1

> 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)
---

# A2A Connector 1.1 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 `kind: "text"` and 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 to `message/send` instead of `message/stream`.
- The server app doesn’t include an active `a2a:task-stream-listener` flow.
- Reverse proxy or gateway strips `text/event-stream` semantics or closes long-lived HTTP
  connections.

Resolution checklist:

- Verify the method is `message/stream`.
- Verify the server flow includes `a2a:task-stream-listener`.
- 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 `agentPath` 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)
---

# Upgrading and Migrating A2A Connector to Version 1.x

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

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

## Supported Upgrade Paths

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

## Changes in 1.0

- There is now a clear distinction in the naming between client and server operations/sources.
- A2A Connector now supports the new **A2A Client - Send Stream Message**, **A2A Client - Task
  Resubscribe**, **A2A Server - Send Push Notification**, **A2A Server - Update Task Artifact**, and
  **A2A Server - Update Task Status** operations.
- A2A Connector now supports the new **A2A Server - On Task Stream Listener** source.
- In the **A2A Server - On Push Notification Set Listener** source, **Response Timeout** is now
  **Push notification request timeout**, and **Response Timeout Unit** is now **Request Timeout
  Unit**.
- Push notifications on the A2A server side are no longer supported unless the **A2A Server - On
  Push Notification Set Listener** source is defined.
- The server now performs out-of-the-box context ID and task ID validations for tasks associated
  with the application.
- The server now supports task cancellation via the `tasks/cancel` method.
- A2A Connector now includes the `A2A:TASK_NOT_CANCELABLE` and `A2A:UNSUPPORTED_OPERATION` errors
  for all operations.
- A2A Connector no longer includes the `A2A:TASK_ALREADY_COMPLETED` error for all operations.
- A2A Connector now uses the A2A Java SDK for request and response validations, which enhances
  reliability.
- In the Server connection type, **Card** is replaced with either **Card Json** or **Card Path** to
  define the agent card.
- The **Agent Card**, **Agent Skill**, **Agent Capabilities**, **Agent Extension**, **Agent
  Provider**, **Security Requirement**, **Http Security Scheme**, **Api Key Security Scheme**,
  **Oauth2 Security Scheme**, **Oauth2 Flows**, **Implicit Oauth2 Flows**, **Oauth2 Scope**,
  **Password Oauth2 Flows**, **Client Credentials Oauth2 Flows**, **Authorization Code Oauth2
  Flows**, and **Open Id Connect Security Scheme** types are no longer supported.

## 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>0.3.0</p></td></tr></tbody></table>

## 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.

## Upgrade Steps

Follow these steps to perform the upgrade to version 1.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 1.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 error handling is updated to
work with the minor changes in error codes in this version of the connector.

## 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.  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

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

# A2A Connector 1.1 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)
---

# A2A Connector 1.1

> 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)