Librus icon

Librus

Read data from Librus Synergia (unofficial)

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing student information such as absences, grades, homework, messages, and calendar events. The node allows users to retrieve detailed information about various resources like absences, grades, messages, homework, and calendar events.

Specifically, the Info - Get Absence operation fetches absence records from the Librus system. This can be useful for educators or administrators who want to automate attendance tracking, generate reports on student absences, or integrate absence data into other systems.

Practical examples:

  • Automatically retrieving absence details for a specific student or date range.
  • Generating absence reports for a class or group.
  • Triggering notifications or workflows based on absence data.

Properties

Name Meaning
Custom method name (Advanced) Override the default Librus API method called by the node. For example, specify a custom method like getMarks to call instead of the standard one. Defaults to empty string (no override).

Note: Although only the "Custom method name" property is provided here, the node internally supports many other parameters depending on the resource and operation selected (e.g., absenceId, from/to dates), but these are not listed here as per the user input.

Output

The node outputs JSON data representing the response from the Librus API for the requested absence information.

  • If multiple input items are processed (e.g., multiple absence IDs), the output will be an array of JSON objects, each corresponding to one absence record.
  • The structure of each JSON object depends on the Librus API's absence data format, typically including fields like absence ID, date, reason, status, etc.
  • 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 user to configure these credentials securely in n8n before execution.

Troubleshooting

  • No supported method found error: If the node throws an error indicating no supported method was found for the resource-operation combination, verify that the resource and operation names are correct and supported by the underlying API client.
  • Authentication errors: Ensure that the Librus API credentials (login and password) are correctly configured and have sufficient permissions.
  • Empty or unexpected results: Check if the input parameters like absenceId or date ranges are correctly set and correspond to existing data in Librus.
  • Custom method usage: When using the "Custom method name" property, ensure the method exists in the API client; otherwise, the node will throw an error listing available methods.

Links and References


If you need details on other operations or resources, please provide their names or additional properties.

Discussion