Toolzz Create User icon

Toolzz Create User

Create User Toolzz API

Overview

This node, Toolzz Create User, is designed to create a new user in the Toolzz platform via its API. It allows you to specify user details and select the environment (production, homologation, or release) where the user should be created. This node is useful for automating user onboarding processes, integrating with HR systems, or batch-creating users as part of workflow automation.

Example scenarios:

  • Automatically creating new users when they are added to an external system.
  • Bulk importing users into Toolzz from a spreadsheet.
  • Integrating Toolzz user creation into a larger onboarding workflow.

Properties

Name Type Meaning
Ambiente options Selects the target environment (Prod, Homol, Release) for the API request.
AccessToken string The access token used for authenticating API requests.
Nome string The name of the user to be created.
Email string The email address of the user to be created.
Escola ID string The school ID associated with the user.
Instituição ID string The institution ID associated with the user. (Not sent in the request body)
Confirme Sua Senha string Password confirmation. (Not sent in the request body)
Cpf string CPF (Brazilian individual taxpayer registry identification). (Not sent in the request)

Note: Only "Nome", "Email", "Escola ID", and "AccessToken" are actually used in the API request. Other fields are present but not utilized in this operation.

Output

The node outputs the JSON response returned by the Toolzz API after attempting to create the user. The structure of this output depends on the API's response, but typically includes information about the newly created user or error details if the creation failed.

Example output:

{
  "id": "12345",
  "name": "John Doe",
  "email": "john.doe@example.com",
  "escola_id": "67890",
  // ...other fields as provided by the API
}
  • No binary data is produced by this node.

Dependencies

  • External Service: Toolzz API endpoint (URL depends on selected environment).
  • Authentication: Requires a valid AccessToken for authorization.
  • n8n Configuration: No special credentials configuration; AccessToken is provided as a property.

Troubleshooting

Common issues:

  • Invalid AccessToken: If the access token is missing or invalid, the API will likely return an authentication error (e.g., 401 Unauthorized). Ensure the token is correct and has sufficient permissions.
  • Missing Required Fields: If "Nome", "Email", or "Escola ID" are empty, the API may reject the request with a validation error.
  • Incorrect Environment: Selecting the wrong environment may result in connection errors or unexpected data.
  • Unused Fields: Some input properties (Instituição ID, Confirme Sua Senha, Cpf) are not sent to the API and have no effect.

Error messages:

  • "401 Unauthorized": Check your AccessToken.
  • "400 Bad Request": Verify that all required fields are filled and correctly formatted.
  • "404 Not Found": Ensure the selected environment URL is correct and reachable.

Links and References

Discussion