A2A icon

A2A

A2A (Account to Account) transfers, account management, and Agent2Agent protocol communication

Overview

This node interacts with an Account-to-Account (A2A) transfer service, focusing on account management and transfers between accounts. Specifically, the Account - Get Balance operation retrieves the current balance of a specified account.

Common scenarios where this node is useful include:

  • Checking the available funds in a user or business account before initiating transactions.
  • Monitoring account balances for financial reporting or alerting.
  • Integrating balance checks into automated workflows that depend on account funds.

For example, a workflow could use this node to fetch the balance of a customer’s account before processing a payment or triggering a notification if the balance falls below a threshold.

Properties

Name Meaning
Account ID The unique identifier of the account whose balance you want to retrieve. This is a required string input.

Output

The output JSON contains the balance information of the specified account as returned by the A2A API. The exact structure depends on the external API response but typically includes fields such as:

  • Current balance amount
  • Currency type
  • Possibly other metadata related to the account balance

No binary data is output by this operation.

Dependencies

  • Requires an API key credential and secret configured in n8n to authenticate requests to the A2A service.
  • The node makes HTTP requests to the A2A API endpoint defined by the base URL in the credentials.
  • Proper network access to the A2A API server is necessary.

Troubleshooting

  • Invalid Account ID: If the provided Account ID does not exist or is malformed, the API may return an error. Verify the Account ID is correct.
  • Authentication Errors: Missing or incorrect API key/secret will cause authentication failures. Ensure credentials are properly set up.
  • Network Issues: Connectivity problems to the A2A API endpoint can cause request failures. Check network settings and API availability.
  • API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.

Error messages from the node typically reflect HTTP errors or JSON parsing issues from the API response. Review the error details to identify the root cause.

Links and References

  • Refer to your A2A service API documentation for detailed information about the /accounts/{accountId}/balance endpoint and response format.
  • n8n documentation on HTTP Request node for understanding how authenticated requests are made.

Discussion