Qonto

Overview

This node integrates with the Qonto API to list cards associated with a specified organization. It allows users to retrieve card information filtered by their status (all, active, or inactive). This is useful for financial management workflows where you need to monitor or process card data programmatically, such as generating reports on active company cards or auditing inactive ones.

Practical examples:

• Automatically fetch all active cards of an organization to track spending.
• Retrieve all cards regardless of status to maintain an up-to-date inventory of issued cards.
• Filter cards by inactive status to identify cards that may need to be deactivated or replaced.

Properties

Output

The node outputs an array of card objects in the json output field. Each object represents a card belonging to the specified organization and includes details as returned by the Qonto API. The exact structure depends on the API response but typically includes card attributes such as card type, name, status, spending limits, currency, and other metadata.

No binary data output is produced by this operation.

Dependencies

• Requires access to the Qonto API.
• Requires an API authentication token configured in n8n either via OAuth2 or Login and Secret-Key method.
• No additional environment variables are explicitly required beyond standard API credentials.

Troubleshooting

• Missing or invalid Organization ID: The node requires a valid organization identifier. Ensure the ID is correct and corresponds to an accessible organization.
• Authentication errors: If authentication fails, verify that the provided credentials (API key or OAuth2 token) are valid and have sufficient permissions.
• Empty results: If no cards are returned, check if the organization actually has cards matching the filter criteria (status).
• API rate limits or connectivity issues: Network problems or API rate limiting can cause request failures. Retry after some time or check network settings.

Common error messages:

• Unauthorized or 401 errors indicate invalid or expired credentials.
• 404 errors may indicate incorrect resource paths or non-existent organization IDs.
• Validation errors if required parameters are missing or malformed.

Links and References

• Qonto API Documentation
• n8n Documentation on Credentials
• n8n Node Development Guide