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 Card resource and the Get Many operation, it retrieves multiple card records from a Qonto account. This operation is useful when you want to list or analyze all cards associated with an account, such as for expense tracking, auditing, or reporting purposes.
Practical examples include:
- Fetching all company cards to monitor spending.
- Retrieving card details to sync with accounting software.
- Generating reports on card usage over time.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: "API Key" |
| Return All | Whether to return all card results or limit the number of returned cards (true/false). |
Output
The node outputs an array of JSON objects representing card data retrieved from the Qonto API. Each object corresponds to a single card and contains its details such as card ID, status, limits, owner information, and other relevant metadata.
If binary data were involved (e.g., card images), it would be included in a separate binary property, but this operation focuses on JSON data only.
Dependencies
- Requires access to the Qonto API.
- Needs an API key credential configured in n8n for authentication.
- The base URL switches between sandbox and production environments based on credential settings.
- Network connectivity to Qonto's endpoints is necessary.
Troubleshooting
- Common issues:
- Invalid or missing API key will cause authentication failures.
- Network timeouts if Qonto API is unreachable.
- Request limits exceeded if too many calls are made in a short period.
- Error messages:
"Unknown resource: card"— indicates a misconfiguration or typo in the resource parameter.- API errors returned by Qonto will be passed through; check the error message for details.
- Resolutions:
- Verify API key correctness and permissions.
- Ensure network access to Qonto endpoints.
- Use the "Return All" option carefully to avoid large data loads causing timeouts.
