WTS Chat

Get data from Wts API

Actions17

Overview

The node "WTS Chat" integrates with the Helena API to manage contacts, messages, sessions, and panels. Specifically for the Message resource and the Send Message Text operation, it allows sending plain text messages through a specified communication channel to a target phone number.

This operation is useful in scenarios such as:

Automating customer support replies via chat channels.
Sending notifications or alerts to users on messaging platforms.
Integrating chatbot responses with human agent handoffs.

For example, you can send a text message from a specific channel (like WhatsApp or SMS) to a customer's phone number, optionally associating the message with a session, department, bot, or user, and control session behavior like starting a new session or hiding it.

Properties

Name	Meaning
Session ID	The identifier of an existing chat session to associate the message with. Optional.
From Name or ID	The channel (e.g., WhatsApp, SMS) from which the message will be sent. Choose from a list or specify an ID dynamically.
To	The recipient's phone number to which the text message will be sent.
Text	The content of the text message to send.
Bots Name or ID	Optionally select a chatbot to activate when the contact responds. Choose from a list or specify an ID dynamically.
Departments Name or ID	Optionally specify the department related to this message. Choose from a list or specify an ID dynamically.
User Name or ID	Optionally specify a user within the selected department who is responsible for the message. This list updates based on the chosen department.
Contact ID	Optionally specify the contact ID related to the message.
Enable Bot	Boolean flag indicating whether to activate the chatbot upon receiving a response from the contact.
Hidden Session	Boolean flag indicating whether the session should be hidden.
Force Start Session	Boolean flag indicating whether to force start a new session if none exists.

Output

The output is a JSON object representing the response from the Helena API after sending the message. It typically includes details about the sent message such as message ID, status, timestamps, and any metadata returned by the API.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "string",
  "from": "string",
  "to": "string",
  "body": {
    "text": "string"
  },
  "status": "string",
  "createdAt": "string",
  "sessionId": "string",
  "botId": "string",
  "userId": "string",
  "departmentId": "string",
  "options": {
    "enableBot": true,
    "hiddenSession": false,
    "forceStartSession": false
  }
}

Dependencies

Requires an API key credential for authentication with the Helena API.
Uses the Helena API endpoint at https://api-test.helena.run.
Relies on n8n's HTTP request capabilities (axios) to communicate with the API.
Dynamic option loading depends on API calls to fetch available channels, bots, departments, and users.

Troubleshooting

Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect or missing required parameters such as channel ID or recipient number may result in API errors.
- Network connectivity issues can prevent successful API calls.
- If the session ID provided does not exist or is invalid, the message may fail to send or be associated incorrectly.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Validation errors from the API may indicate missing or malformed parameters; ensure all required fields are correctly filled.
- Timeout or network errors suggest connectivity problems; check your internet connection and API availability.

Links and References

Helena API Documentation (hypothetical link, replace with actual if available)
n8n Expressions Documentation
Axios HTTP Client

WTS ChatInstall