Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides an interface to a universal messaging gateway API, supporting multiple resources and operations. Specifically, for the Auth - Signup operation, it allows creating a new user account in the system. The first user created via signup typically becomes an administrator. This operation is useful when automating user registration workflows or integrating user management into larger automation processes.
Practical examples include:
- Automatically registering new users from a form submission.
- Creating admin users programmatically during initial setup.
- Integrating user signup as part of onboarding flows.
Properties
| Name | Meaning |
|---|---|
| Email address | The email address of the new user to register. |
| Password (min 8 chars, 1 uppercase, 1 number) | The password for the new user account. Must meet complexity requirements: minimum 8 characters, at least one uppercase letter, and one number. |
| Full name | Optional full name of the user. |
Output
The output JSON contains the response from the API after attempting to create the user account. This typically includes details about the newly created user such as user ID, email, roles, and possibly authentication tokens or status messages depending on the API's response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the messaging gateway API.
- The base URL for the API is taken from the credentials configuration.
- The node sends HTTP POST requests to the
/api/v1/auth/signupendpoint with query string parameters for email, password, and optionally name.
Troubleshooting
- Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Password not meeting complexity requirements may result in validation errors.
- Attempting to sign up with an already registered email will likely return an error.
- Error messages:
- "Unauthorized" or "Invalid API key": Check that the API key credential is correctly set up.
- "Password does not meet complexity requirements": Ensure the password has at least 8 characters, one uppercase letter, and one number.
- "Email already exists": Use a different email or handle duplicate registrations gracefully.
Links and References
- Refer to the messaging gateway API documentation for detailed signup endpoint behavior and response structure.
- General best practices for password security and user registration flows.