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, specifically supporting various financial resources and operations. For the SEPA Transfer resource with the Get SEPA Beneficiaries operation, it retrieves a list of SEPA beneficiaries associated with the user's account. This is useful for automating workflows that require fetching beneficiary details for initiating SEPA transfers or managing payment recipients.
Practical examples include:
- Automatically retrieving and displaying all SEPA beneficiaries before creating a transfer.
- Synchronizing beneficiary data with other financial or CRM systems.
- Validating beneficiary information before processing payments.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with the Qonto API. Currently supports: API Key |
| Return All | Whether to return all SEPA beneficiaries or limit the number of results returned. Values: true (all), false (limited) |
Output
The node outputs an array of JSON objects representing SEPA beneficiaries. Each object contains detailed information about a beneficiary, such as their name, IBAN, and other relevant banking details required for SEPA transfers.
If binary data were involved, it would be summarized here, but this operation deals solely with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the Qonto API.
- The node uses the Qonto API base URL, which can switch between sandbox and production environments based on credentials configuration.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Network timeouts or connectivity issues may prevent successful API calls.
- Requesting too many records without setting "Return All" to true might result in truncated data.
Error messages:
"Unknown resource: sepaTransfer": Indicates the resource parameter was not recognized; ensure the resource name is correct.- API errors related to authentication typically indicate invalid or expired API keys.
- Rate limiting errors from the Qonto API may require implementing retry logic or reducing request frequency.
Links and References
- Qonto API Documentation
- SEPA Transfer Information
- n8n documentation on Creating Custom Nodes