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 messages, homework, absences, calendars, and grades. Specifically, the "Delete Message" operation under the "Homework" resource allows users to delete a message by its ID within the Librus system.
Typical use cases include automating the removal of outdated or irrelevant messages related to homework assignments, streamlining communication management in educational workflows, or cleaning up message inboxes programmatically.
For example, a teacher could set up an automation that deletes homework-related messages older than a certain date, helping maintain an organized messaging environment without manual intervention.
Properties
| Name | Meaning |
|---|---|
| From | Optional start date (YYYY-MM-DD) to filter messages or data by date range. |
| To | Optional end date (YYYY-MM-DD) to filter messages or data by date range. |
| Custom method name | Advanced option to override the default underlying API method called (e.g., getMarks). |
Note: Although the provided properties are generic and shared across multiple resources, for the "Delete Message" operation specifically, the key parameter used internally is the message ID to delete, which is not listed here but is retrieved internally as deleteMessageId.
Output
The output of this node is JSON data representing the result of the delete operation. Typically, this will be a confirmation object or status indicating whether the message was successfully deleted.
- If the operation returns binary data (not typical for delete), it would be handled accordingly, but for "Delete Message," the output is JSON.
- The output JSON structure depends on the Librus API response for the delete message call, usually including success status or error details.
Example output JSON might look like:
{
"success": true,
"messageId": 12345
}
Dependencies
- Requires valid credentials for the Librus API (login and password).
- Uses an internal client wrapper (
LibrusClientWrapper) to interact with the Librus API. - No additional external dependencies beyond the configured API credentials.
Troubleshooting
- No supported method found error: This occurs if the node cannot find the appropriate API method to call for the given resource and operation. Ensure the operation and resource names are correct and supported.
- Authentication errors: Verify that the provided API credentials (login and password) are correct and have sufficient permissions.
- Date filtering issues: If using the "From" and "To" properties, ensure dates are in the correct format (YYYY-MM-DD). Incorrect formats may cause unexpected results or no filtering.
- Message ID missing or invalid: For deleting a message, the message ID must be correctly specified; otherwise, the API call will fail.
Links and References
- Librus API Documentation (if publicly available)
- n8n documentation on creating custom nodes
- General info about Librus platform: https://www.librus.pl/
If you need further details on other operations or resources, feel free to ask!