Librus icon

Librus

Read data from Librus Synergia (unofficial)

Overview

This node integrates with the Librus API, a platform commonly used in educational environments for managing school-related data such as messages, homework, absences, calendar events, and grades. Specifically, the Calendar - Delete Message operation allows users to delete a message from their inbox within the Librus system.

Typical use cases include automating the cleanup of messages, managing notifications, or integrating Librus messaging with other workflows like alerts or record keeping. For example, a school administrator could automatically remove outdated announcements or a teacher might clear messages after processing them.

Properties

Name Meaning
Custom method name (Optional) Override the default underlying API method to call. Example: getMarks.

Note: The node also internally uses parameters such as resource, operation, messageId, and deleteMessageId to identify what action to perform and on which message, but only the above property is explicitly defined in the provided input properties JSON.

Output

The output of this node is an array of items where each item contains a json field representing the response from the Librus API for the requested operation.

  • For the Delete Message operation, the output JSON typically contains the result of the deletion request, which may be a confirmation object or status indicating success or failure.
  • If the operation involves retrieving files (not applicable here), binary data would be returned encoded in base64 with MIME type information.
  • The output structure is consistent with n8n's standard format: an array of objects each having a json property with the API response.

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 are required beyond access to the Librus platform.
  • The node expects proper configuration of credentials within n8n to authenticate API requests.

Troubleshooting

  • No supported method found error: This occurs if the specified resource-operation combination does not match any known API methods. Ensure that the resource is set to "Calendar" and the operation to "Delete Message" correctly, or provide a valid custom method name.
  • Authentication errors: Invalid or missing credentials will prevent API access. Verify that the login and password are correct and properly configured in n8n.
  • Empty or unexpected responses: Check that the messageId or deleteMessageId parameter corresponds to an existing message in the user's inbox.
  • Date filtering issues: Some operations support date range filtering; ensure date formats are correct if used.
  • Binary data handling: For file retrieval operations, ensure the binary property name is set correctly to avoid data loss.

Links and References

Discussion