Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node integrates with the Qonto API to retrieve information about SEPA transfers, specifically allowing you to get details of a single bulk SEPA transfer by its ID. It is useful in financial automation workflows where you need to fetch detailed data about specific bulk SEPA transfers made through Qonto accounts.
Practical examples include:
- Automatically retrieving and processing details of a particular bulk SEPA transfer for reconciliation or reporting.
- Triggering downstream actions based on the status or contents of a specific bulk SEPA transfer.
- Auditing or verifying payment batches by fetching their metadata programmatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Currently supports: API Key |
| ID | The unique identifier of the bulk SEPA transfer resource to retrieve (required string) |
Output
The node outputs JSON data representing the details of the requested single bulk SEPA transfer. This typically includes all relevant fields returned by the Qonto API for that transfer, such as amounts, beneficiary details, status, timestamps, and any metadata associated with the bulk transfer.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Qonto API key credential configured in n8n for authentication.
- Network access to Qonto's API endpoints (sandbox or production depending on environment).
- The node internally uses the Qonto API base URL which switches between sandbox and production based on credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing an incorrect or non-existent bulk transfer ID will result in errors indicating the resource was not found.
- Network timeouts or connectivity issues can prevent successful API calls.
Error messages:
"Unknown resource: sepaTransfer"— indicates a misconfiguration or typo in the resource parameter; ensure "sepaTransfer" is selected.- API error messages from Qonto (e.g., 401 Unauthorized, 404 Not Found) should be checked against the provided ID and API key validity.
Resolutions:
- Verify the API key credential is correctly set up and has necessary permissions.
- Double-check the bulk transfer ID for correctness.
- Ensure network connectivity and no firewall restrictions blocking API requests.
Links and References
- Qonto API Documentation — official docs for understanding available endpoints and data structures.
- SEPA Transfer Concepts — background on SEPA payments and bulk transfers.
