Toolzz Create User icon

Toolzz Create User

Create User Toolzz API

Overview

The Toolzz Create User node allows you to create a new user in the Toolzz platform via its API. This node is useful in automation scenarios where you need to programmatically onboard users, such as syncing users from another system, batch-creating accounts for a school, or automating user registration workflows.

Practical examples:

  • Automatically creating student accounts when they enroll in a course.
  • Syncing user data from an external CRM or database into Toolzz.
  • Bulk onboarding of teachers or staff by integrating with HR systems.

Properties

Name Type Meaning
Ambiente options Selects the environment (Production, Homologation, Release) to which the user will be created.
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 identifier of the school to which the user will be associated.
Cpf string The CPF (Cadastro de Pessoas Físicas, Brazilian individual taxpayer registry identification). (Note: Not used in the request body.)

Note:

  • The property "Cpf" is defined but not used in the actual API request.
  • There are references to "password" and "schools" parameters in the code, but these are not present in the provided properties list. The node expects "password" and "schools" (likely meant to be "Escola ID") as input.

Output

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

Example output (structure may vary):

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

Dependencies

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

Troubleshooting

Common issues:

  • Missing or invalid AccessToken: If the AccessToken is missing or incorrect, the API will likely return an authentication error (e.g., 401 Unauthorized).
  • Required fields missing: If required fields like "Nome", "Email", "Escola ID", or "password" are not provided, the API may return a validation error.
  • Incorrect environment selection: Choosing the wrong environment (Ambiente) could result in requests being sent to the wrong server, leading to unexpected results or failures.

Error messages:

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

Links and References

Discussion