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 integrates with the Qonto API to manage clients within an organization. Specifically, the "Get a List of Clients" operation fetches a list of clients associated with a specified organization, optionally filtered by their status and creation date range. This is useful for scenarios where you need to retrieve client data for reporting, synchronization with other systems, or automated workflows that depend on client information.
Practical examples:
- Automatically fetching all active clients created in the last month to update a CRM system.
- Generating reports of inactive clients for follow-up actions.
- Filtering clients by creation date to analyze onboarding trends.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "Login and Secret-Key" or "OAuth2". |
| Organization ID | The unique identifier of the organization whose clients are to be fetched (required). |
| Status | Filter clients by their status. Options: "All", "Active", "Inactive". |
| Start Date | Fetch clients created after this date (optional). |
| End Date | Fetch clients created before this date (optional). |
Output
The output is a JSON array containing client objects retrieved from the Qonto API. Each object represents a client with its associated details as provided by the API. The exact structure depends on the API response but typically includes client identifiers, names, contact information, status, and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires either an API key credential ("Login and Secret-Key") or OAuth2 credentials configured in n8n.
- The node uses helper functions to handle API requests and pagination internally.
Troubleshooting
- Missing or invalid Organization ID: The operation requires a valid organization identifier. Ensure this property is set correctly.
- Authentication errors: If the API credentials are incorrect or expired, the node will fail to authenticate. Verify that the API key or OAuth2 token is valid and has necessary permissions.
- Empty results: If no clients match the filters, the output will be an empty array. Adjust filters or verify the organization's client data.
- API rate limits: Excessive requests may trigger rate limiting by Qonto. Implement retry logic or reduce request frequency if needed.
- Date format issues: Ensure that the start and end dates are provided in a valid datetime format recognized by the node.
Links and References
- Qonto API Documentation (for detailed API endpoints and data structures)
- n8n documentation on HTTP Request Node (conceptual understanding of API calls)