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 related to calendars, messages, homework, absences, grades, and more from a Librus account.
Specifically, the Calendar - Get Grade operation fetches grade-related data from the user's Librus account. This can be useful for educators or students who want to programmatically access their grading information, track academic performance over time, or integrate this data into other systems such as dashboards or reporting tools.
Practical examples include:
- Automatically retrieving recent grades to notify students or parents.
- Aggregating grades across subjects for performance analysis.
- Integrating grade data into school management systems or personal productivity apps.
Properties
| Name | Meaning |
|---|---|
| Custom method name | Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method name will be called instead of the default one associated with the selected operation. |
Note: The node internally supports many parameters depending on the resource and operation, but for the Calendar - Get Grade operation, only the "Custom method name" property is exposed here.
Output
The output is a JSON array where each item corresponds to a grade or related data retrieved from the Librus API. The exact structure depends on the API response for the grade retrieval method but typically includes fields such as grade value, subject, date, and possibly additional metadata.
If the node retrieves binary data (not typical for the Calendar Get Grade operation), it would be returned in the binary property with base64 encoding and appropriate MIME type, but this operation outputs JSON data only.
Dependencies
- Requires valid 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 the credentials.
- The node relies on helper functions for filtering data by date range and converting streams to buffers when handling files (not relevant for this operation).
Troubleshooting
- No supported method found error: If the custom method name or operation does not match any available API methods, the node throws an error listing available methods. Ensure the operation and custom method name are correct and supported by the Librus API.
- Authentication errors: Invalid or missing credentials will prevent API access. Verify that the login and password are correct and have sufficient permissions.
- Empty or unexpected results: Check date range filters and input parameters to ensure they match existing data in the Librus account.
- API changes: Since the node calls underlying API methods dynamically, changes in the Librus API may cause some operations to fail until the node is updated.
Links and References
- Librus Official Website – For general information about the platform.
- Librus API Documentation – (If publicly available) Reference for API methods and usage.
- n8n Documentation on Creating Custom Nodes – For understanding how nodes interact with APIs.
If you need details on other operations or resources, please provide their names or additional properties.