Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API, a platform commonly used by schools for managing student information, communication, and schedules. The node allows users to perform various operations related to school data such as retrieving messages, homework, absences, calendar events, grades, and account information.

Specifically, the Absence - Get Account Info operation fetches detailed account information about the user from the Librus system. This can be useful for scenarios where you want to automate retrieval of user profile details or verify account status within workflows.

Practical examples include:

  • Automatically fetching and logging user account info at the start of a workflow.
  • Using account info to personalize notifications or reports.
  • Integrating Librus account data into other systems like CRM or school management tools.

Properties

Name Meaning
Custom method name (Optional) Override the default Librus API method to call. For example, specify "getMarks" to call that method instead of the default one.

Output

The node outputs JSON data representing the response from the Librus API for the requested operation. For the Get Account Info operation, the output JSON contains the user's account details as returned by the API.

If the operation returns multiple items (arrays), each item is output as a separate JSON object in the array of items.

No binary data is produced for this operation.

Example output structure (simplified):

{
  "id": "user123",
  "name": "John Doe",
  "role": "Student",
  "email": "john.doe@example.com",
  ...
}

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • Uses an internal client wrapper to communicate with the Librus API.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • No supported method found error: If the specified resource-operation combination or custom method name does not match any available API methods, the node will throw an error listing available methods. Ensure the resource and operation names are correct and that the custom method name (if used) matches a valid API method.
  • Authentication errors: Invalid or missing credentials will cause authentication failures. Verify that the API login and password are correctly set in the node credentials.
  • Empty or unexpected responses: Check date range filters or parameters if the output is empty or incomplete.
  • Binary data handling: For operations returning files (not relevant here), ensure the binary property name is correctly set.

Links and References

Discussion