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, messages, homework, absences, and grades. The node allows users to retrieve various types of information from their Librus account programmatically within n8n workflows.

Specifically, the Info - Get Timetable operation fetches the user's timetable data for a specified date range. This is useful for automating schedule retrieval, integrating school timetables into calendars, or triggering notifications based on upcoming classes.

Practical examples:

  • Automatically fetching and syncing your weekly class timetable to Google Calendar.
  • Creating reminders or alerts before each lesson starts.
  • Aggregating timetable data across multiple students or classes for administrative reporting.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method will be called instead of the default one for the selected operation.

Note: For the "Get Timetable" operation, additional parameters relevant to the timetable are used internally but not exposed in the provided properties JSON. These include:

  • ttFrom (start date of timetable range)
  • ttTo (end date of timetable range)

These are used to specify the date range for which the timetable is fetched.

Output

The node outputs an array of JSON objects representing timetable entries within the specified date range. Each object corresponds to a scheduled lesson or event in the timetable.

If the output is a single object, it is wrapped in an array for consistency.

No binary data is produced for the "Get Timetable" operation.

Dependencies

  • Requires valid Librus API credentials (login and password) configured in n8n.
  • Uses an internal Librus API client wrapper to communicate with the Librus service.
  • No additional external dependencies beyond the API access.

Troubleshooting

  • No supported method found error:
    This occurs if the node cannot find a matching method in the Librus API client for the requested resource and operation. Ensure that the resource and operation names are correct and supported. Using the "Custom method name" property incorrectly may also cause this.

  • Authentication errors:
    Verify that the Librus API credentials (login and password) are correctly set up and have sufficient permissions.

  • Empty or unexpected results:
    Check the date range parameters (ttFrom, ttTo) to ensure they cover the desired period. Also, confirm that the user account has timetable data available for those dates.

Links and References

Discussion