Qonto

Interact with Qonto API

Actions45

Attachment Actions
- Get Many
- Get One
Beneficiary Actions
- Get Many
- Get One
Business Account Actions
- Get Many
- Get One
Card Actions
- Get Many
- Get One
Client Actions
- Get Many
- Get One
Client Invoice Actions
- Get Many
- Get One
Credit Note Actions
- Get Many
- Get One
External Transfer Actions
- Get Many
- Get One
Insurance Contract Actions
- Get Many
- Get One
Internal Transfer Actions
- Get Many
- Get One
Label Actions
- Get Many
- Get One
Membership Actions
- Get Many
- Get Current
Organization Actions
- Get
Quote Actions
- Get Many
- Get One
Request Actions
- Get Many
- Get One
SEPA Transfer Actions
- Get Many
- Get One
- Get Recurring Transfers
- Get Single Recurring Transfer
- Get Bulk Transfers
- Get Single Bulk Transfer
- Get SEPA Beneficiaries
- Get Single SEPA Beneficiary
Statement Actions
- Get Many
- Get One
Supplier Invoice Actions
- Get Many
- Get One
Team Actions
- Get Many
- Get One
Transaction Actions
- Get Many
- Get One

Overview

This node integrates with the Qonto API, specifically allowing users to interact with various Qonto resources. For the Team - Get One operation, it retrieves detailed information about a single team entity by its unique ID. This is useful in scenarios where you need to fetch specific team details for reporting, auditing, or further processing within an automation workflow.

Practical examples include:

Fetching a team's profile data to display in a dashboard.
Retrieving team information before updating or synchronizing with another system.
Using team details as part of a conditional logic branch in an automation.

Properties

Name	Meaning
Authentication	Method of authenticating with Qonto API. Options: `API Key`
ID	The unique identifier of the team resource to retrieve. This is a required string input.

Output

The node outputs JSON data representing the requested team resource. The structure typically includes all relevant fields describing the team, such as its ID, name, members, roles, and other metadata as provided by the Qonto API.

If the node encounters an error during execution (e.g., invalid ID), the output JSON will contain an error field with the error message.

No binary data output is indicated for 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:
- Invalid or missing team ID: The node requires a valid team ID; ensure the ID is correct and exists.
- Authentication failures: Verify that the API key credential is correctly set up and has necessary permissions.
- Network or timeout errors: Check network connectivity and API availability.
Error messages:
- "Unknown resource: team": Indicates the resource parameter was not recognized; ensure "team" is selected.
- Errors returned from the Qonto API (e.g., 404 Not Found) will be passed through in the output's error field.

To resolve errors, verify input parameters, credentials, and API status.

Links and References

Qonto API Documentation
n8n documentation on creating custom nodes

QontoInstall