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. Specifically, the "Homework" resource with the "Get Notifications" operation allows users to retrieve notifications related to homework and other school activities within an optional date range.

Typical use cases include:

  • Automatically fetching new homework notifications for students or parents.
  • Monitoring updates or alerts about assignments over a specified period.
  • Integrating homework notifications into other workflows such as reminders or calendar events.

For example, a teacher could use this node to pull all homework-related notifications from the last week and send summary emails to students.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format; limits notifications from this date onward.
To Optional end date filter in YYYY-MM-DD format; limits notifications up to this date.
Custom method name Advanced option to override the default underlying API method called (e.g., getMarks).

Output

The node outputs an array of JSON objects representing the notifications retrieved from the Librus API. Each object corresponds to a single notification and contains relevant details as provided by the API.

If no notifications are found, the output will be an empty array.

No binary data is produced by this operation.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • The node expects the environment to have network access to the Librus service.

Troubleshooting

  • No supported method found error: This occurs if the node cannot find a matching API method for the selected resource-operation combination or custom method name. Ensure that the resource and operation are correctly set and that any custom method name matches a valid API method.
  • Authentication failures: If credentials are incorrect or expired, the node will fail to authenticate. Verify the login and password credentials.
  • Date filtering issues: Invalid date formats for the "From" and "To" properties may cause unexpected results or errors. Use the YYYY-MM-DD format strictly.
  • Empty results: If no notifications appear, check that the date range covers periods where notifications exist and that the user account has relevant data.

Links and References

Discussion