Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API to retrieve various types of information related to messages, homework, absences, calendar events, grades, notifications, and account info for a user. Specifically, the "Messages" resource with the "Get Account Info" operation fetches detailed account information about the user from the Librus system.

Common scenarios where this node is beneficial include:

  • Automating retrieval of user account details from Librus for integration with other systems.
  • Fetching message data or announcements within specified date ranges.
  • Accessing homework assignments, absences, timetable, calendar events, grades, and notifications programmatically.
  • Downloading message attachments as binary data.

Practical example:

  • A school administrator uses this node to automatically pull student account info and recent messages to sync with an internal dashboard.
  • A teacher automates fetching homework assignments and announcements for their classes within a given date range.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format to limit results to entries after this date. Applies to messages and homework resources.
To Optional end date filter in YYYY-MM-DD format to limit results to entries before this date. Applies to messages and homework resources.
Custom method name Advanced option to override the default underlying API method called (e.g., getMarks). Useful for calling specific API methods not covered by standard operations.

Output

The output is returned as JSON objects representing the data retrieved from the Librus API based on the selected resource and operation.

For the "Get Account Info" operation under the "Messages" resource, the output JSON contains detailed account information about the user, such as profile details and possibly linked data relevant to the user's account.

If the operation involves downloading files (e.g., message attachments), the node outputs binary data encoded in base64 with associated metadata including MIME type and filename.

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • The node expects proper configuration of these credentials within n8n to authenticate API requests.

Troubleshooting

  • No supported method found error: This occurs if the requested resource-operation combination does not map to any available API method. Verify that the resource and operation names are correct and supported.
  • Authentication failures: Ensure that the provided login and password credentials are valid and have sufficient permissions.
  • Date filtering issues: If no results appear when using the "From" and "To" date filters, check that dates are correctly formatted (YYYY-MM-DD) and that data exists within that range.
  • Binary data handling: When retrieving files, ensure the binary property name is set correctly to avoid missing or malformed file data.

Links and References

Discussion