Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node interacts with the Qonto API to manage and retrieve information about beneficiaries within a financial organization. Specifically, the "Show Beneficiary" operation fetches detailed information about a single beneficiary by their unique identifier.
Common scenarios where this node is beneficial include:
- Retrieving beneficiary details for payment processing or verification.
- Integrating beneficiary data into workflows for accounting or compliance.
- Automating updates or audits of beneficiary records in financial systems.
For example, a user can input a beneficiary ID to get all associated details such as name, bank account information, and status, which can then be used to trigger further actions like payments or notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests. Options: "Login and Secret-Key", "OAuth2". |
| ID | The unique identifier of the beneficiary to retrieve. Required for the "Show Beneficiary" operation. |
Output
The output is a JSON object representing the beneficiary's details as returned by the Qonto API. This typically includes fields such as beneficiary name, IBAN, status, creation date, and other relevant metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires valid authentication credentials, either via login and secret key or OAuth2 token.
- The node uses helper functions to make HTTP requests to the Qonto API endpoints.
- No additional environment variables are explicitly required beyond the configured credentials.
Troubleshooting
- Invalid or missing beneficiary ID: Ensure that the "ID" property is provided and correctly formatted (usually a UUID).
- Authentication errors: Verify that the selected authentication method is properly configured with valid credentials.
- API request failures: Network issues or API downtime may cause errors; check connectivity and Qonto service status.
- Permission issues: The authenticated user must have permission to access beneficiary data.
- If the node throws an error message related to "not found" or "unauthorized," confirm the beneficiary ID exists and credentials have sufficient rights.