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 such as messages, homework, absences, calendar events, and grades. The "Get Message" operation under the "Homework" resource specifically retrieves detailed information about a particular homework entry identified by its ID.
Typical use cases include:
- Fetching details of a specific homework assignment to display or process in an automated workflow.
- Integrating homework data into other systems like calendars, task managers, or notification services.
- Automating reminders or follow-ups based on homework deadlines or content.
For example, a teacher could automate sending homework details to students via email or a messaging platform by retrieving the homework data through this node.
Properties
| Name | Meaning |
|---|---|
| From | Optional start date filter (format: YYYY-MM-DD) to limit data retrieval to after this date. |
| To | Optional end date filter (format: YYYY-MM-DD) to limit data retrieval to before this date. |
| Custom method name | Advanced option to override the default underlying API method called (e.g., getMarks). |
Note: For the "Get Message" operation on the "Homework" resource, the main relevant input is the homework ID parameter (not listed here but used internally), which identifies the specific homework to retrieve.
Output
The output JSON structure contains the detailed data of the requested homework item. This typically includes fields such as homework description, due dates, subject, attachments, and any other metadata provided by the Librus API for that homework entry.
If multiple items are returned (not typical for "Get Message"), each will be an individual JSON object in the output array.
No binary data output is produced for this operation.
Dependencies
- Requires valid credentials for the Librus API (login and password).
- Uses an internal client wrapper to communicate with the Librus API.
- Date filtering is applied if "From" and/or "To" properties are set.
- No additional external dependencies beyond the Librus API and n8n environment.
Troubleshooting
- No supported method found error: If the custom method name or operation does not match any available API methods, the node will throw an error listing available methods. Ensure the operation and custom method names are correct.
- Authentication errors: Invalid or missing credentials will prevent API access. Verify the API login and password are correctly configured.
- Date format issues: The "From" and "To" properties must be in
YYYY-MM-DDformat. Incorrect formats may cause filtering to fail or return no results. - Empty results: If the specified homework ID does not exist or is inaccessible, the output may be empty or null. Confirm the homework ID is valid.
Links and References
- Librus API Documentation (official API docs, if publicly available)
- n8n documentation on creating custom nodes
- General info on date filtering best practices
If you need details on other operations or resources, feel free to ask!