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 student information such as absences, grades, messages, homework, and calendars. The node allows users to perform various operations on different resources like Absence, Messages, Homework, Calendar, and Info.
Specifically, the Get Point Grade operation under the Absence resource fetches detailed point grade information related to a student's absence or performance. This can be useful for educators or school administrators who want to retrieve specific grading details programmatically.
Practical examples:
- Automatically retrieving a student's point grade for an absence to include in reports.
- Integrating absence-related grades into a custom dashboard or notification system.
- Fetching point grades as part of a larger workflow that manages student attendance and performance.
Properties
| Name | Meaning |
|---|---|
| Custom method name | Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this method is called instead of the default one for the operation. |
Note: Other parameters relevant to the operation (like gradeId) are retrieved internally and not exposed in the provided properties JSON but are required for the operation.
Output
The output is a JSON object containing the data returned from the Librus API for the requested point grade. The structure depends on the API response for the point grade but typically includes details about the grade itself.
- If multiple items are returned, the node outputs an array of JSON objects.
- For this operation, binary data output is not applicable.
Example output snippet (conceptual):
{
"gradeId": 123,
"value": "5",
"description": "Excellent participation",
"date": "2024-04-01"
}
Dependencies
- Requires valid credentials for the Librus API (login and password).
- Uses an internal client wrapper (
LibrusClientWrapper) to communicate with the API. - No additional external dependencies beyond the configured API credentials.
Troubleshooting
- No supported method found error: Occurs if the specified resource-operation combination does not match any available API methods. Ensure the correct resource and operation names are selected.
- Authentication errors: Verify that the provided login and password credentials are correct and have sufficient permissions.
- Empty or unexpected responses: Check date filters or parameters; some operations support filtering by date range which might limit results.
- Custom method name misuse: Providing an incorrect custom method name may cause the node to fail finding the method. Use only valid method names exposed by the Librus API client.
Links and References
- Librus API Documentation (official API docs, if publicly available)
- n8n documentation on creating custom nodes
- General info on Librus platform