LibrusInstall

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing student information such as absences, messages, homework, calendar events, and notifications. The node allows users to perform various operations on different resources within Librus, including retrieving absence records, getting notifications, managing messages, and more.

Specifically, the Get Notifications operation under the Absence resource fetches notification data related to absences or other relevant updates from the Librus system. This can be useful for educators, administrators, or parents who want to automate monitoring of absence notifications or integrate them into other workflows.

Practical examples:

• Automatically retrieve absence notifications daily and send summaries via email.
• Integrate absence notifications into a school management dashboard.
• Trigger alerts or follow-up actions when new absence notifications are received.

Properties

Note: Although only the "Custom method name" property is explicitly defined here, the node internally supports many other parameters depending on the resource and operation chosen (e.g., date ranges, IDs). For the Get Notifications operation, no additional input properties are required beyond authentication and resource/operation selection.

Output

The output is an array of JSON objects representing the notifications retrieved from the Librus API. Each object corresponds to a single notification item with its associated data fields as returned by the API.

• The json field contains the notification details.
• No binary data output is expected for this operation.

If the node is configured to get files (in other operations), it can output binary data encoded in base64, but this does not apply to the Get Notifications 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 of results by date range (from and to parameters).
• No external environment variables are explicitly required beyond the API credentials.

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 node. Also, check if the custom method name (if provided) matches an existing method in the API client.

• Authentication failures:
  Ensure that the provided login and password credentials are correct and have sufficient permissions to access the requested data.

• Empty or unexpected results:
  Check if any date filters (from, to) are set correctly. Incorrect date formats or ranges might result in empty outputs.

• API rate limits or connectivity issues:
  Network problems or API rate limiting may cause errors or timeouts. Retry after some time or check network connectivity.

Links and References

• Librus Official Website (for general platform info)
• Librus API Documentation (if publicly available; replace with actual link)
• n8n documentation on Creating Custom Nodes

If you need details about other operations or resources, feel free to ask!