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
SEPA Transfer → Get One
AI-generatedOverview
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 One operation, the node retrieves detailed information about a single SEPA transfer by its unique ID.
This is useful in scenarios where you need to fetch the status, details, or metadata of a specific SEPA transfer previously created or recorded in Qonto. For example, you might want to verify if a payment has been completed, check the beneficiary details, or audit transaction history.
Practical examples:
- Fetching a SEPA transfer's details after initiating it elsewhere.
- Retrieving transfer information to display in a dashboard or report.
- Validating transfer data before performing further automated processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Only option available: "API Key". |
| ID | The unique identifier of the SEPA transfer to retrieve. This is a required string input. |
Output
The output is an array of JSON objects representing the retrieved SEPA transfer(s). Each object contains all relevant fields returned by the Qonto API for that SEPA transfer, such as amount, currency, status, beneficiary details, execution date, and any other metadata associated with the transfer.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Qonto account with API access.
- Needs an API key credential configured in n8n to authenticate requests.
- The node uses the Qonto API endpoint, switching between sandbox and production URLs based on environment configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent SEPA transfer ID will likely result in an error from the API indicating the resource was not found.
- Missing or incorrect API key authentication will cause authorization failures.
- Network connectivity problems can lead to timeouts or request failures.
Error messages:
"Unknown resource: sepaTransfer": This would occur if the resource parameter is incorrectly set; ensure the resource name matches exactly.- API errors related to invalid ID or permissions will be passed through; check the ID value and API key validity.
Resolutions:
- Verify the SEPA transfer ID is correct and exists in your Qonto account.
- Confirm the API key is valid and has sufficient permissions.
- Check network connectivity and API endpoint accessibility.
Links and References
- Qonto API Documentation
- SEPA Transfer API Reference (for detailed field descriptions and usage)
- n8n documentation on creating API credentials
