Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API to retrieve calendar data, among other functionalities. Specifically, the "Get Calendar" operation fetches calendar information for a specified month and year. This is useful for automating access to school or organizational calendars managed via Librus, enabling workflows such as scheduling, reminders, or syncing events with other systems.

Practical examples:

  • Automatically retrieving the current month's calendar to display upcoming events in a dashboard.
  • Fetching a future month's calendar to prepare notifications or reports.
  • Integrating calendar data into other applications like Google Calendar or task management tools.

Properties

Name Meaning
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method will be called instead of the default one for the operation.
Month Number representing the month to retrieve (1-12). Use 0 to select the current month automatically.
Year Number representing the year to retrieve (e.g., 2025). Use 0 to select the current year automatically.

Output

The output is an array of JSON objects representing calendar entries for the requested month and year. Each object corresponds to a calendar event or day detail as returned by the Librus API.

  • The structure of each JSON object depends on the Librus API response but generally includes date, event details, and related metadata.
  • If multiple items are returned nested in arrays, the node flattens them into a single array of objects.
  • No binary data is output for this operation.

Example output snippet (conceptual):

[
  {
    "date": "2024-06-01",
    "events": [
      {
        "title": "Math Exam",
        "type": "exam",
        "description": "Chapter 5-7"
      }
    ]
  },
  {
    "date": "2024-06-02",
    "events": []
  }
]

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • The node uses an internal client wrapper to communicate with the Librus API.
  • No additional external services or environment variables are required beyond the API credentials.

Troubleshooting

  • No supported method found error: Occurs if the operation or custom method name does not match any available API methods. Verify that the operation name is correct and that the custom method name (if used) exists in the API.
  • Empty or unexpected output: Check that the month and year parameters are correctly set; using 0 defaults to the current date. Also, ensure the account has calendar data for the requested period.
  • Authentication errors: Ensure the provided API credentials are valid and have sufficient permissions.
  • Flattening issues: The node attempts to flatten nested arrays in the calendar response. If the structure changes unexpectedly, output might be affected.

Links and References

Discussion