Qonto icon

Qonto

Consume Qonto API

Actions46

Overview

This node interacts with the Qonto API to list labels associated with an organization. It is useful for retrieving all labels or a limited number of labels that belong to a specific organization in Qonto. This can help users organize and categorize transactions or other entities by their labels.

A practical example: A user wants to fetch all labels from their Qonto organization to display them in a dashboard or use them as filters in further automation workflows.

Properties

Name Meaning
Authentication Method of authentication to use when connecting to Qonto API. Options: "Login and Secret-Key", "OAuth2".
Return All Whether to return all label results or only up to a specified limit (true/false).
Limit Maximum number of label results to return if "Return All" is false. Minimum value is 1.

Output

The output is a JSON array where each element represents a label object retrieved from the Qonto API. Each label object contains details about a label within the specified organization.

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 (qontoApiRequest and handleListing) to make authenticated HTTP requests to the Qonto API endpoints.

Troubleshooting

  • Authentication errors: Ensure that the correct authentication method is selected and that the corresponding credentials are properly configured in n8n.
  • Organization ID missing or invalid: The organizationId parameter must be provided and valid; otherwise, the API call will fail.
  • API rate limits: If many requests are made in a short time, the Qonto API might throttle requests. Consider enabling "Return All" carefully or limiting the number of results.
  • Network issues: Check network connectivity and proxy settings if requests fail unexpectedly.

Common error messages:

  • Unauthorized or 401 errors indicate invalid or missing credentials.
  • 400 Bad Request may indicate missing required parameters like organizationId.
  • 429 Too Many Requests indicates hitting API rate limits.

Links and References

Discussion