LibrusInstall

Overview

This node integrates with the Librus API, a platform commonly used in educational environments for managing school-related data such as absences, messages, homework, calendar events, and grades. Specifically, the "Absence - Get Attachment" operation allows users to retrieve attachments related to absences or other resources managed by Librus.

Typical use cases include:

• Fetching detailed absence records or related files for students.
• Automating retrieval of absence documentation for reporting or analysis.
• Integrating absence data into other systems or workflows.

For example, a school administrator could use this node to automatically download absence attachments submitted by students or parents and store them in a document management system.

Properties

Note: The node also internally uses other parameters like absenceId to specify which absence record to fetch, but these are not part of the provided input properties JSON.

Output

The output is an array of items where each item contains a json field holding the data returned from the Librus API for the requested absence attachment or related resource.

• For binary data (such as file attachments), the node converts the stream into a base64-encoded string and places it inside a binary property. This includes:
  • data: The base64-encoded content of the attachment.
  • mimeType: Set to "application/octet-stream".
  • fileName: Extracted from the attachment path.

Thus, the output can contain either JSON objects representing absence data or binary data representing downloaded files.

Dependencies

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

Troubleshooting

• No supported method found error: This occurs if the specified resource-operation combination does not match any available method in the Librus API client. To fix, verify that the resource and operation names are correct and supported.
• Authentication failures: Ensure that the provided login and password credentials are valid and have sufficient permissions.
• Empty or unexpected output: Check date filters (from, to) and IDs (e.g., absenceId) to ensure they correspond to existing data.
• Binary data issues: If attachments fail to download properly, confirm the attachment path is correct and accessible.

Links and References

• Librus API Documentation (if publicly available)
• n8n Documentation on Creating Custom Nodes
• General info on Handling Binary Data in n8n