Actions4
- Send Message Actions
- Get List Actions
Overview
This node integrates with the Prinrcart API to send and retrieve messages within a work chat environment. Specifically, the "Send Message" operation allows users to send a message to a specified user by importing the message content and providing the recipient's user ID. This is useful in scenarios where automated messaging or notifications need to be sent programmatically, such as alerting team members, sending updates, or integrating chat functionality into workflows.
Example use cases:
- Automatically sending a notification message to a user when a certain event occurs.
- Importing and forwarding message content from another system into the work chat.
- Building custom chatbots or integrations that interact with users via messages.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" for accessing the API. |
| Message Import | The content or context of the message to be sent. This is a required string input. |
| User ID | The identifier of the user who will receive the message. |
Output
The node outputs an array of JSON objects representing the response from the Prinrcart API after sending the message. The exact structure depends on the API response but generally includes confirmation of message delivery or error details if the request failed.
No binary data output is produced by this node.
Dependencies
- Requires an API token credential for authenticating requests to the Prinrcart API.
- The node makes HTTP POST requests to
https://erp-amz.cloodo.com/v4/messages/sendendpoint. - Proper network access to the Prinrcart API service is necessary.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Incorrect or empty "Message Import" content may result in API errors or no message being sent.
- Providing an invalid or non-existent "User ID" will likely cause the API to reject the request.
Error messages:
- Authentication errors typically indicate problems with the API token; verify the token is correct and has proper permissions.
- Validation errors from the API may indicate missing required fields like message content or user ID.
- Network errors could occur if the API endpoint is unreachable; check internet connectivity and endpoint URL.
Links and References
- Prinrcart API documentation (not provided in source; consult your API provider)
- n8n HTTP Request node documentation for understanding requestWithAuthentication usage: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/