Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API, a platform commonly used in educational settings for managing school-related data such as messages, homework, absences, calendar events, and grades. Specifically, the "Messages" resource with the "Get Event" operation allows users to retrieve detailed information about calendar events, including whether an event is marked as an absence.

Typical use cases include:

  • Fetching specific calendar events for students or teachers.
  • Integrating school calendar events into other systems or workflows.
  • Automating notifications or reports based on calendar events.

For example, a school administrator could use this node to automatically pull upcoming events from the Librus calendar and send reminders to students or parents.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format to limit results to events after this date.
To Optional end date filter in YYYY-MM-DD format to limit results to events before this date.
Custom method name Advanced option to override the default API method called (e.g., to call a different underlying function).

Note: The "From" and "To" properties are used to filter the returned events by date range when applicable.

Output

The node outputs JSON objects representing the retrieved event(s) from the Librus calendar. Each output item corresponds to one event and contains all relevant event details as provided by the Librus API.

If multiple input items are processed, the node returns an array of event objects, each corresponding to the respective input.

No binary data output is produced for this operation.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • Date filtering is applied internally based on the "From" and "To" parameters.
  • No additional external services or environment variables are required beyond the API credentials.

Troubleshooting

  • No supported method found error: This occurs if the specified resource-operation combination does not match any available API methods. Ensure that the resource is set to "Messages" and operation to "Get Event", or use the "Custom method name" property correctly.
  • Authentication errors: Verify that the provided API credentials (login and password) are correct and have sufficient permissions.
  • Empty results: If no events are returned, check the date filters ("From" and "To") to ensure they cover the expected event dates.
  • Invalid date format: Dates must be in YYYY-MM-DD format; otherwise, filtering may fail or return unexpected results.

Links and References

Discussion