Actions105
- Info Actions
- Messages Actions
- Homework Actions
- Absence Actions
- Calendar Actions
Overview
This node integrates with the Librus API, a platform commonly used by schools for managing educational data. Specifically, the "List Announcements" operation under the "Absence" resource retrieves announcements from the user's inbox or related announcement channels within Librus.
Typical use cases include:
- Automatically fetching school announcements to display in dashboards or send notifications.
- Integrating announcements into other systems like calendars or messaging platforms.
- Filtering announcements by date range to focus on relevant periods.
For example, a school administrator could use this node to pull all announcements posted during a specific month and then distribute them via email or internal communication tools.
Properties
| Name | Meaning |
|---|---|
| Custom method name | Advanced: override the underlying Librus API method to call (e.g., getMarks). If empty, defaults to the standard method for listing announcements. |
Note: The node also internally uses parameters such as date ranges (from, to) to filter results, but these are not exposed in the provided properties JSON.
Output
The output is an array of JSON objects representing announcements retrieved from the Librus API. Each object contains details about a single announcement, such as its content, title, date, and possibly other metadata depending on the API response.
If the operation returns binary data (not typical for announcements), it would be encoded in base64 format with associated MIME type and filename, but this does not apply to the "List Announcements" operation.
Dependencies
- Requires valid credentials for the Librus API, specifically a login and password.
- Uses an internal client wrapper to communicate with the Librus API.
- Supports optional filtering by date range (
fromandtoparameters). - No additional external dependencies beyond the Librus API and n8n environment.
Troubleshooting
- No supported method found error: This occurs if the specified resource-operation combination or custom method name does not match any available methods in the Librus API client. To fix, verify the resource and operation names or remove the custom method override.
- Authentication errors: Ensure that the provided login and password credentials are correct and have sufficient permissions.
- Empty results: Could be due to no announcements in the specified date range or incorrect filtering parameters.
- Date filtering issues: Make sure date inputs are in the expected format and logical (e.g.,
fromdate is beforetodate).
Links and References
- Librus API Documentation (official API docs, if publicly available)
- n8n documentation on creating custom nodes
- General info on Librus platform