Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API, a platform commonly used in educational settings for managing school-related information. Specifically, the "Homework" resource with the "List Receivers" operation retrieves a list of message receivers from the user's inbox group (e.g., teachers). This can be useful for scenarios where you want to programmatically obtain contacts or recipients related to messages within the Librus system.

Practical examples include:

  • Automatically fetching and displaying all possible message recipients before sending a message.
  • Integrating with other systems to synchronize contact lists or notify specific groups.
  • Filtering message receivers by date ranges if applicable.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format to limit results from this date onward.
To Optional end date filter in YYYY-MM-DD format to limit results up to this date.
Custom method name Advanced: override the default underlying API method to call (e.g., specify a custom method name instead of the default one).

Output

The output is an array of JSON objects representing the message receivers retrieved from the Librus API. Each object corresponds to a receiver's details as returned by the API.

  • The json field contains the receiver data.
  • No binary data output is produced for this operation.

Example output structure (simplified):

[
  {
    "id": "receiver_id_1",
    "name": "Receiver Name 1",
    "group": "nauczyciel"
  },
  {
    "id": "receiver_id_2",
    "name": "Receiver Name 2",
    "group": "nauczyciel"
  }
]

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 node throws an error indicating no supported method was found for the resource-operation combination, ensure that the operation name is correct and supported by the current version of the Librus API client.
  • Authentication errors: Verify that the provided login credentials are correct and have sufficient permissions.
  • Empty results: If the output is empty, check the date filters ("From" and "To") to ensure they cover the expected range.
  • Custom method name usage: When using the "Custom method name" property, ensure the method exists in the API client; otherwise, the node will fail to find and execute it.

Links and References

Discussion