Actions4
- Send Message Actions
- Get List Actions
Overview
This node integrates with the Prinrcart API to interact with a Workchat messaging system. It supports sending messages, retrieving message details, and fetching user chat lists or contact lists. This node is useful for automating communication workflows, such as sending notifications, retrieving chat histories, or managing contact information within an organization.
Practical examples:
- Automatically send a message to a user when a specific event occurs.
- Retrieve detailed chat messages for auditing or analysis.
- Fetch lists of active user chats or contacts for display or further processing.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently only "API Token" is supported. |
| Resource | The category of action to perform: "Send Message" or "Get List". |
| Operation | Specific operation under the chosen resource: |
| - For "Send Message": "sendMessage", "getDetailMessage" | |
| - For "Get List": "userChatList", "getContactList" | |
| messageImport | (For sendMessage) The content of the message to be sent. |
| userId | (For sendMessage and getDetailMessage) The identifier of the user involved in the chat. |
| page | (For getContactList) The page number for paginated contact list retrieval. |
Output
The node outputs JSON data representing the response from the Prinrcart API for each executed operation:
- For sendMessage: Confirmation or details of the sent message.
- For getDetailMessage: Detailed chat messages for the specified user.
- For userChatList: A list of user chat sessions.
- For getContactList: A paginated list of contact chats.
No binary data output is produced by this node.
Dependencies
- Requires an API token credential for authenticating requests to the Prinrcart API.
- Makes HTTP requests to endpoints under
https://erp-amz.cloodo.com/v4/messages/. - Uses n8n's built-in request helper with authentication support.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Incorrect user IDs or page numbers may result in empty or error responses.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Errors returned from the API are propagated; typical messages include authorization errors or resource not found.
- If the node is set to continue on fail, errors are returned as part of the output JSON with an
errorfield describing the issue.
Resolution tips:
- Verify that the API token is correctly configured and has necessary permissions.
- Ensure user IDs and pagination parameters are valid.
- Check network access to the API endpoint.
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/