Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API, a platform commonly used in educational environments for managing school-related data. It allows users to retrieve various types of information such as messages, homework, absences, calendar events, grades, notifications, and account details. The "Get Lucky Number" operation specifically fetches the user's lucky number from their Librus account.

Typical use cases include:

  • Automating retrieval of student or teacher data from Librus.
  • Integrating school schedules, homework assignments, or messages into other workflows.
  • Fetching the lucky number as part of personalized notifications or gamification features within educational apps.

For example, a school administrator could use this node to automatically gather all homework assignments due within a date range, or a teacher might retrieve messages from their inbox to trigger alerts.

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 also internally uses other parameters depending on the resource and operation, such as date ranges (from, to), IDs (folderId, messageId, etc.), but these are not exposed in the provided properties JSON and thus are not listed here.

Output

The output is an array of items where each item contains a json field holding the data returned by the Librus API for the requested operation.

  • For most operations, the json field contains objects or arrays representing entities like messages, homework, absences, calendar events, grades, notifications, or account info.
  • For the "Get Lucky Number" operation, the json output contains the lucky number data retrieved from the API.
  • When fetching files (e.g., message attachments), the node outputs binary data encoded in base64 under a binary property (default named "data"). This includes the file's MIME type and filename.

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 by date ranges for some operations.
  • No additional external services beyond the Librus API are required.

Troubleshooting

  • No supported method found error: Occurs if the selected resource-operation combination does not match any available API methods. Ensure the resource and operation names are correct and supported.
  • Authentication errors: Invalid or missing credentials will prevent API access. Verify that the login and password are correctly configured.
  • Empty or unexpected results: Check date filters and IDs used in parameters; incorrect values may lead to no data being returned.
  • Binary file handling: When retrieving files, ensure the binary property name matches downstream usage to avoid data loss.

Links and References

Discussion