Qonto icon

Qonto

Interact with Qonto API

Actions45

Overview

The node interacts with the Qonto API, specifically allowing users to manage various resources within a Qonto account. For the Label resource with the Get Many operation, it retrieves multiple label records from the Qonto system. This is useful for scenarios where you want to list or process all labels associated with your Qonto account, such as categorizing transactions or organizing financial data.

Practical examples include:

  • Fetching all labels to display in a dashboard.
  • Using labels to filter or tag transactions in subsequent workflow steps.
  • Synchronizing labels with another system for reporting or analytics.

Properties

Name Meaning
Authentication Method of authenticating with Qonto API. Options: API Key
Return All Whether to return all label results or limit the number returned. Boolean: true or false

Output

The output consists of an array of JSON objects representing label records retrieved from Qonto. Each object corresponds to a label and contains its properties as provided by the Qonto API.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the resource, but for labels, only JSON data is expected.

Dependencies

  • Requires an active connection to the Qonto API.
  • Needs an API key credential configured in n8n for authentication.
  • The node uses the Qonto API base URL, which can switch between sandbox and production environments based on credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Network connectivity problems may prevent reaching the Qonto API.
    • Request limits or permissions might restrict access to label data.
  • Error messages:

    • "Unknown resource: label" — indicates a misconfiguration or typo in the resource parameter.
    • API errors returned from Qonto (e.g., unauthorized, rate limited) will be passed through; ensure correct API key and permissions.
  • Resolutions:

    • Verify that the API key is correctly set up and has necessary permissions.
    • Check network connectivity and firewall settings.
    • Use the "Return All" option carefully to avoid large data loads that might time out.

Links and References

Discussion