Moscow School Simple

Simple Moscow School API integration with direct parameters
Join our community

Actions4

Overview

This node integrates with the Moscow School System API to retrieve various types of student-related data. Specifically, the "Get Marks" operation fetches a student's marks within a specified date range. This is useful for parents or guardians who want to monitor academic performance over time, or for educational administrators tracking student progress.

Practical examples:

  • A parent wants to see all marks their child received between September 1 and December 31.
  • An educator needs to generate a report of student marks for a semester.
  • A school system automation workflow that collects marks data periodically for analysis.

Properties

Name Meaning
Authentication Token JWT token from Moscow School System used to authenticate API requests.
Student ID Identifier of the student whose marks are being requested.
From Date Start date (inclusive) for the marks retrieval range in ISO date-time format.
To Date End date (inclusive) for the marks retrieval range in ISO date-time format.

Output

The output is an array of JSON objects representing the marks retrieved from the Moscow School System API for the specified student and date range.

  • The exact structure depends on the API response but typically includes details such as subject, mark value, date, and possibly teacher comments.
  • If the API returns stringified JSON arrays, the node attempts to parse them into proper JSON objects.
  • No binary data is output by this node.

Example output snippet (conceptual):

[
  {
    "subject": "Mathematics",
    "mark": "5",
    "date": "2023-09-15",
    "comments": "Excellent work"
  },
  {
    "subject": "History",
    "mark": "4",
    "date": "2023-09-20"
  }
]

Dependencies

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

Troubleshooting

  • Invalid Dates: If the "From Date" or "To Date" inputs are invalid or missing, the node falls back to the current date, which may result in unexpected or empty results. Ensure dates are correctly formatted.
  • Authentication Errors: If the JWT token is invalid or expired, the API will reject requests. Verify the token's validity.
  • Proxy Issues: The node attempts to use a free Russian proxy but throws an error to fall back to direct connection since free proxies are unreliable. Network restrictions or firewall settings might affect connectivity.
  • API Response Parsing: Sometimes the API returns stringified JSON arrays; the node tries to parse these automatically. If parsing fails, raw strings may be returned.
  • Error Handling: On failure, the node logs detailed error messages. If "Continue On Fail" is enabled, errors are returned in the output JSON under an error field instead of stopping execution.

Links and References

Discussion