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. It allows users to retrieve various types of information such as absences, grades, messages, homework, calendar events, and more. Specifically, the "Get Absences" operation under the "Info" resource fetches absence records, optionally filtered by date range.

Typical use cases include:

  • Automatically retrieving student absence data for attendance tracking.
  • Integrating absence information into school management workflows.
  • Generating reports or notifications based on absence records.

For example, a school administrator could use this node to pull all absences within a specific period to analyze attendance trends.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method is called instead of the default one for the operation.

Note: The node also internally uses other parameters depending on the operation, such as date ranges (from, to), but these are not exposed in the provided property definition snippet.

Output

The output is an array of JSON objects representing the data returned from the Librus API for the requested operation.

For the "Get Absences" operation, the JSON output contains absence records, potentially filtered by the specified date range. Each item corresponds to an individual absence entry with details as provided by the API.

If the node retrieves binary data (e.g., files in some message operations), it outputs a binary property containing the file data encoded in base64 along with MIME type and filename metadata. However, this does not apply to the "Get Absences" operation.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • Supports optional filtering by date range (from and to parameters).
  • No additional external dependencies beyond the API access.

Troubleshooting

  • No supported method found error: This occurs if the node cannot find a matching API method for the selected resource and operation. Ensure that the resource and operation names are correct and supported by the current version of the node.
  • Authentication errors: Verify that the provided Librus API credentials are correct and have sufficient permissions.
  • Empty results: If no absences are returned, check the date range filters and ensure there are absence records in that period.
  • Custom method usage: Using an invalid custom method name may cause failures; only use known methods supported by the underlying API client.

Links and References

Discussion