Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to retrieve various types of data related to school management, such as messages, homework, absences, calendar events, and grades. Specifically, for the Messages - Get Absences operation, it fetches absence records from the user's account optionally filtered by a date range.

Common scenarios where this node is beneficial include:

  • Automating attendance tracking by retrieving absence data for students.
  • Integrating absence information into other systems like school management software or reporting tools.
  • Monitoring student attendance over specific periods for analysis or notifications.

For example, a user can configure the node to get all absences between two dates to generate attendance reports or trigger alerts when a student has excessive absences.

Properties

Name Meaning
From Optional start date (format: YYYY-MM-DD) to filter absences from this date onward.
To Optional end date (format: YYYY-MM-DD) to filter absences up to this date.
Custom method name Advanced option to override the default API method called (e.g., specify a different Librus API method).

Output

The output is an array of JSON objects representing absence records retrieved from the Librus API. Each object contains details about a single absence event, such as date, type, and possibly additional metadata depending on the API response.

If no absences are found within the specified date range, the output will be an empty array.

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.
  • 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 requested resource-operation combination. Ensure the operation name is correct and supported by the current version of the node.
  • Authentication failures: If credentials are invalid or missing, the node will fail to connect. Verify that the API login and password are correctly configured.
  • Date format issues: The "From" and "To" properties must be in YYYY-MM-DD format. Incorrect formats may cause filtering to fail or return unexpected results.
  • Empty results: If no absences appear, check that the date range covers periods where absences exist and that the account has relevant data.

Links and References

Discussion