A2A icon

A2A

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

Actions12

Overview

This node interacts with an Account to Account (A2A) service, focusing on account management operations under the "Account" resource. Specifically, the "Get Many" operation retrieves multiple accounts from the service, optionally filtered by account type and limited in number.

Common scenarios for this node include:

  • Fetching a list of user bank accounts for display or further processing.
  • Filtering accounts by type (e.g., checking or savings) to perform targeted financial operations.
  • Integrating account data into workflows that require bulk account information retrieval.

Practical example:

  • A finance dashboard workflow that periodically fetches all checking accounts up to a specified limit to update balances or transaction histories.

Properties

Name Meaning
Limit Max number of results to return. Must be at least 1. Defaults to 50.
Account Type Filter accounts by type. Options: All (no filter), Checking, Savings. Defaults to All.

Output

The output is a JSON array where each item represents an account object retrieved from the external A2A API. The exact structure depends on the API response but typically includes account details such as account ID, type, balance, and other metadata.

No binary data output is produced 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 GET requests to the /accounts endpoint of the configured base URL.
  • Proper network access to the A2A API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Authentication failures due to missing or invalid API credentials.
    • Network connectivity problems preventing access to the A2A API.
    • Invalid parameter values, e.g., setting Limit below 1.

  • Error messages:

    • Errors returned from the API will be surfaced, such as unauthorized access or bad request errors.
    • JSON parsing errors are unlikely here since the node expects JSON responses from the API.

  • Resolutions:

    • Verify API credentials and ensure they have the required permissions.
    • Check network/firewall settings to allow outbound calls to the API.
    • Ensure input parameters conform to expected types and constraints.

Links and References

  • No direct links available from the source code. Consult your A2A service provider's API documentation for detailed account endpoint specifications.

Discussion