LibrusInstall

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 resource with the Get Absence operation, it fetches detailed information about a particular absence or multiple absences by their IDs.

Common scenarios where this node is beneficial include:

• Automating attendance tracking by retrieving absence records.
• Integrating school absence data into other systems like HR or student management platforms.
• Generating reports on student attendance over specific date ranges.

For example, a user can configure the node to get absence details for a specific absence ID or multiple IDs, optionally filtering results by date range.

Properties

Note: The "From" and "To" properties apply generally to resources "messages" and "homework" but are also used internally to filter absence data by date range when applicable.

Output

The output is an array of JSON objects representing absence records retrieved from the Librus API. Each object contains detailed information about an absence, such as dates, reasons, and possibly related metadata depending on the API response.

If multiple absence IDs are provided as input, the output will be an array of absence objects corresponding to each requested ID.

No binary data output is produced for this operation.

Example output structure (simplified):

[
  {
    "absenceId": 123,
    "date": "2024-05-01",
    "reason": "Sick leave",
    "status": "Approved"
  },
  {
    "absenceId": 124,
    "date": "2024-05-02",
    "reason": "Family emergency",
    "status": "Pending"
  }
]

Dependencies

• Requires valid credentials for the Librus API (login and password).
• Uses an internal client wrapper to communicate with the Librus API.
• No additional external services beyond the Librus API are required.
• The node expects proper configuration of these credentials within n8n.

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 operation name matches exactly one of the supported Librus API methods or use the "Custom method name" property to specify a valid method.
• Authentication errors: Ensure that the provided API credentials (login and password) are correct and have sufficient permissions.
• Empty or unexpected results: Check the date filters ("From" and "To") to ensure they cover the expected period. Also, verify that the absence IDs provided exist in the system.
• Multiple absence IDs handling: When providing multiple absence IDs, ensure each ID is correctly specified per item in the input data; otherwise, the node may return incomplete results.

Links and References

• Librus API Documentation (official API docs, if publicly available)
• n8n documentation on creating custom nodes
• General info on attendance management systems