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
The node provides integration with the Qonto API, allowing users to interact with various financial resources managed by Qonto. Specifically, for the SEPA Transfer resource and the Get Single Recurring Transfer operation, the node retrieves detailed information about a single recurring SEPA transfer by its unique identifier.
This functionality is useful in scenarios where you need to fetch details of a specific recurring payment scheduled via SEPA (Single Euro Payments Area) transfers, such as auditing payments, verifying transfer schedules, or integrating transfer data into other workflows or reporting systems.
Example use cases:
- Automatically retrieving details of a recurring SEPA transfer to update accounting records.
- Monitoring recurring payments for compliance or reconciliation purposes.
- Triggering notifications or follow-up actions based on the status or details of a recurring transfer.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: API Key |
| ID | The unique identifier of the recurring SEPA transfer to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the details of the requested recurring SEPA transfer. The structure typically includes fields such as transfer amount, currency, schedule, beneficiary details, status, and other metadata related to the recurring transfer.
If the node supports binary data output (not indicated here), it would represent any associated files or documents related to the transfer, but this operation primarily returns structured JSON data.
Dependencies
- Requires an active Qonto account with API access.
- Requires an API key credential configured in n8n for authentication.
- Network access to Qonto's API endpoints (sandbox or production depending on configuration).
- No additional external dependencies beyond the Qonto API and n8n environment.
Troubleshooting
Common issues:
- Invalid or missing transfer ID: The node requires a valid ID; ensure the ID corresponds to an existing recurring SEPA transfer.
- Authentication errors: Verify that the API key is correctly set up and has sufficient permissions.
- Network or timeout errors: Check connectivity to Qonto API endpoints and increase timeout if necessary.
Error messages:
"Unknown resource: sepaTransfer": Indicates the resource name was not recognized; ensure the resource parameter is correctly set."The ID of the resource to retrieve is required": The ID property must be provided.- API error responses from Qonto will be passed through; check the message for details like invalid credentials or not found resources.
Links and References
- Qonto API Documentation
- SEPA Transfer Information
- n8n Documentation on Creating Custom Nodes