Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node integrates with the Qonto API to retrieve detailed information about an organization and its associated bank accounts. Specifically, for the "Organization" resource and the "Get Organization and Its Bank_accounts" operation, it fetches the organization's data including its bank accounts. It optionally includes external connected accounts beyond the default Qonto accounts.
This node is useful in scenarios where you need to synchronize or display comprehensive organizational financial data within workflows, such as generating reports, auditing accounts, or integrating with accounting systems.
Example use cases:
- Automatically fetching an organization's bank account details for reconciliation.
- Including external linked accounts to get a full financial overview.
- Triggering downstream processes based on updated organization or bank account info.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| Include_external_accounts | Boolean flag indicating whether to include connected external accounts along with Qonto accounts. |
Output
The node outputs JSON data representing the organization's details along with its bank accounts. The structure typically includes fields describing the organization (such as name, ID, etc.) and an array of bank accounts associated with it. If the Include_external_accounts property is set to true, the output will also contain external connected accounts.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Qonto API.
- Requires authentication credentials configured in n8n, either via login and secret key or OAuth2.
- Uses internal helper functions to make authenticated HTTP requests to Qonto's endpoints.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided.
- API request failures: Network issues or invalid parameters can cause errors. Verify connectivity and parameter correctness.
- Empty or incomplete data: If external accounts are expected but not returned, check that
Include_external_accountsis set to true. - Rate limits: Qonto API may enforce rate limits; handle errors accordingly or add retry logic.