Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node interacts with the Librus API, a platform commonly used by schools for managing messages, homework, absences, calendars, and student information. Specifically, the "Messages" resource with the "Get Lucky Number" operation retrieves a student's lucky number from their account information.

Use cases include:

  • Fetching a student's lucky number as part of a broader workflow to analyze or display student data.
  • Integrating Librus data into other systems or dashboards where lucky numbers are relevant.
  • Automating reports or notifications that include this specific piece of student info.

Properties

Name Meaning
From Optional start date filter in YYYY-MM-DD format to limit data retrieval by date range.
To Optional end date filter in YYYY-MM-DD format to limit data retrieval by date range.
Custom method name Advanced option to override the default API method called (e.g., specify a different Librus API method).

Note: The "From" and "To" properties apply generally to filtering results by date but may not affect the "Get Lucky Number" operation directly since it fetches a single value.

Output

The output is a JSON object containing the lucky number data retrieved from the Librus API under the json field of the returned item. The structure depends on the API response but typically includes the lucky number and possibly related metadata.

No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "luckyNumber": 7,
  "studentId": "12345",
  "retrievedAt": "2024-06-01T12:00:00Z"
}

Dependencies

  • Requires an API key credential for authenticating with the Librus API.
  • The node uses an internal client wrapper to communicate with the Librus API endpoints.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • No supported method found error: This occurs if the specified operation or custom method name does not match any available API methods. Verify the operation name and ensure the custom method name (if used) is correct.
  • Authentication errors: Ensure the provided API credentials (login and password) are valid and have sufficient permissions.
  • Empty or unexpected responses: Check date filters ("From" and "To") to ensure they cover the expected data range. For "Get Lucky Number," these filters might be irrelevant.
  • Network or API downtime: Confirm network connectivity and Librus API availability.

Links and References

Discussion