Moscow School Simple

Simple Moscow School API integration with direct parameters
Join our community

Actions4

Overview

The "Moscow School Simple" node provides a straightforward integration with the Moscow School System API, allowing users to retrieve various types of student-related data by supplying direct parameters. It supports operations such as fetching basic student information, schedules, homework assignments, and marks within specified date ranges.

This node is beneficial in scenarios where educators, parents, or school administrators want to automate access to student data from the Moscow School System without dealing with complex API setups. For example, a parent could use this node to automatically fetch their child's daily schedule or homework assignments, or a teacher might retrieve marks for students over a certain period.

Specifically, the Get Student Info operation retrieves basic information about a student using an authentication token and the student's ID.

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 information you want to access.

Output

The output of the Get Student Info operation is a JSON object containing the student's basic information as returned by the Moscow School System API. This typically includes personal details associated with the student account.

The node does not output binary data; all responses are JSON-formatted data structures representing the requested information.

Example output structure (simplified):

{
  "id": "student-id",
  "name": "Student Name",
  "grade": "Grade Level",
  "class": "Class Identifier",
  // ... other student info fields
}

Dependencies

  • Requires a valid JWT authentication token issued by the Moscow School System.
  • Makes HTTP(S) requests to the Moscow School System API endpoints.
  • Optionally attempts to use a Russian proxy for requests, but falls back to direct connection if no reliable proxy is available.
  • Uses the axios library for HTTP requests.
  • No additional n8n credentials or environment variables are explicitly required beyond providing the authentication token.

Troubleshooting

  • Invalid or expired token: If the provided JWT token is invalid or expired, the API will reject requests. Ensure the token is current and correctly copied.
  • Invalid Student ID: Providing an incorrect or non-existent student ID will result in errors or empty responses.
  • Date format issues: Although not applicable for this operation, other operations require valid ISO date strings; invalid dates cause fallback to the current date.
  • Proxy errors: The node tries to use a Russian proxy but will log warnings and proceed with a direct connection if none are available. Proxy failures do not block execution.
  • Network or API errors: Network issues or API downtime will cause request failures. Error messages include HTTP status codes and response details to aid diagnosis.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion