Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
The node provides an operation to accept a user invite by using an invite token and setting a password. This is typically used in scenarios where a new user has been invited to a system and needs to confirm their invitation by providing the token they received and choosing a password. It automates the acceptance of user invitations, streamlining onboarding processes.
Practical examples:
- Automating user onboarding workflows where users receive invite tokens via email and then use this node to accept the invite and set their password.
- Integrating with systems that require programmatic acceptance of user invites as part of a larger automation or provisioning pipeline.
Properties
| Name | Meaning |
|---|---|
| Token | Accept invite token (string) required to validate and accept the user invite. Example: "eyJh...KmUk" |
| Password | Password of the user (string), entered securely, required to set the user's password upon accepting the invite |
Output
The node outputs JSON data representing the result of the invite acceptance process. This typically includes confirmation details such as success status, user information, or error messages if the invite token is invalid or expired.
No binary data output is indicated.
Dependencies
- Requires an API key or authentication token to connect to the backend service managing user invites.
- The node depends on external methods and routing logic imported from bundled dependencies (
./actions/routerand./methods). - Proper configuration of credentials and endpoint URLs within n8n is necessary for successful execution.
Troubleshooting
- Common issues may include invalid or expired invite tokens, resulting in errors during invite acceptance.
- Missing or incorrect passwords can cause validation failures.
- Authentication errors if the API key or credentials are not properly configured.
- Error messages will likely indicate token validity or permission issues; ensure the token is correct and the user has rights to accept invites.
- Network or connectivity problems with the backend service can also cause failures.
Links and References
- Refer to the official API documentation of the user management system for details on invite tokens and acceptance endpoints.
- n8n documentation on credential setup and HTTP request nodes for configuring API access.