Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The node interacts with the Qonto API to perform various operations on different resources. Specifically, for the Team resource with the Get Many operation, it retrieves multiple team records from the Qonto platform. This is useful when you want to list or process information about multiple teams within an organization managed in Qonto.
Common scenarios include:
- Fetching all teams or a subset of teams for reporting or synchronization.
- Integrating team data into other systems or workflows.
- Automating audits or reviews of team structures and memberships.
Example: You might use this node to pull all teams associated with your Qonto account to display them in a dashboard or to trigger notifications based on team changes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: API Key |
| Return All | Whether to return all available team records (true) or limit the number of results (false). |
Output
The output consists of JSON objects representing team data retrieved from Qonto. Each item corresponds to a team record with its properties as returned by the Qonto API.
If binary data were involved (not indicated here), it would typically represent files or attachments related to the team, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authentication with the Qonto API.
- The node uses the Qonto API endpoints, which may require configuration of environment variables or credentials within n8n to specify sandbox or production environments.
- Network access to Qonto's API servers is necessary.
Troubleshooting
- Unknown resource error: If the resource parameter is incorrect or missing, the node will throw an "Unknown resource" error. Ensure the resource is set to "team".
- Authentication failures: Incorrect or missing API key will cause authentication errors. Verify that the API key credential is correctly configured.
- Timeouts or network issues: The node has a 30-second timeout; slow or unreachable API endpoints can cause failures.
- Partial data retrieval: If "Return All" is false, only a limited number of teams are returned. To get complete data, enable "Return All".