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 educational data. Specifically, the "Calendar" resource with the "Get Account Info" operation retrieves detailed account information about the authenticated user.

Typical use cases include:

  • Fetching user profile details to personalize workflows.
  • Verifying account status or metadata before performing other operations.
  • Integrating user info into broader automation scenarios involving school data.

For example, an educator might use this node to automatically pull their account info and then trigger notifications or reports based on that data.

Properties

Name Meaning
Custom method name (Optional) Override the default API method called by specifying a custom method name.

The only input property relevant here is Custom method name, which allows advanced users to specify a different underlying API method than the default one for this operation.

Output

The output is a JSON object containing the user's account information as returned by the Librus API. This typically includes personal details, roles, permissions, and other metadata associated with the account.

The node does not produce binary data for this operation.

Example output structure (simplified):

{
  "userId": "12345",
  "name": "John Doe",
  "role": "Teacher",
  "email": "john.doe@example.com",
  ...
}

Dependencies

  • Requires valid credentials for the Librus API (login and password).
  • The node uses an internal client wrapper to communicate with the Librus API.
  • No additional external services are required beyond the Librus API itself.

Troubleshooting

  • No supported method found error: If the node cannot find a matching API method for the requested resource and operation, it will throw an error listing available methods. This can happen if the operation name is incorrect or if the API has changed. Verify the operation name and update the node accordingly.
  • Authentication errors: Ensure that the provided login and password credentials are correct and have sufficient permissions.
  • Empty or unexpected output: Check date range filters or parameters if applicable; although for this operation, no date filters apply.
  • Custom method name misuse: Providing an invalid custom method name may cause the node to fail finding the method. Use this option only if you know the exact API method to call.

Links and References

Discussion