Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API, a platform commonly used in educational environments for managing school-related information. The node allows users to perform various operations on different resources such as messages, homework, absences, calendar events, and general info.

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

Practical examples:

  • Automatically deleting notification messages after processing them.
  • Cleaning up spam or unwanted messages based on certain criteria.
  • Integrating message deletion into broader workflows involving student or teacher communications.

Properties

Name Meaning
Custom method name (Optional) Override the default underlying API method to call. For example, specify a custom method like getMarks if needed.

Note: Although only one property is explicitly defined here, the node internally supports many other parameters depending on the resource and operation selected (e.g., messageId, folderId, page, userId, etc.). For the Delete Message operation, the key input is the message ID to delete.

Output

The output of this node is JSON data representing the result of the delete operation. Typically, this will be an object confirming the success or failure of the deletion request.

If the operation involves file retrieval (not applicable here), the node can output binary data encoded in base64 with associated metadata such as MIME type and filename.

For the Delete Message operation, the output JSON usually contains confirmation details returned by the API about the deleted message.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • No supported method found error: If the node throws an error indicating no supported method was found for the resource-operation combination, verify that the resource and operation names are correct and supported by the current version of the API client.
  • Authentication errors: Ensure that the provided login and password credentials are correct and have sufficient permissions.
  • Message ID issues: When deleting a message, ensure the message ID exists and belongs to the authenticated user; otherwise, the API may return an error.
  • Empty or unexpected responses: Check date filters or pagination parameters if results are empty or incomplete.

Links and References

Discussion