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 data such as messages, homework, absences, calendar events, and grades. Specifically, the Calendar - List Receivers operation retrieves a list of message receivers from the inbox system within Librus.

Typical use cases include:

  • Fetching all possible recipients to whom messages can be sent within the Librus environment.
  • Automating communication workflows by dynamically obtaining receiver lists.
  • Integrating Librus messaging capabilities into broader automation pipelines.

For example, a school administrator could use this node to automatically retrieve and display all teachers or students available for messaging before sending announcements or notifications.

Properties

Name Meaning
Custom method name (Optional) Override the default underlying API method to call (e.g., getMarks). If set, this custom method will be invoked instead of the standard one for listing receivers.

Output

The output is an array of JSON objects representing the message receivers retrieved from the Librus inbox system. Each object typically contains details about a receiver such as their identifier, name, and possibly other metadata depending on the API response.

If the node is used with other operations that return files or binary data, it can also output binary data encoded in base64, but for the List Receivers operation, the output is purely JSON.

Example output snippet (conceptual):

[
  {
    "id": "receiver1",
    "name": "John Doe",
    "type": "teacher"
  },
  {
    "id": "receiver2",
    "name": "Jane Smith",
    "type": "student"
  }
]

Dependencies

  • Requires valid credentials for the Librus API, specifically a login and password.
  • The node depends on an internal client wrapper around the Librus API to perform calls.
  • No additional external services are required beyond access to the Librus platform.
  • Proper configuration of credentials in n8n is necessary to authenticate API requests.

Troubleshooting

  • No supported method found error: This occurs if the specified resource-operation combination does not match any known API methods. Ensure the Resource is set to "Calendar" and Operation to "List Receivers". Also, verify that the optional custom method name (if provided) matches a valid method.
  • Authentication failures: Incorrect or missing credentials will prevent API access. Double-check the configured login and password.
  • Empty or unexpected output: If no receivers are returned, confirm that the account has access to the inbox and that there are receivers available. Also, check date filters if used in other operations.
  • API changes: Since the node relies on the Librus API, any changes or deprecations in the API may cause failures. Keep the node and its dependencies updated.

Links and References

Discussion