LibrusInstall

Overview

This node interacts with the Librus API to retrieve calendar data within a specified date range. It is designed to fetch calendar entries, such as school events or schedules, optionally filtered by month and year. This functionality is useful for automating workflows that require access to academic calendars, event planning, or timetable management.

Practical examples include:

• Automatically fetching and processing upcoming school events for notifications.
• Integrating calendar data into other systems like Google Calendar or Slack.
• Generating reports based on calendar events within a specific timeframe.

Properties

Output

The node outputs an array of JSON objects representing calendar entries retrieved from the Librus API. Each object corresponds to a calendar event or schedule item, typically including details such as dates, descriptions, and related metadata.

If multiple calendar entries are returned, they are flattened into a single array of objects. The output does not include binary data for this operation.

Example output structure (simplified):

[
  {
    "date": "2024-06-01",
    "eventName": "School Holiday",
    "description": "National holiday observed"
  },
  {
    "date": "2024-06-15",
    "eventName": "Parent-Teacher Meeting",
    "description": "Scheduled meeting for all classes"
  }
]

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 or environment variables are explicitly required beyond the API credentials.

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 Resource is set to "Messages" and Operation to "Get Calendar". Also, check if the custom method name (if used) matches a valid API method.
• Empty or unexpected results: Ensure the date filters ("From" and "To") are correctly formatted (YYYY-MM-DD) and logically consistent (start date before end date).
• Authentication errors: Confirm that the provided API credentials are correct and have sufficient permissions to access calendar data.
• Flattening issues: The node attempts to flatten nested arrays in the response; if the output seems malformed, verify the API response structure or try removing the custom method override.

Links and References

• Librus API Documentation (general reference, actual URL may vary)
• n8n documentation on creating custom nodes
• Date filtering helper function used internally: filters data by date range based on "From" and "To" properties