Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
This node integrates with the WTS Chat API to perform various operations related to messaging, contacts, sessions, panels, chatbots, and sequences. Specifically for the Message resource and the Get Message Status operation, it retrieves the current status of a message by its unique identifier.
Common scenarios where this node is beneficial include:
- Tracking the delivery or read status of messages sent through the WTS Chat platform.
- Monitoring message lifecycle events in automated workflows.
- Integrating message status checks into customer support or CRM automation pipelines.
For example, after sending a message via WTS Chat, you can use this node to query whether the message was delivered, read, or failed, enabling conditional logic based on message state.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the message whose status you want to retrieve. |
Output
The node outputs JSON data containing the status information of the specified message. The exact structure depends on the WTS Chat API response but typically includes fields such as delivery status, read receipts, timestamps, and any error codes if applicable.
No binary data output is produced by this operation.
Example output (conceptual):
{
"messageId": "12345",
"status": "delivered",
"deliveredAt": "2024-04-01T12:34:56Z",
"readAt": "2024-04-01T12:40:00Z"
}
Dependencies
- Requires an active connection to the WTS Chat API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for API requests is
https://api.wts.chat. - No additional external dependencies are required beyond the configured API credentials.
Troubleshooting
- Invalid or missing Message ID: If the Message ID property is empty or invalid, the node will throw an error indicating that the ID must be provided.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- API connectivity issues: Network problems or incorrect base URL configuration may cause request failures.
- Unexpected API errors: The node wraps API errors and surfaces them; check the error message for details and verify the message ID exists in the WTS Chat system.
Links and References
- WTS Chat API Documentation (general reference for API endpoints and message status details)
- n8n documentation on creating custom nodes