QontoInstall

Overview

This node integrates with the Qonto API to perform operations related to internal transfers within a Qonto business account. Specifically, the Internal Transfer - Get One operation retrieves detailed information about a single internal transfer by its unique ID.

Typical use cases include:

• Fetching the status and details of a specific internal transfer for reconciliation or auditing.
• Automating workflows that require verification of internal fund movements between accounts.
• Integrating Qonto internal transfer data into other financial or ERP systems.

For example, a finance team could use this node to automatically pull details of an internal transfer after it is initiated, ensuring up-to-date records in their accounting software.

Properties

Output

The node outputs JSON data representing the internal transfer resource retrieved from Qonto. The structure typically includes fields such as:

• Transfer ID
• Amount and currency
• Source and destination account details
• Status of the transfer (e.g., pending, completed)
• Dates related to creation and execution
• Any relevant metadata or notes attached to the transfer

If the node encounters an error (e.g., invalid ID), the output JSON will contain an error field describing the issue.

No binary data output is produced by this operation.

Dependencies

• Requires a valid Qonto API key credential configured in n8n for authentication.
• Network access to Qonto's API endpoints (sandbox or production based on environment).
• No additional external dependencies beyond the Qonto API.

Troubleshooting

• Common Issues:

  • Providing an invalid or non-existent internal transfer ID will result in an error response.
  • Missing or incorrect API key credentials will cause authentication failures.
  • Network connectivity issues can prevent successful API calls.

• Error Messages:

  • "Unknown resource: internalTransfer" — indicates a misconfiguration or typo in the resource parameter.
  • API errors returned from Qonto (e.g., 404 Not Found if the ID does not exist) will be surfaced in the node output under the error field.

• Resolutions:

  • Verify the internal transfer ID is correct and exists in your Qonto account.
  • Ensure the API key credential is properly set up and has necessary permissions.
  • Check network connectivity and firewall settings allowing outbound requests to Qonto.

Links and References

• Qonto API Documentation — official API reference for internal transfers and other resources.
• n8n Documentation — general guidance on using credentials and configuring nodes.