Overview
This node, Toolzz Show School And Classes, retrieves information about a specific school and its associated classes from the Toolzz API using a provided School ID. It is useful in educational automation workflows where you need to fetch up-to-date details about a school and its classes for reporting, synchronization, or integration with other systems.
Practical examples:
- Automatically updating a database with the latest class lists for a given school.
- Integrating school/class data into dashboards or learning management systems.
- Triggering notifications or actions based on changes in school/class structure.
Properties
| Name | Type | Meaning |
|---|---|---|
| AccessToken | String | The authentication token required to access the Toolzz API. |
| Ambiente | Options | Selects the environment (Prod, Homol, Release) to which the API request will be sent. |
| ID Da Escola | String | The unique identifier of the school whose data (and classes) should be retrieved. |
Output
The node outputs a JSON object containing the details of the specified school and its classes as returned by the Toolzz API. The exact structure depends on the API response, but typically includes fields such as school name, address, and an array of class objects.
Example output:
{
"id": "123",
"name": "Sample School",
"address": "123 Main St",
"classes": [
{
"id": "c1",
"name": "Class 1"
},
{
"id": "c2",
"name": "Class 2"
}
]
}
Note: The actual fields may vary depending on the Toolzz API.
Dependencies
- External Service: Requires access to the Toolzz API.
- API Key: A valid AccessToken is mandatory.
- n8n Configuration: No special credentials configuration; the AccessToken is provided directly as a property.
Troubleshooting
- Invalid AccessToken: If the AccessToken is missing or incorrect, the API will likely return an authentication error (e.g., 401 Unauthorized). Ensure the token is current and has the necessary permissions.
- Incorrect School ID: Providing a non-existent or malformed School ID may result in a 404 Not Found error.
- Environment Selection: Choosing the wrong environment (Ambiente) could lead to unexpected data or connection failures if the endpoint is not available.
- Network Issues: Connectivity problems between n8n and the selected API environment can cause timeouts or failed requests.