Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to retrieve various types of data related to a user's school activities. Specifically, for the Messages resource and the Get Notifications operation, it fetches notifications or messages from the user's account within an optional date range. This is useful for automating the retrieval of new messages or announcements from the Librus platform, enabling workflows such as alerting users about new notifications, archiving messages, or integrating message data into other systems.

Practical examples:

  • Automatically fetching all notifications received between two dates to generate a report.
  • Triggering downstream processes when new important messages arrive.
  • Archiving messages for compliance or record-keeping purposes.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format; only notifications from this date onward will be retrieved.
To Optional end date filter in YYYY-MM-DD format; only notifications up to this date will be retrieved.
Custom method name Advanced option to override the default underlying API method called (e.g., specify a different Librus API method).

Output

The node outputs an array of JSON objects representing the notifications fetched from the Librus API. Each object corresponds to a single notification or message, containing all relevant details as provided by the API (such as message content, sender, date, etc.).

If the node is used with operations that return files (not applicable here), it can output binary data encoded in base64 with associated metadata like MIME type and filename.

Dependencies

  • Requires valid user credentials (login and password) for the Librus API.
  • Depends on the external Librus API service being accessible.
  • Uses an internal client wrapper to communicate with the Librus API.
  • No additional environment variables are explicitly required beyond the credentials.

Troubleshooting

  • No supported method found error: If the node cannot find a matching API method for the requested resource-operation combination, it throws an error listing available methods. This usually means the operation or resource name is incorrect or unsupported.
  • Authentication failures: Incorrect login or password will prevent successful API calls.
  • Date format issues: The "From" and "To" properties must be in YYYY-MM-DD format; invalid formats may cause filtering to fail or return unexpected results.
  • Empty results: If no notifications exist in the specified date range, the output will be empty.
  • API rate limits or downtime: External API limitations or outages can cause errors or delays.

Links and References

Discussion