Actions12
- Transfer Actions
- Account Actions
- Agent Actions
Overview
This node enables interaction with an Account-to-Account (A2A) transfer service, allowing users to manage transfers between accounts programmatically. Specifically, the Transfer - Get Many operation retrieves a list of transfers with optional filtering by status and limiting the number of results.
Common scenarios where this node is beneficial include:
- Fetching recent transfer transactions for reconciliation or reporting.
- Monitoring transfers filtered by their current status (e.g., pending, completed).
- Integrating transfer data into dashboards or downstream workflows.
For example, a finance team could use this node to pull all completed transfers from the last day to update their accounting system automatically.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of transfer records to return. Must be at least 1. Default is 50. |
| Status | Filter transfers by their status. Options are: All (no filter), Cancelled, Completed, Failed, Pending. |
Output
The output is a JSON array where each item represents a transfer object retrieved from the API. Each transfer object typically includes details such as amount, currency, source and destination account IDs, reference, description, status, timestamps, and other metadata related to the transfer.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential and secret configured in n8n to authenticate requests against the A2A service.
- The base URL for the API must be set in the credentials.
- Uses HTTP requests with bearer token authorization and custom headers for authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Requesting too many records without respecting API limits may result in errors or truncated responses.
- Filtering by an unsupported status value will likely return no results or an error.
Error messages:
- Authentication errors usually indicate invalid API key or secret; verify credentials in n8n settings.
- Validation errors on parameters (e.g., limit less than 1) require adjusting input values accordingly.
- Network or connectivity errors suggest checking the base URL and network access.
Links and References
- Refer to your A2A service API documentation for detailed transfer object schema and supported query parameters.
- n8n documentation on HTTP Request node for understanding how authenticated requests are made.