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 perform operations related to external transfers. Specifically, the "Get One" operation under the "External Transfer" resource retrieves detailed information about a single external transfer by its unique ID.
Typical use cases include:
- Fetching the status and details of a specific external payment or transfer.
- Auditing or reconciling payments by retrieving transfer data on demand.
- Integrating Qonto external transfer data into workflows for reporting or further processing.
For example, a user might input an external transfer ID to retrieve its amount, beneficiary, status, and timestamps to verify if a payment was successfully processed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Currently supports: API Key |
| ID | The unique identifier of the external transfer to retrieve. This is a required string. |
Output
The node outputs JSON data representing the external transfer object retrieved from the Qonto API. This typically includes fields such as:
- Transfer ID
- Amount and currency
- Beneficiary details
- Status (e.g., pending, completed)
- Creation and execution dates
- Any relevant metadata associated with the transfer
No binary data output is indicated for this operation.
Dependencies
- Requires a valid 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 configuration.
- Network connectivity to Qonto's API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing transfer ID will cause errors; ensure the ID corresponds to an existing external transfer.
- Authentication failures due to incorrect or expired API keys.
- Network timeouts or connectivity problems when reaching Qonto's API.
Error messages:
"Unknown resource: externalTransfer"— indicates a misconfiguration in the resource parameter.- API error responses (e.g., 401 Unauthorized) suggest invalid credentials.
- Timeout errors may require increasing the timeout setting or checking network conditions.
To resolve these, verify the correctness of the transfer ID, confirm API key validity, and ensure stable internet access.
Links and References
- Qonto API Documentation — official API reference for external transfers and authentication.
- n8n documentation on creating custom nodes for further customization guidance.