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 "Get Absences" operation under the "Absence" resource retrieves absence records from the Librus system.
Typical use cases include:
- Automatically fetching student absence data for attendance tracking.
- Integrating absence information into school management workflows or reporting tools.
- Monitoring and analyzing attendance patterns over specific date ranges.
For example, a school administrator could use this node to pull all absences within a given period to generate attendance reports or trigger notifications for excessive absences.
Properties
| Name | Meaning |
|---|---|
| Custom method name | (Advanced) Override the default Librus API method called for this operation. For example, you can specify a different method name like getMarks if needed. Defaults to empty string (no override). |
Output
The node outputs JSON data representing absence records retrieved from the Librus API. The structure of each JSON object corresponds to the absence data model returned by the API, typically including details such as absence dates, types, and related metadata.
If multiple absences are retrieved, the output is an array of JSON objects, each representing one absence record.
No binary data output is produced for this operation.
Dependencies
- Requires valid credentials for the Librus API, specifically a login and password.
- The node depends on an internal client wrapper around the Librus API to perform requests.
- Date filtering is supported via optional "from" and "to" parameters (not shown in the provided properties but used internally).
- No additional external services or environment variables are explicitly required beyond the API credentials.
Troubleshooting
- No supported method found error: If the custom method name or operation does not match any available Librus API methods, the node will throw an error listing available methods. Ensure the operation and custom method name are correct.
- Authentication failures: Incorrect or expired credentials will prevent access to the API. Verify that the login and password are valid.
- Empty results: If no absences are returned, check the date range filters or ensure the account has relevant absence data.
- Date filtering issues: The node applies date range filtering internally; incorrect date formats or ranges may lead to unexpected results.
Links and References
- Librus Official Website (for general platform info)
- No direct public API documentation link is provided in the source code; consult your Librus API provider or documentation for detailed API method descriptions.