Librus icon

Librus

Read data from Librus Synergia (unofficial)

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing educational data such as homework, messages, absences, calendar events, and grades. Specifically, the "Homework - Get Attachment" operation allows users to retrieve attachments related to homework assignments within an optional date range.

Typical use cases include:

  • Automatically fetching homework attachments assigned between specific dates.
  • Integrating homework materials into other systems or workflows.
  • Archiving or processing homework files for reporting or review.

For example, a teacher could use this node to download all homework attachments assigned in the last week to prepare lesson plans or share resources with students.

Properties

Name Meaning
From Optional start date filter (format: YYYY-MM-DD). Limits results to items from this date.
To Optional end date filter (format: YYYY-MM-DD). Limits results to items up to this date.
Custom method name Advanced option to override the default API method called (e.g., getMarks).

Output

The node outputs JSON data representing the homework attachments retrieved from the Librus API. The structure depends on the underlying API response but generally includes metadata about each attachment such as file names, URLs, and associated homework details.

If multiple attachments are returned, the output is an array of JSON objects, each corresponding to one attachment.

No binary data output is indicated for this operation; the attachments are referenced via JSON metadata rather than included as raw files.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • Date filtering is applied locally based on the "From" and "To" input properties.
  • No additional external services or environment variables are explicitly required beyond the API credentials.

Troubleshooting

  • No supported method found error: This occurs if the specified resource-operation combination or custom method name does not match any available API methods. Verify that the "Custom method name" property is correct or leave it empty to use defaults.
  • Authentication failures: Ensure that the provided login and password credentials are valid and have sufficient permissions.
  • Empty results: If no attachments are returned, check the date filters ("From" and "To") to ensure they cover the expected timeframe.
  • Date format issues: Dates must be in YYYY-MM-DD format; incorrect formats may cause filtering to fail or return unexpected results.

Links and References

Discussion