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 interacts with the Qonto API to retrieve data related to various financial and organizational resources. Specifically, for the Beneficiary - Get One operation, it fetches detailed information about a single beneficiary by its unique ID. This is useful in scenarios where you need to obtain precise details about a payment recipient or vendor stored in Qonto, such as verifying beneficiary information before initiating a transfer or auditing payment records.
Practical examples include:
- Retrieving beneficiary details to confirm bank account information before sending payments.
- Fetching beneficiary metadata for reporting or reconciliation purposes.
- Integrating beneficiary data into other workflows or systems that require up-to-date payee information.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Supported option: "API Key" |
| ID | The unique identifier of the beneficiary resource to retrieve. This is a required field. |
Output
The node outputs JSON data representing the beneficiary's details as returned by the Qonto API. This typically includes fields such as the beneficiary's name, bank account information, address, and any other metadata associated with that beneficiary in Qonto.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the beneficiary, but this operation focuses on JSON data only.
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, which varies depending on environment (sandbox or production).
- Network connectivity to Qonto's API servers.
Troubleshooting
Common issues:
- Invalid or missing API key: Ensure the API key credential is correctly set up and has sufficient permissions.
- Incorrect beneficiary ID: Verify that the provided ID exists and is correct; otherwise, the API will return an error.
- Network timeouts or connectivity problems: Check internet connection and firewall settings.
Error messages:
"Unknown resource: beneficiary": This indicates a misconfiguration or typo in the resource parameter; ensure "beneficiary" is selected.- API errors related to authentication or authorization usually indicate invalid credentials.
- Errors containing
"error": "<message>"in the output JSON indicate runtime failures; review the message for specifics.
Links and References
- Qonto API Documentation — Official API docs for understanding available endpoints and data structures.
- n8n Documentation — For general guidance on using credentials and configuring nodes.
