Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API, a platform commonly used by schools for managing educational data. Specifically, the "Calendar" resource with the "Get Attachment" operation allows users to retrieve calendar-related data or attachments from the Librus system.

Typical use cases include:

  • Fetching calendar events or timetable information for students or teachers.
  • Downloading attachments related to calendar events.
  • Integrating school calendar data into other workflows or systems for notifications, reporting, or scheduling.

For example, a user might automate fetching all calendar events for a given month and then send reminders via email or update another calendar system.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method is called instead of the default one for the selected operation.

Note: The node internally supports many parameters depending on the resource and operation, such as date ranges, IDs, titles, content, etc., but for the "Calendar - Get Attachment" operation specifically, only the above custom method name property is exposed in your provided input properties.

Output

The output JSON structure depends on the specific calendar operation invoked:

  • For calendar-related operations like getting timetables, calendar events, or attachments, the node returns JSON objects representing those entities.
  • If the operation involves downloading a file (e.g., an attachment), the node outputs binary data encoded in base64 under a specified binary property (default "data"). This includes the file's MIME type and filename extracted from the path.
  • When multiple items are returned (e.g., multiple events), the output is an array of JSON objects, each representing one item.

In summary, the output contains either:

  • JSON objects with calendar event or timetable details.
  • Binary data for attachments with metadata for further processing.

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 are required beyond access to the Librus platform.
  • The node expects proper configuration of credentials within n8n to authenticate API requests.

Troubleshooting

  • No supported method found error: This occurs if the requested 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 results: Check date range filters and IDs passed to the node; incorrect or missing parameters may lead to no data being returned.
  • Binary data issues: If downloading files, ensure the attachment path is correct and accessible.

Links and References

Discussion