Qonto icon

Qonto

Interact with Qonto API

Actions45

Overview

The node provides integration with the Qonto API, allowing users to interact with various financial resources managed by Qonto. Specifically, for the Internal Transfer resource with the Get Many operation, the node retrieves multiple internal transfer records from a Qonto account.

This operation is useful in scenarios where you want to fetch a list of internal transfers for reconciliation, reporting, or auditing purposes. For example, a finance team could use this node to automatically pull all internal transfer transactions within a certain period and analyze cash flow between accounts.

Properties

Name Meaning
Authentication Method of authenticating with Qonto API. Currently supports: API Key
Return All Whether to return all internal transfer records or limit the number of results returned.
  • Authentication: Selects the authentication method; only "API Key" is available.
  • Return All: If set to true, the node fetches all available internal transfer records. If false, it limits the output to a predefined maximum (not specified here).

Output

The node outputs an array of JSON objects representing internal transfer records retrieved from Qonto. Each object corresponds to one internal transfer entry with fields as defined by the Qonto API response schema for internal transfers.

No binary data output is indicated for this operation.

Dependencies

  • Requires a valid API key credential for authenticating requests to the Qonto API.
  • The node uses the Qonto API base URL, which switches between sandbox and production environments based on the credential environment setting.
  • Network connectivity to Qonto's API endpoints is necessary.

Troubleshooting

  • Unknown Resource Error: If the resource parameter is incorrect or missing, the node throws an error stating "Unknown resource". Ensure the resource is set to "internalTransfer".
  • API Authentication Failures: Invalid or missing API keys will cause authentication errors. Verify that the API key credential is correctly configured.
  • Rate Limits or Timeouts: The node sets a 30-second timeout for API calls. Large data requests might time out or hit rate limits. Use the "Return All" property judiciously.
  • Partial Failures: If the node is configured to continue on failure, errors during execution will be captured in the output JSON under an error field instead of stopping the workflow.

Links and References

Discussion