Librus icon

Librus

Read data from Librus Synergia (unofficial)
Join our community

Actions105

Overview

This node integrates with the Librus API to manage messages and related data within the Librus educational platform. Specifically, the Send Message operation under the Messages resource allows users to send a message to a specified user by providing the recipient's user ID, a title, and content for the message.

Common scenarios where this node is beneficial include:

  • Automating communication between teachers and students or parents.
  • Sending notifications or announcements programmatically from workflows.
  • Integrating Librus messaging into broader automation pipelines for school management.

For example, a teacher could use this node in an automated workflow to send reminders about upcoming assignments or events directly to students' Librus inboxes.

Properties

Name Meaning
From Optional start date filter (YYYY-MM-DD). Used in some operations but not relevant here.
To Optional end date filter (YYYY-MM-DD). Used in some operations but not relevant here.
Custom method name Advanced: override the underlying Librus API method to call (e.g., getMarks).
User ID Required. The numeric ID of the recipient user to whom the message will be sent.
Title Required. The subject/title of the message being sent.
Content Required. The body/content text of the message.

Note: The "From" and "To" properties exist but are not used in the Send Message operation; they apply to other operations like listing messages.

Output

The output JSON contains the response from the Librus API after sending the message. This typically includes confirmation details such as message ID, status, timestamps, or any metadata returned by the API indicating success or failure.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "messageId": 12345,
  "status": "sent",
  "timestamp": "2024-06-01T12:34:56Z"
}

Dependencies

  • Requires valid credentials for the Librus API, including login and password.
  • The node uses an internal client wrapper to communicate with the Librus API.
  • No additional external services beyond the Librus API are required.
  • Ensure that the API credentials are configured correctly in n8n before using this node.

Troubleshooting

  • Error: No supported method found for resource "messages" on librus-api client.
    This indicates the node could not find the appropriate API method to call. Verify that the operation and resource parameters are set correctly and that the API client supports the requested action.

  • Authentication errors:
    If the node fails to authenticate, check that the provided API credentials (login and password) are correct and have sufficient permissions.

  • Invalid User ID or missing required fields:
    Ensure that the User ID, Title, and Content fields are all provided and valid. Missing these will cause the API call to fail.

  • API rate limits or connectivity issues:
    Network problems or API rate limiting may cause failures. Retry after some time or verify network access.

Links and References

Discussion