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 messaging-related data within the Librus system. Specifically, the "Messages" resource with the "List Receivers" operation fetches a list of message receivers filtered by a specified group. This is useful in scenarios where you want to obtain contacts or recipients categorized by roles or groups (e.g., teachers, students) for sending messages or managing communication.

Practical examples include:

  • Retrieving all teacher contacts ("nauczyciel" group) to send announcements.
  • Listing student groups or other predefined receiver groups to target specific audiences.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format to limit results by date (not used here)
To Optional end date filter in YYYY-MM-DD format to limit results by date (not used here)
Custom method name Advanced: override the default API method called to fetch data (e.g., getMarks)
Group Receiver group name to specify which group of message receivers to list (default: "nauczyciel")

Note: For this operation, only the Group property is actively used to determine which set of receivers to list.

Output

The output is an array of JSON objects, each representing a receiver in the specified group. The exact structure depends on the API response but typically includes details such as receiver identifiers, names, and possibly contact information.

No binary data output is produced for this operation.

Example output item (conceptual):

{
  "id": "receiver-id",
  "name": "Receiver Name",
  "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 access.

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 and resource are correctly set and supported by the underlying API client.
  • Authentication errors: Ensure that the provided login and password credentials are correct and have sufficient permissions.
  • Empty results: If no receivers are returned, check that the specified group name exists and contains members in the Librus system.
  • Date filters ignored: The "From" and "To" properties do not affect this operation; setting them will have no impact.

Links and References

Discussion