Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to manage and retrieve various types of data related to messages, homework, absences, calendar events, and user information. Specifically, for the Messages resource with the List Subjects operation, it fetches a list of subjects related to homework assignments.

Common scenarios where this node is beneficial include:

  • Retrieving subjects to filter or organize homework assignments.
  • Integrating school-related data into workflows for notifications or reporting.
  • Automating data collection from the Librus platform for educational management.

For example, a teacher could use this node to automatically pull all subjects they teach and then fetch homework assignments per subject to send reminders to students.

Properties

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

Note: The "From" and "To" properties are used to filter the returned data by date ranges when applicable.

Output

The output is an array of JSON objects representing the subjects related to homework. Each item corresponds to one subject retrieved from the Librus API.

  • The json field contains the subject data as returned by the API.
  • This operation does not produce binary data.

Example output structure (simplified):

[
  {
    "id": "subjectId1",
    "name": "Mathematics",
    "otherSubjectDetails": "..."
  },
  {
    "id": "subjectId2",
    "name": "History",
    "otherSubjectDetails": "..."
  }
]

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 or environment variables are required beyond the API credentials.

Troubleshooting

  • No supported method found error: If the node throws an error indicating no supported method was found for the resource-operation combination, verify that the operation name matches exactly and that the API credentials have sufficient permissions.
  • Empty or unexpected results: Check the date filters ("From" and "To") to ensure they are correctly formatted and logically consistent (start date before end date).
  • Authentication failures: Ensure the provided login and password credentials are correct and active.
  • API changes: If the Librus API changes, some methods might become unavailable; in such cases, using the "Custom method name" property to specify an alternative method may help.

Links and References

Discussion