LibrusInstall

Overview

This node integrates with the Librus API, a platform commonly used in educational environments for managing school-related data such as messages, absences, homework, calendars, and grades. The node allows users to perform various operations on different resources within Librus, including sending messages, retrieving absences, listing homework, and more.

Specifically, the Absence - Send Message operation enables sending messages related to absences or other contexts through the Librus messaging system. This can be useful for teachers, administrators, or parents who want to communicate about student absences directly via the platform.

Practical examples include:

• Sending notifications to students or parents about an absence.
• Communicating with school staff regarding attendance issues.
• Automating absence-related messaging workflows within n8n.

Properties

Note: Although only one property is provided here, the node internally supports many parameters depending on the resource and operation chosen (e.g., messageId, userId, title, content, folderId, page, etc.). These are not listed here as they were not part of the provided input properties.

Output

The output of the node is an array of items where each item contains a json field representing the response from the Librus API for the requested operation.

• For most operations, the json field contains the JSON object(s) returned by the API, such as message details, absence records, homework lists, calendar events, grades, etc.
• For the Send Message operation under the Absence resource, the output JSON will contain the result of the message sending action, typically confirmation or status information.
• If the operation involves downloading files (e.g., getting a message attachment), the node outputs binary data encoded in base64 under a specified binary property, along with metadata like MIME type and filename.

Dependencies

• Requires valid credentials for the Librus API, specifically a login and password.
• Uses an internal client wrapper (LibrusClientWrapper) to interact with the Librus API.
• Relies on helper functions for filtering results by date range and converting streams to buffers.
• No additional external services beyond the Librus API are required.

Troubleshooting

• No supported method found error:
  If the node throws an error indicating no supported method was found for the selected resource and operation, it means either the operation is invalid or the custom method name does not match any available API methods.
  Resolution: Verify that the resource and operation names are correct and that the custom method name (if used) corresponds to a valid method in the Librus API client.

• Authentication errors:
  If credentials are incorrect or missing, the node will fail to authenticate with the Librus API.
  Resolution: Ensure that the API login and password credentials are correctly configured in n8n.

• Empty or unexpected responses:
  Some operations may return empty arrays or unexpected data structures if the parameters (like IDs or date ranges) do not match any records.
  Resolution: Double-check input parameters such as absence IDs, date filters, and paging options.

• Binary data handling:
  When retrieving files, ensure the binary property name is correctly set; otherwise, the file data may not be accessible downstream.

Links and References

• Librus API Documentation (Note: actual public documentation may vary or require access)
• n8n Documentation on Creating Custom Nodes
• General info on Librus Platform