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. It allows users to retrieve various types of information such as messages, homework, absences, calendar events, and grades. Specifically, the "Calendar" resource with the "Get Absence" operation fetches detailed absence records from the user's calendar.
Typical use cases include:
- Automatically retrieving student absence records for attendance tracking.
- Integrating school calendar absences into other systems or workflows.
- Generating reports on student attendance over specific date ranges.
For example, a school administrator could use this node to pull absence details for a given student and then trigger notifications or update attendance databases accordingly.
Properties
| Name | Meaning |
|---|---|
| Custom method name | (Optional) Override the default underlying API method to call (e.g., getMarks). If set, this custom method will be invoked instead of the standard one for the selected operation. |
Note: The node also internally uses other parameters depending on the operation, such as absenceId for identifying specific absences, but these are not exposed in the provided input properties JSON.
Output
The node outputs JSON data representing the requested information from the Librus API.
For the "Calendar" resource and "Get Absence" operation:
- If multiple input items are provided, it returns an array of absence objects corresponding to each
absenceId. - If a single item is processed, it returns a single absence object.
- Each absence object contains detailed information about the absence record fetched from the API.
No binary data output is associated with this operation.
Dependencies
- Requires valid credentials for the Librus API, specifically a login and password.
- Depends on the external
librus-apiclient library wrapped inside the node's helper classes. - The node expects proper configuration of these credentials within n8n to authenticate API requests.
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 current version of the Librus API client.
- Authentication failures: Invalid or missing credentials will prevent successful API calls. Verify that the login and password are correctly configured.
- Empty or unexpected results: Check date range filters (
from,to) if used, as they may limit returned data. Also, ensure that the specifiedabsenceIdexists. - Custom method name issues: Using an incorrect or unsupported custom method name can cause errors. Use this feature only if you know the exact method available in the API client.
Links and References
- Librus API Documentation (official API docs, if publicly available)
- n8n documentation on creating custom nodes
- General info on attendance management systems
If you need details on other operations or resources, please provide their names or additional input property definitions.