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 interacts with the Qonto API to manage various financial resources. Specifically, for the SEPA Transfer resource and the Get Recurring Transfers operation, it retrieves a list of recurring SEPA transfers associated with the user's account.
This node is beneficial in scenarios where users want to automate the monitoring or processing of their scheduled SEPA payments, such as:
- Fetching all recurring SEPA transfers to reconcile scheduled payments.
- Integrating recurring transfer data into accounting or ERP systems.
- Automating notifications or workflows based on upcoming or past recurring transfers.
Example use case: A finance team wants to automatically pull all recurring SEPA transfers every day to update their cash flow forecasts.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: API Key |
| Return All | Whether to return all recurring SEPA transfers or limit the number of results returned. |
Output
The output is an array of JSON objects representing recurring SEPA transfers. Each object contains details about a single recurring transfer, such as identifiers, amounts, schedules, beneficiary information, and status.
If the node supports binary data output (not indicated here), it would typically represent attachments or documents related to transfers, but this is not applicable for this operation.
Dependencies
- Requires access to the Qonto API via an API key credential.
- The node expects the user to configure authentication credentials within n8n.
- Network connectivity to Qonto's API endpoints (sandbox or production depending on environment).
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Network timeouts or connectivity issues may prevent data retrieval.
- Requesting too many records without enabling "Return All" might result in truncated data.
Error messages:
"Unknown resource: sepaTransfer"— indicates a misconfiguration or typo in the resource parameter.- API errors from Qonto (e.g., 401 Unauthorized) suggest invalid credentials.
- Timeout errors indicate network or server responsiveness problems; retry or check connectivity.
Resolutions:
- Verify that the API key is correctly set up in n8n credentials.
- Enable "Return All" if you need the complete list of recurring transfers.
- Check network settings and ensure Qonto API endpoints are reachable.