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 in Polish schools for managing educational data such as absences, messages, homework, calendar events, and grades. The node allows users to perform various operations on different resources within the Librus system.

Specifically, for the Absence resource with the List Inbox operation, the node fetches a list of absence records from the user's account. This can be useful for educators or school administrators who want to retrieve and process absence data programmatically, for example, to generate reports, monitor attendance trends, or trigger notifications based on absence patterns.

Practical examples include:

  • Automatically retrieving all absences within a specified date range.
  • Integrating absence data into external school management systems.
  • Monitoring student attendance and alerting parents or staff when absences exceed a threshold.

Properties

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

Note: Although only one property is explicitly provided, the node internally supports many other parameters depending on the resource and operation, such as date ranges (from, to), IDs (absenceId), pagination (page), and others. For the Absence resource and List Inbox operation, relevant parameters like date filtering are supported internally.

Output

The output is an array of JSON objects representing the fetched absence records. Each object corresponds to one absence entry retrieved from the Librus API.

  • If multiple input items are processed, the output will be an array of absence objects matching each input.
  • The node does not output binary data for this operation.
  • The JSON structure depends on the Librus API response for absences but typically includes details such as absence dates, types, reasons, and related metadata.

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 date filtering via "from" and "to" parameters to limit results by date range.
  • No additional external dependencies beyond the Librus API and its authentication.

Troubleshooting

  • No supported method found error: If the node cannot find a suitable API method for the selected resource and operation, it throws an error listing available methods. This usually means the operation or resource is unsupported or misspelled. Verify the resource and operation names.
  • Authentication errors: Ensure that the provided credentials (login and password) are correct and have sufficient permissions.
  • Empty results: If no absences are returned, check the date range filters or absence IDs used. Also verify that the user account actually has absence data.
  • Custom method usage: Using the "Custom method name" property incorrectly may cause method resolution failures. Use only valid method names exposed by the Librus API client.

Links and References

Discussion