LibrusInstall

Overview

This node integrates with the Librus API, a platform commonly used in Polish schools for managing student information such as absences, grades, messages, homework, and calendar events. The node allows users to perform various operations on different resources within the Librus system.

Specifically, the Absence - Get Lucky Number operation retrieves the "lucky number" associated with the user account from the Librus system. This could be useful in scenarios where the lucky number is part of a gamification or reward system integrated into the school platform.

Practical examples:

• Automatically fetch the lucky number of a student to display it in a custom dashboard.
• Use the lucky number as part of a notification or report sent to parents or teachers.

Properties

Note: For the Get Lucky Number operation, no additional input properties are required beyond authentication credentials and the optional custom method name.

Output

The output is a JSON object containing the data returned by the Librus API's method that fetches the lucky number. The structure depends on the API response but typically includes the lucky number value and possibly related metadata.

No binary data output is expected for this operation.

Example output JSON might look like:

{
  "luckyNumber": 7,
  "description": "Your lucky number for today"
}

Dependencies

• Requires valid Librus API credentials (login and password) configured in n8n.
• Uses an internal client wrapper to communicate with the Librus API.
• No external environment variables beyond the credentials are needed.

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 operation name matches exactly and that the API credentials have sufficient permissions.
• Authentication failures: Ensure the provided login and password are correct and that the Librus API service is accessible.
• Empty or unexpected output: Confirm that the user account has a lucky number assigned and that the API endpoint is functioning properly.
• Custom method name issues: If using the custom method name property, ensure the method exists in the underlying API client; otherwise, the node will throw an error listing available methods.

Links and References

• Librus Official Website
• (No public official API documentation available; usage relies on the internal client wrapper.)