Actions12
- Transfer Actions
- Account Actions
- Agent Actions
Overview
This node enables managing Account-to-Account (A2A) transfers within a financial or payment system. Specifically, the Transfer - Cancel operation allows users to cancel a previously initiated transfer by providing its unique Transfer ID. This is useful in scenarios where a transfer was made in error, needs to be stopped before completion, or requires revocation due to changed circumstances.
Practical examples include:
- Cancelling a scheduled payment that is no longer needed.
- Revoking a transfer if suspicious activity is detected.
- Stopping a transfer when the recipient account details were incorrect.
Properties
| Name | Meaning |
|---|---|
| Transfer ID | The unique identifier of the transfer to cancel. |
Output
The output JSON contains the response from the API after attempting to cancel the transfer. Typically, this will include details about the cancelled transfer such as its status and confirmation of cancellation.
Example structure (simplified):
{
"id": "string",
"status": "cancelled",
"amount": number,
"currency": "string",
"fromAccountId": "string",
"toAccountId": "string",
"reference": "string",
"description": "string"
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with appropriate permissions to manage transfers.
- The node uses HTTP requests authenticated via bearer token and secret headers.
- The base URL for the API and authentication credentials must be configured in the node's credentials settings.
Troubleshooting
- Invalid Transfer ID: If the provided Transfer ID does not exist or is malformed, the API may return an error indicating the transfer cannot be found. Verify the Transfer ID is correct.
- Permission Denied: Insufficient API permissions or invalid credentials can cause authorization errors. Ensure the API key and secret are valid and have rights to cancel transfers.
- Transfer Already Completed or Cancelled: Attempting to cancel a transfer that is already completed or previously cancelled may result in an error or no action. Confirm the current status of the transfer before cancelling.
- Network or API Errors: Connectivity issues or API downtime can cause request failures. Check network connectivity and API service status.
Links and References
- Refer to your A2A transfer API documentation for detailed information on transfer cancellation endpoints and expected responses.
- n8n HTTP Request node documentation for understanding how authenticated requests are made.