Moscow School Simple

Simple Moscow School API integration with direct parameters
Join our community

Actions4

Overview

The "Get Schedule" operation of the Moscow School Simple node fetches a student's schedule for a specific date from the Moscow School System API. This node is useful for educators, parents, or school administrators who want to programmatically retrieve daily schedules for students. For example, it can be used to automate reminders about classes or to integrate student schedules into other educational management systems.

Properties

Name Meaning
Authentication Token JWT token from Moscow School System used for authenticating API requests.
Student ID The unique identifier of the student whose schedule you want to retrieve.
Date The date (in YYYY-MM-DD format) for which the schedule is requested.

Output

The output JSON contains the schedule data retrieved from the Moscow School API for the specified student and date. The structure typically includes an array of schedule entries, each representing a class or event scheduled for that day. If the response is a stringified JSON array, the node attempts to parse each element into JSON objects.

No binary data is output by this operation.

Dependencies

  • Requires a valid JWT authentication token from the Moscow School System.
  • Makes HTTP(S) requests to the Moscow School API endpoints.
  • Optionally supports using a Russian proxy server for requests, but falls back to direct connection if no proxy is available.
  • Uses Axios library for HTTP requests.
  • No additional environment variables or n8n credentials are explicitly required beyond the provided token.

Troubleshooting

  • Invalid Date: If the provided date is invalid or missing, the node defaults to the current date and logs a warning.
  • Authentication Errors: If the JWT token is invalid or expired, the API request will fail. Ensure the token is correct and has not expired.
  • Proxy Issues: The node tries to use a free Russian proxy but throws an error to fall back to direct connection since free proxies are unreliable.
  • API Request Failures: Network issues or API downtime may cause request failures. The node logs detailed error information including HTTP status codes and response data.
  • Parsing Errors: Sometimes the API returns stringified JSON arrays; the node attempts to parse these but if parsing fails, raw strings are returned.

Links and References

Discussion