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 provides integration with the Qonto API, allowing users to interact with various Qonto resources. Specifically, for the "Request" resource and the "Get One" operation, the node retrieves a single request entity by its unique ID. This is useful when you need to fetch detailed information about a specific request in your Qonto account.
Common scenarios include:
- Fetching details of a particular payment or transaction request.
- Retrieving status or metadata of a specific request for auditing or processing.
- Integrating Qonto request data into workflows for reporting or notifications.
Example: You want to get the details of a request with ID 12345 to check its current status before proceeding with further automation steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: "API Key" |
| ID | The unique identifier of the request resource to retrieve. Must be provided as a string. |
Output
The node outputs an array of JSON objects representing the retrieved request(s). For the "Get One" operation on the "Request" resource, the output JSON contains the full details of the specified request, including all relevant fields returned by the Qonto API for that request.
If the node supports binary data (not indicated here), it would typically represent attachments or documents related to the request, but this is not evident from the provided code.
Dependencies
- Requires an active Qonto API key credential for authentication.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- No additional external dependencies are indicated beyond the Qonto API access.
Troubleshooting
- Error: Unknown resource — This occurs if an invalid or unsupported resource name is provided. Ensure the resource parameter is set to "request".
- Missing or invalid ID — The "ID" property is required; omitting it or providing an incorrect value will cause the API call to fail.
- Authentication errors — If the API key is missing, invalid, or lacks permissions, the node will fail to authenticate. Verify the API key credential setup.
- Timeouts or network issues — The node has a 30-second timeout; network problems may cause failures. Check connectivity and API availability.
- Continue on Fail — If enabled, errors during execution will be captured in the output JSON under an "error" field instead of stopping the workflow.