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 grades, homework, absences, messages, and calendar events. The node allows users to retrieve various types of information from Librus, including detailed event data when using the "Info" resource with the "Get Event" operation.

Typical use cases include:

  • Fetching specific calendar events or absences for students or teachers.
  • Retrieving messages, homework assignments, or grades.
  • Accessing notifications or account information.

For example, a school administrator could automate the retrieval of upcoming events or absences to synchronize with other scheduling tools or notify parents.

Properties

Name Meaning
Custom method name (Advanced) Override the default underlying API method to call (e.g., getMarks). If empty, the node uses the standard method mapped to the selected resource and operation.

Note: The node internally supports many parameters depending on the resource and operation, such as eventId, eventIsAbsence, date ranges (from, to), paging options, message IDs, etc. However, only the "Custom method name" property is explicitly defined in the provided input properties JSON.

Output

The node outputs an array of items where each item contains a json field holding the data returned from the Librus API call corresponding to the requested resource and operation.

  • For the "Get Event" operation under the "Info" resource, the output JSON contains details about the requested event(s). This may include event metadata such as event ID, title, description, date/time, and whether the event is marked as an absence.
  • If multiple events are requested (multiple input items), the output will be an array of event objects.
  • The node can also output binary data for certain operations (e.g., downloading files), but this does not apply to the "Get Event" operation.

Dependencies

  • Requires valid credentials for the Librus API, specifically a login and password.
  • Uses an internal client wrapper to communicate with the Librus API.
  • Supports optional filtering by date range and pagination depending on the operation.
  • No additional external services beyond the Librus API are required.

Troubleshooting

  • No supported method found error: If the node cannot find a matching API method for the selected resource and operation (or custom method name), it throws an error listing available methods. To fix this, verify that the resource and operation names are correct and that the custom method name (if used) matches a valid API method.
  • Authentication errors: Ensure that the provided Librus API credentials (login and password) are correct and have sufficient permissions.
  • Empty or unexpected results: Check if the input parameters like event ID or date ranges are correctly set. Also, confirm that the requested data exists in the Librus system.
  • Binary data handling: For operations returning files, ensure the binary property name is set correctly to avoid missing or malformed attachments.

Links and References

Discussion