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 grades, absences, homework, messages, and calendars. The node allows users to retrieve various types of data from Librus, including grades, absences, messages, homework assignments, and calendar events.
Specifically, the "Get Grades" operation under the "Absence" resource fetches grade-related information from the user's account. This can be useful for educators or students who want to automate the retrieval of their academic performance data for reporting, analysis, or integration with other systems.
Practical examples:
- Automatically fetching all grades for a student over a semester to generate a performance report.
- Integrating grade data into a school management dashboard.
- Triggering notifications when new grades are posted.
Properties
| Name | Meaning |
|---|---|
| Custom method name | (Optional) Override the default underlying Librus API method to call (e.g., getMarks). |
Note: For the "Get Grades" operation, no additional input properties are explicitly required beyond authentication credentials and the optional custom method override.
Output
The output is a JSON array where each item represents a grade or related grade information retrieved from the Librus API. The exact structure depends on the API response but typically includes fields such as grade value, subject, date, and possibly comments.
If multiple grades are returned, each will be an individual JSON object in the output array.
No binary data output is produced for this operation.
Dependencies
- Requires valid user credentials for the Librus API (login and password).
- Uses an internal client wrapper to communicate with the Librus API.
- No external environment variables are explicitly required beyond these credentials.
Troubleshooting
- No supported method found error: If the node cannot find a matching API method for the requested resource-operation combination, it throws an error listing available methods. This can happen if the operation name is incorrect or if the API has changed. Verify the operation name and ensure the API client supports it.
- Authentication failures: Incorrect login or password will prevent successful API calls. Ensure credentials are correct and have necessary permissions.
- Empty or unexpected responses: If the API returns no data or malformed data, check date filters or parameters passed to the node.
- Custom method name misuse: Providing an invalid 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 Official Website
- Librus API Documentation (if available) (Note: actual public API docs may not be available)
- n8n documentation on Creating Custom Nodes