Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to retrieve calendar-related data, specifically allowing users to get a timetable for a specified date range. It is useful in educational or organizational contexts where schedules need to be programmatically accessed and processed. For example, a school administrator could use this node to automatically fetch and display class timetables for students or teachers within a given period.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks).
From Date Start date of the timetable range in YYYY-MM-DD format.
To Date End date of the timetable range in YYYY-MM-DD format.

Output

The output is a JSON array where each element represents an entry from the timetable retrieved from the Librus API. The exact structure depends on the API response but typically includes details such as dates, times, subjects, and possibly locations or notes related to scheduled events.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Librus API.
  • The node uses an internal client wrapper to communicate with the Librus API.
  • No additional environment variables are explicitly required beyond the API credentials.

Troubleshooting

  • No supported method found error: This occurs if the node cannot find a matching method in the API client for the requested resource-operation combination. Ensure that the "Resource" is set to "Calendar" and the "Operation" to "Get Timetable". Also, verify that the custom method name (if used) is correct.
  • Invalid date format: The "From Date" and "To Date" must be in YYYY-MM-DD format. Incorrect formatting may cause the API call to fail or return no data.
  • Empty results: If no timetable entries are returned, check that the date range covers a valid period with scheduled events.
  • Authentication errors: Verify that the provided API credentials are valid and have sufficient permissions to access timetable data.

Links and References

Discussion