Qonto

Overview

This node integrates with the Qonto API to manage various financial resources. Specifically, for the Card resource and the Retrieve Card Data View URL operation, it allows users to retrieve URLs that provide detailed views of card data within an organization. This can be useful for automating workflows that require access to card information or integrating card data views into other systems.

Common scenarios include:

• Automatically fetching card details for reporting or auditing.
• Integrating card data views into dashboards or internal tools.
• Triggering downstream processes based on card data availability.

Properties

Name	Meaning
Authentication	Method used to authenticate API requests. Options: "Login and Secret-Key", "OAuth2".

Note: The provided properties JSON only includes the authentication property. Other properties related to the Card resource and its operations (like organization ID, filters, etc.) are defined internally in the node but not listed here.

Output

The node outputs a JSON array where each item corresponds to the response from the Qonto API for the requested operation. For the Retrieve Card Data View URL operation, the output JSON contains the URL(s) or relevant card data view information returned by the API.

If multiple cards or data views are retrieved, the output will be an array of such objects.

The node does not explicitly handle binary data output for this operation.

Dependencies

• Requires access to the Qonto API.
• Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
• Uses helper functions (qontoApiRequest, handleListing) to make HTTP requests to the Qonto API.
• Uses UUID generation for idempotency keys when creating resources (not directly relevant for this read operation).

Troubleshooting

• Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials.
• Invalid parameters: Missing or incorrect organization IDs or card identifiers may cause API errors.
• API rate limits: Frequent calls might hit Qonto API rate limits; consider adding delays or error handling.
• Empty responses: If no cards match the filters, the output may be empty; verify filter criteria.
• Network issues: Connectivity problems can cause request failures; check network and proxy settings.

Common error messages typically come from the Qonto API and should be interpreted according to their content, e.g., unauthorized access, resource not found, or validation errors.

Links and References

• Qonto API Documentation
• n8n Documentation - Creating Custom Nodes