Toolzz List School And Classes icon

Toolzz List School And Classes

Get School and Classes of Toolzz API

Overview

The Toolzz List School And Classes node retrieves a list of schools and their associated classes from the Toolzz API. This node is useful in educational automation workflows where you need to fetch organizational data (schools and classes) for further processing, reporting, or integration with other systems.

Common scenarios:

  • Synchronizing school and class data into another system (e.g., CRM, LMS).
  • Generating reports based on current school/class structures.
  • Automating onboarding processes that require up-to-date school/class information.

Practical example:
You could use this node at the start of a workflow to pull all schools and classes, then iterate over them to send notifications, create user accounts, or update records elsewhere.

Properties

Name Type Meaning
AccessToken String The bearer token used for authenticating requests to the Toolzz API.
Ambiente Options Selects the environment (Prod, Homol, Release) which determines the base URL for the API.

Output

The node outputs a JSON array containing the response from the endpoint /api/schools of the selected Toolzz environment. Each item in the array represents a school and its associated classes as returned by the Toolzz API.

Output structure:

  • The exact fields depend on the Toolzz API's /api/schools response, but typically each object will include school details and an array/list of classes.

Example output (structure may vary):

[
  {
    "id": 123,
    "name": "School A",
    "classes": [
      {"id": 1, "name": "Class 1"},
      {"id": 2, "name": "Class 2"}
    ]
  },
  ...
]

Note: The node does not output binary data.

Dependencies

  • External Service: Requires access to the Toolzz API.
  • API Key: You must provide a valid AccessToken (bearer token) for authentication.
  • Network: The n8n instance must be able to reach the selected environment's URL.

Troubleshooting

Common issues:

  • Invalid AccessToken: If the provided token is invalid or expired, the API will likely return a 401 Unauthorized error. Ensure your token is correct and has not expired.
  • Incorrect Ambiente selection: Choosing the wrong environment may result in connection errors or unexpected data. Double-check the environment matches your intended use (production, testing, etc.).
  • Network issues: If n8n cannot reach the selected URL, check firewall settings and network connectivity.

Error messages:

  • 401 Unauthorized: Check your AccessToken.
  • ENOTFOUND or ECONNREFUSED: Verify the Ambiente URL and network access.
  • Unexpected token ... in JSON: The API did not return valid JSON; check if the endpoint is correct and accessible.

Links and References

Discussion