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 provides integration with the Qonto API, specifically allowing interaction with various Qonto resources. For the Membership resource and the Get Current operation, it retrieves information about the current membership details associated with the authenticated user or organization.
This node is beneficial in scenarios where you need to programmatically access membership data from Qonto, such as fetching current membership status, roles, or permissions for automation workflows involving financial or team management processes.
Practical examples include:
- Automatically retrieving membership details to verify user roles before performing sensitive operations.
- Integrating membership info into reporting dashboards.
- Triggering workflows based on membership changes or statuses.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating requests. Options: "API Key" |
Output
The node outputs JSON data representing the current membership information retrieved from Qonto. This typically includes details such as membership ID, user or organization identifiers, roles, permissions, and related metadata.
If the node supports binary data output (not indicated here), it would represent attachments or files related to membership, but this is not applicable for the "Get Current" operation.
Dependencies
- Requires an API key credential for authenticating requests to the Qonto API.
- The node uses the Qonto API base URL, which can switch between sandbox and production environments based on configuration.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Network timeouts or incorrect environment settings may prevent successful API calls.
- Unknown resource errors if the resource name is misspelled or unsupported.
Error messages:
Unknown resource: membership— indicates the resource parameter was not recognized; ensure "Membership" is selected correctly.- Authentication errors usually mention invalid credentials; verify the API key is correct and has necessary permissions.
- Timeout errors suggest network issues or slow API responses; consider increasing timeout settings or checking connectivity.
Links and References
- Qonto API Documentation — official API reference for detailed membership endpoints and data structures.
- n8n documentation on creating custom nodes for further customization guidance.