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 manage memberships within an organization. Specifically, the "Create and Invite a New Membership" operation allows users to invite a new person (employee or accountant) to join their organization on Qonto by providing their email, name, role, and optionally assigning them to a team.
Common scenarios where this node is beneficial include:
- Automating onboarding workflows by programmatically inviting new team members.
- Managing organizational access control by assigning roles and teams during invitation.
- Integrating membership invitations into broader business processes such as HR or accounting automation.
Example use case:
- A company uses n8n to automate employee onboarding. When a new employee record is created in their HR system, this node sends an invitation to the employee's email to join the organization's Qonto account with the appropriate role and team assignment.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| Email address of the person being invited to join the organization. | |
| First_name | First name of the person being invited. |
| Last_name | Last name of the person being invited. |
| Role | Role assigned to the person being invited (e.g., employee, accountant). |
| Team_id | Unique identifier of the team to which the new membership will be assigned (optional). |
Output
The node outputs JSON data representing the response from the Qonto API after creating the membership invitation. This typically includes details about the newly created membership invitation such as the invited person's information, assigned role, team association, and invitation status.
No binary data output is produced by this operation.
Dependencies
- Requires valid authentication credentials for the Qonto API, either via an API key (login and secret-key) or OAuth2 token.
- The node depends on the Qonto API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the authentication credentials.
Troubleshooting
Common issues:
- Invalid or missing authentication credentials will cause authorization errors.
- Providing incomplete or invalid email or role fields may result in API validation errors.
- Specifying a non-existent team ID may cause the API to reject the request.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key or OAuth2 token is correctly set up and has necessary permissions.
- 400 Bad Request: Verify that all required fields (email, first name, last name, role) are provided and valid.
- 404 Not Found (for team_id): Ensure the team ID exists in the organization before assigning it.
- Network or timeout errors: Confirm network connectivity and Qonto API availability.