Actions105
- Info Actions
- Messages Actions
- Homework Actions
- Absence Actions
- Calendar Actions
Overview
This node integrates with the Librus API, a platform commonly used by schools for managing educational data and communication. The "Calendar" resource with the "Send Message" operation allows users to send messages through the Librus system. This can be useful for teachers or school staff who want to programmatically send announcements, notifications, or direct messages to students, parents, or colleagues.
Practical examples include:
- Sending reminders about upcoming events or deadlines.
- Notifying students or parents about schedule changes.
- Distributing homework assignments or important notices.
Properties
| Name | Meaning |
|---|---|
| Custom method name | Advanced: override the underlying Librus API method to call (e.g., getMarks). If set, this custom method will be used instead of the default one for sending messages. |
Note: Other parameters such as userId, title, content, group, attachmentPath, etc., are used internally in the node but are not exposed in the provided properties JSON. They represent typical message fields like recipient, subject, body, and attachments.
Output
The output is a JSON object representing the response from the Librus API after attempting to send a message. It typically contains details about the sent message or confirmation of success.
If the operation involves file retrieval (not applicable here), the node can output binary data encoded in base64 with MIME type and filename metadata.
Dependencies
- Requires an API key credential for authenticating with the Librus API (login and password).
- Uses an internal client wrapper (
LibrusClientWrapper) to interact with the Librus API. - No additional external dependencies beyond the configured API credentials.
Troubleshooting
- No supported method found error: If the custom method name or operation does not match any available API methods, the node throws an error listing available methods. Ensure the operation and custom method names are correct.
- Authentication errors: Invalid or missing API credentials will prevent successful connection. Verify that login and password are correctly configured.
- Empty or malformed responses: Check date range filters and input parameters to ensure they are valid and correspond to existing data.
- Binary data handling: When retrieving files, ensure the binary property name is correctly set to avoid missing or corrupted attachments.
Links and References
- Librus Official Website (for general platform info)
- No direct public API documentation linked in the code; refer to your Librus API provider or internal documentation for detailed API method descriptions.