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 information. It allows users to perform various operations such as retrieving messages, homework, absences, calendar events, and student info like grades or notifications.

The List Receivers operation under the Info resource specifically fetches a list of message receivers from the Librus system. This can be useful for scenarios where you want to identify all possible recipients for messaging within the platform, such as teachers, students, or groups.

Practical examples:

  • Automatically fetching all available message receivers to populate a dropdown in a custom workflow.
  • Using the list of receivers to send bulk notifications or announcements programmatically.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If empty, defaults to the standard method for the operation.

Note: The node also internally uses other parameters depending on the operation, but for the List Receivers operation, only the "Custom method name" property is relevant here.

Output

The output is an array of JSON objects representing the message receivers retrieved from the Librus API. Each object corresponds to one receiver and contains their details as provided by the API.

No binary data is produced for this operation.

Example output structure (simplified):

[
  {
    "id": "receiverId1",
    "name": "Receiver Name 1",
    "type": "teacher"
  },
  {
    "id": "receiverId2",
    "name": "Receiver Name 2",
    "type": "student"
  }
]

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 the Librus API itself.

Troubleshooting

  • No supported method found error: If the custom method name is incorrect or does not exist in the API client, the node will throw an error listing available methods. Ensure the custom method name matches a valid API method.
  • Authentication errors: Invalid or missing credentials will prevent the node from connecting to the Librus API. Verify that the login and password are correct.
  • Empty results: If no receivers are returned, check if the user has appropriate permissions or if the account actually has any receivers configured.
  • Date filtering issues: Although not applicable to List Receivers, other operations use date filters; ensure date formats are correct when using those.

Links and References

Discussion