Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
The "Accept-invite" operation in the Auth resource allows a user to accept a project invitation and create an account using an invite token. This node is useful in scenarios where users are invited to join a project via an invitation link, and they need to register their account by providing the invite token, their full name, and a secure password. For example, when onboarding new team members or collaborators to a project, this operation facilitates seamless account creation tied to the invitation.
Properties
| Name | Meaning |
|---|---|
Invite token from invitation link (token) |
The unique token extracted from the invitation link that validates the invite. |
Full name (name) |
The full name of the user accepting the invitation; used for account creation. |
Password (min 8 chars, 1 uppercase, 1 number) (password) |
The password for the new account, which 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 attempting to accept the invitation and create the user account. Typically, this will include details about the newly created user or confirmation of successful acceptance. The exact structure depends on the API's response but generally includes user identification and authentication context.
This node does not output binary data.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the GateKit 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 containing the token, name, and password.
Troubleshooting
- Invalid or expired invite token: If the token is invalid or expired, the API will likely return an error. Ensure the token is copied correctly from the invitation link and has not expired.
- Password complexity errors: The password must be at least 8 characters long and include at least one uppercase letter and one number. Failure to meet these criteria may cause the API to reject the request.
- Missing required fields: All three properties (
token,name, andpassword) are required. Omitting any will result in an error. - API authentication issues: Ensure the API key credential is valid and has the necessary permissions to perform this operation.
Links and References
- GateKit API Documentation (hypothetical link for reference)
- General best practices for password security: https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#password-storage
If you need further details or examples on how to use this node within n8n workflows, feel free to ask!