Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing educational data such as timetables, absences, messages, homework, and grades. Specifically, the "Absence" resource with the "Get Timetable" operation fetches the user's timetable within an optional date range.

Typical use cases include:

  • Retrieving a student's or teacher's class schedule for a given period.
  • Automating timetable retrieval to sync with calendars or other scheduling tools.
  • Using timetable data to correlate with absences or events.

For example, a school administrator could automate fetching weekly timetables to distribute schedules via email or integrate them into a school management system.

Properties

Name Meaning
Custom method name (Optional) Overrides the default underlying API method to call. For "Get Timetable", this can specify a custom method instead of the standard one.

Note: The node also accepts parameters relevant to the timetable operation such as ttFrom and ttTo (date range), but these are not explicitly listed in the provided properties JSON. They are inferred from the code as input parameters for filtering the timetable.

Output

The output is a JSON array where each item represents timetable data retrieved from the Librus API. The structure depends on the API response but generally includes details about classes, times, subjects, and possibly locations.

If multiple items are returned, they are output as separate JSON objects in the array.

No binary data output is associated with the "Get Timetable" operation.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • Supports optional date range filtering (from and to parameters) to limit timetable data.
  • No additional external services or environment variables are required beyond the API credentials.

Troubleshooting

  • No supported method found error: If the specified resource-operation combination or custom method name does not match any available API methods, the node throws an error listing available methods. Ensure the correct resource, operation, and optionally custom method name are set.
  • Authentication errors: Invalid or missing API credentials will prevent successful connection. Verify that the login and password are correct.
  • Empty or unexpected results: If the date range filters (from, to) are incorrect or too restrictive, the timetable may return empty. Adjust or omit these parameters to broaden the query.
  • API changes: Since the node relies on the underlying Librus API client, any breaking changes in the API might cause failures. Check for updates to the node or client library if issues arise.

Links and References

Discussion