Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to manage and retrieve messages and related data such as homework, absences, calendar events, and grades. Specifically, for the Messages - Get Message operation, it fetches a single message from a specified folder by its ID.

Common scenarios where this node is useful include:

  • Retrieving detailed content of a specific message in a user's inbox or other folders.
  • Automating workflows that require reading or processing messages from Librus.
  • Integrating Librus messaging data into other systems or dashboards.

For example, you could use this node to automatically fetch a message by its ID when triggered, then parse and forward its content to another system or notify a user.

Properties

Name Meaning
From Optional start date filter (format: YYYY-MM-DD) to limit messages by date range.
To Optional end date filter (format: YYYY-MM-DD) to limit messages by date range.
Custom method name Advanced: override the default Librus API method called (e.g., getMarks).
Folder ID Numeric ID of the folder containing the message (default is 5, e.g., inbox).
Message ID Numeric ID of the message to retrieve. This is required for the "Get Message" operation.

Output

The output JSON contains the full details of the requested message as returned by the Librus API. The structure typically includes fields such as sender, recipients, subject, content, timestamps, and any metadata associated with the message.

If the node is used to get a file attachment (in other operations), it outputs binary data encoded in base64 under a configurable binary property, including MIME type and filename.

Dependencies

  • Requires an active connection to the Librus API using valid user credentials (login and password).
  • The node depends on the librus-api client wrapper internally to communicate with the API.
  • No additional external services are needed beyond the Librus API.
  • Proper configuration of credentials in n8n is necessary for authentication.

Troubleshooting

  • No supported method found error: If the node throws an error about no supported method found for the resource-operation combination, verify that the operation and resource names are correct and supported by the current version of the Librus API client.
  • Invalid Message ID or Folder ID: Ensure the message ID and folder ID exist and are accessible by the authenticated user; otherwise, the API may return errors or empty results.
  • Date filters not working: Confirm that the "From" and "To" dates are in the correct format (YYYY-MM-DD) and that the date range is valid.
  • Authentication failures: Check that the provided credentials are correct and have sufficient permissions to access messages.
  • Empty results: If no message is returned, verify that the message ID corresponds to a message in the specified folder.

Links and References

Discussion