Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API to retrieve various types of data related to a school environment, such as messages, homework, absences, calendar events, grades, and notifications. Specifically, for the Calendar - Get Notifications operation, it fetches notification data from the user's account.

Typical use cases include:

  • Automatically retrieving calendar notifications to keep track of upcoming events or changes.
  • Integrating school calendar notifications into other workflows or systems.
  • Monitoring notifications for timely alerts about school activities.

For example, a user might set up this node to periodically pull new calendar notifications and send them as reminders via email or chat.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method is called instead of the default one for the selected operation.

Note: The node also internally uses other parameters depending on the operation, but for the "Get Notifications" operation under the Calendar resource, only the above property is relevant from the provided list.

Output

The output is an array of JSON objects representing the notifications retrieved from the Librus API. Each object corresponds to a single notification with its associated details as returned by the API.

  • The json field contains the notification data.
  • No binary data output is expected for this operation.

Example output structure (simplified):

[
  {
    "id": "notification_id",
    "title": "Notification title",
    "date": "2024-06-01T12:00:00Z",
    "content": "Details about the notification"
  },
  ...
]

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.
  • The node expects proper configuration of these credentials within n8n.

Troubleshooting

  • No supported method found error: This occurs if the node cannot find a matching API method for the selected resource and operation. Ensure that the resource and operation names are correct and supported by the node.
  • Authentication errors: Invalid or missing credentials will cause failures. Verify that the login and password for the Librus API are correctly configured.
  • Empty or unexpected results: Check date range filters or other parameters that might limit the returned data.
  • Custom method usage: If using the "Custom method name" property, ensure the method exists in the API client; otherwise, the node will throw an error listing available methods.

Links and References

Discussion