Overview
The "Moscow School Simple" node integrates with the Moscow School System API to retrieve various types of student-related data. It supports operations such as fetching basic student information, daily schedules, homework assignments, and marks within a date range. This node is useful for educators, parents, or school administrators who want to automate access to student data from the Moscow School System directly within their workflows.
Practical examples include:
- Automatically retrieving a student's homework for a specific date to send reminders.
- Fetching a student's schedule to integrate with calendar applications.
- Obtaining marks over a period to generate performance reports.
Properties
| Name | Meaning |
|---|---|
| Authentication Token | JWT token from Moscow School System used for authenticating API requests. |
| Student ID | Identifier of the student whose data you want to access. |
| Date | The specific date (YYYY-MM-DD) for which to get the schedule or homework (required for "Get Schedule" and "Get Homework" operations). |
Output
The node outputs JSON data corresponding to the selected operation:
- Get Student Info: Returns an object containing basic information about the student.
- Get Schedule: Returns an array or object representing the student's schedule for the specified date.
- Get Homework: Returns an array or object with homework assignments for the specified date.
- Get Marks: Returns an array or object with the student's marks within the specified date range.
If the response contains stringified JSON arrays, the node attempts to parse them into objects. The output does not include binary data.
Dependencies
- Requires an active internet connection to reach the Moscow School System API endpoints.
- Needs a valid JWT authentication token issued by the Moscow School System.
- Uses Axios HTTP client internally for making API requests.
- Optionally attempts to use a Russian proxy for requests but falls back to direct connection if none are available.
- No special n8n environment variables or credentials beyond the provided token input property are required.
Troubleshooting
- Invalid or expired token: If the JWT token is invalid or expired, API requests will fail. Ensure the token is current and correctly copied.
- Invalid dates: Providing an invalid date format will cause the node to fallback to the current date and log a warning. Use the YYYY-MM-DD format.
- Network issues or proxy failures: The node tries to use a Russian proxy but will fall back to direct connection if unavailable. Network restrictions or proxy failures may cause request errors.
- API request failures: Errors during API calls will be logged with details. Common causes include incorrect student IDs, network timeouts, or server-side issues.
- Parsing errors: If the API returns unexpected data formats, parsing might fail, but the node attempts to handle stringified JSON gracefully.
To resolve errors, verify input parameters, ensure network connectivity, and confirm the validity of the authentication token.