Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The WTS Chat node for n8n allows you to interact with the Wts API, specifically to manage and retrieve information about messages, contacts, sessions, panels, sequences, and chatbots.
For the Resource: Message and Operation: Get Message By ID, this node retrieves detailed information about a specific message using its unique identifier.
Common scenarios:
- Fetching the full details of a sent or received message for logging, auditing, or further automation.
- Integrating message data into other workflows, such as CRM updates or notifications.
- Troubleshooting delivery or content issues by retrieving the exact message payload.
Practical example:
You have an automated workflow that needs to fetch the status or content of a WhatsApp message after it has been sent, in order to update a database or trigger follow-up actions.
Properties
| Display Name | Type | Description |
|---|---|---|
| Message ID | String | The unique identifier of the message to retrieve. This is required to fetch the message details. |
Output
The output will be a single item with a json field containing the message details as returned by the Wts API. The structure of this object depends on the API response, but typically includes fields such as:
{
"id": "string",
"from": "string",
"to": "string",
"body": {
"text": "string",
// ...other possible fields depending on message type
},
"status": "string",
"timestamp": "string",
// ...additional metadata fields
}
- The actual fields may vary based on the message type and the Wts API version.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Wts API (https://api.wts.chat).
- API Key: You must configure valid Wts API credentials (
wtsApi) in your n8n instance. - n8n Configuration: Ensure the WTS Chat node is installed and properly configured with the necessary credentials.
Troubleshooting
Common Issues:
- Invalid or missing Message ID: If the Message ID is empty or incorrect, the node will throw an error indicating that the message could not be found.
- Authentication errors: If the API key is missing or invalid, you will receive authentication-related errors from the Wts API.
- Network/API errors: Any connectivity issues or API downtime will result in error messages.
Error Messages & Resolutions:
"There is no data in the input": Ensure you provide a valid Message ID."NodeApiError": This is a generic wrapper for API errors; check the error message for more details (e.g., invalid credentials, not found, etc.)."Fill in the field": Indicates a required property was left empty—ensure all mandatory fields are filled.
Links and References
- Wts API Documentation (refer to official docs for message schema)
- n8n Documentation: Credentials
- n8n Community Forum