Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The "Accept-invite" operation under the "Auth" resource allows a user to accept a project invitation and create an account. This is typically used when a user receives an invitation link containing a token, which they use to join a project by providing their full name and setting a password. It streamlines onboarding new users who have been invited to collaborate on a project.
Practical examples:
- A team member receives an email invitation to join a messaging project and uses this node to accept the invite and create their user account.
- Automating user onboarding workflows where invitations are sent externally, and acceptance is handled programmatically.
Properties
| Name | Meaning |
|---|---|
Invite token from invitation link (token) |
The unique token included in the invitation link that verifies the invite. Required to accept the invitation. |
Full name (name) |
The full name of the user accepting the invitation. Required for account creation. |
Password (min 8 chars, 1 uppercase, 1 number) (password) |
The password the user sets for their new account. Must meet complexity requirements: minimum 8 characters, at least one uppercase letter, and one number. |
Output
The output JSON contains the response from the API after successfully accepting the invitation and creating the user account. This typically includes user details and authentication context confirming the account creation.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the messaging platform's API.
- The base URL for the API is taken from the credentials configuration.
- The node sends a POST request to the
/api/v1/auth/accept-inviteendpoint with query parameters fortoken,name, andpassword.
Troubleshooting
- Invalid or expired token: If the invite token is invalid or has expired, the API will reject the request. Ensure the token is copied correctly from the invitation link and is still valid.
- Password complexity errors: The password must meet the specified complexity rules. Errors occur if the password is too short or lacks required character types.
- Missing required fields: All three properties (
token,name,password) are mandatory. Omitting any will cause the request to fail. - API authentication issues: Make sure the API key credential is properly set up and has permissions to accept invites.
Links and References
- No direct external links provided in the source code.
- For more information, consult the messaging platform's API documentation related to user invitations and authentication.