LibrusInstall

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing educational data such as messages, homework, absences, calendars, and grades. The node allows users to perform various operations on different resources within Librus, including deleting messages under the "Absence" resource.

Specifically, the Delete Message operation under the Absence resource enables users to remove a message by its ID from their Librus inbox or related message folders. This is useful for automating message management tasks, such as cleaning up old notifications or removing irrelevant communications programmatically.

Practical examples include:

• Automatically deleting absence-related messages after processing them.
• Cleaning up message inboxes based on custom workflows.
• Integrating Librus message deletion into broader school administration automation.

Properties

Note: Although only the "Custom method name" property is explicitly defined here, the node internally uses other parameters like messageId or deleteMessageId to identify which message to delete, but these are not exposed in the provided input properties JSON.

Output

The node outputs an array of items where each item contains a json field representing the response from the Librus API for the delete message operation.

• For the Delete Message operation, the output JSON typically contains confirmation or status information about the deletion request.
• If the operation returns multiple results (e.g., batch deletes), the output will be an array of such JSON objects.
• The node does not output binary data for this operation.

Example output structure (simplified):

[
  {
    "json": {
      "success": true,
      "messageId": 12345,
      "status": "deleted"
    }
  }
]

Dependencies

• Requires valid credentials for the Librus API, specifically a login and password.
• Uses an internal client wrapper (LibrusClientWrapper) to interact with the Librus API.
• No additional external services beyond the Librus API are required.
• The node expects proper configuration of credentials within n8n to authenticate API requests.

Troubleshooting

• No supported method found error: If the node throws an error indicating no supported method was found for the resource-operation combination, it usually means the operation or resource is not implemented or incorrectly specified. Verify that the Resource is set to "Absence" and Operation to "Delete Message" exactly.
• Authentication errors: Ensure that the Librus API credentials (login and password) are correct and have sufficient permissions.
• Invalid message ID: Deletion will fail if the provided message ID does not exist or the user lacks permission to delete it. Double-check the message ID parameter.
• Empty or unexpected responses: If the node returns empty arrays or unexpected data, verify date filters or other parameters are correctly set.
• Custom method name misuse: Using an incorrect custom method name can cause the node to fail finding the method. Use this feature only if you know the exact underlying API method to call.

Links and References

• Librus Official Website – For general information about the platform.
• n8n Documentation – For guidance on using credentials and creating custom nodes.
• (No public official Librus API documentation is linked here due to lack of availability in the source code.)