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 interacts with the Qonto API to retrieve detailed information about a single membership within an organization. It is useful in scenarios where you need to fetch specific membership data, such as user roles, team assignments, or membership status, for further processing or automation workflows. For example, you might use this node to verify membership details before granting access to resources or to synchronize membership data with other systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| ID | The unique identifier of the membership to retrieve details for. |
Output
The node outputs a JSON object containing the detailed information of the specified membership. This typically includes membership attributes such as email, first name, last name, role, team association, and other relevant membership metadata as returned by the Qonto API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires either an API key credential (Login and Secret-Key) or OAuth2 authentication configured in n8n.
- Uses internal helper functions to make authenticated HTTP requests to the Qonto API endpoints.
Troubleshooting
Common issues:
- Invalid or missing membership ID will cause the API request to fail.
- Authentication errors if credentials are not properly set up or expired.
- Network connectivity issues preventing access to the Qonto API.
Error messages:
- Errors from the Qonto API will be propagated, such as "Not Found" if the membership ID does not exist.
- Authentication failures will return authorization errors; ensure credentials are valid and have necessary permissions.
Resolution tips:
- Double-check the membership ID input for correctness.
- Verify that the selected authentication method is correctly configured in n8n.
- Ensure network access to the Qonto API endpoint is available.
Links and References
- Qonto API Documentation (for detailed API endpoint info)
- n8n documentation on API Credentials and HTTP Request Node for general guidance on API integrations.