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 by schools for managing student information such as grades, absences, homework, messages, and calendars. The node allows users to perform various operations on different resources within the Librus system.

Specifically, the Absence - Get Grade operation retrieves grade information related to absences or other academic records from the Librus system. This can be useful for educators or school administrators who want to programmatically access detailed grade data for students, enabling automation of reporting, monitoring, or integration with other educational tools.

Practical examples include:

  • Automatically fetching a student's grade details after an absence.
  • Integrating grade retrieval into a broader workflow that tracks attendance and performance.
  • Generating reports combining absence records with corresponding grades.

Properties

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

Note: Other parameters like absenceId are used internally based on the operation but were not provided in the input properties JSON.

Output

The node outputs data in the json field of each item:

  • For the Get Grade operation under the Absence resource, the output is the grade data retrieved from the Librus API. This typically includes detailed information about a specific grade record.
  • The output structure depends on the API response but generally consists of objects representing grades with their associated metadata.
  • If multiple inputs are processed, the output is an array of such grade objects.
  • The node does not output binary data for this operation.

Dependencies

  • Requires valid credentials for the Librus API, specifically a login and password.
  • Uses an internal client wrapper to communicate with the Librus API.
  • No additional external dependencies beyond the configured 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 and resource names are correct and supported by the current version of the node.
  • Authentication errors: Ensure that the provided Librus API credentials (login and password) are correct and have sufficient permissions.
  • Empty or unexpected results: Check date range filters if used, as they may limit returned data. Also, confirm that the requested absenceId or other identifiers exist in the system.
  • Custom method usage: When using the "Custom method name" property, ensure the method exists in the underlying API client; otherwise, the node will fail to find and call it.

Links and References

Discussion