WTS Chat icon

WTS Chat

Get data from Wts API
Join our community

Actions39

Overview

This node operation sends a chatbot message through the WTS Chat API. It allows users to specify the chatbot to use, the channel from which the message is sent, the recipient's number, and session details. It supports options to skip sending if another bot is running or if a conversation is in progress, and can force start a session. Additionally, it allows attaching metadata to both the session and the contact for enhanced context.

Use Case Examples

  1. Automate sending chatbot messages to customers on a specified channel and session.
  2. Send chatbot messages conditionally based on whether another bot is active or a conversation is ongoing.
  3. Attach custom metadata to sessions and contacts when sending chatbot messages for personalized interactions.

Properties

Name Meaning
Session ID Identifier for the chat session to which the chatbot message is related.
Chatbot Name or ID Select or specify the chatbot to send the message from.
From Name or ID Select or specify the channel from which the chatbot message is sent.
To The recipient's number to which the chatbot message will be sent.
Force Start Session Boolean flag to force the start of a new session when sending the chatbot message.
Skip If Bot In Execution Boolean flag to skip sending the chatbot message if another chatbot is currently running.
Skip If In Progress Boolean flag to skip sending the chatbot message if a conversation is already in progress.
Session Metadata Key-value pairs to add metadata to the session when sending the chatbot message.
Contacts Metadata Key-value pairs to add metadata to the contact when sending the chatbot message.

Output

JSON

  • json - Response from the WTS Chat API after sending the chatbot message, containing details about the sent message or operation status.

Dependencies

  • WTS Chat API

Troubleshooting

  • Ensure that the 'Chatbot Name or ID' and 'From Name or ID' (channel) are selected or specified correctly; otherwise, the message will not be sent.
  • Verify that the 'To' field (recipient number) is provided; missing this will cause an error.
  • If using file inputs for attachments, ensure the binary data is correctly provided in the input to avoid errors about missing files.
  • Check API key credentials are correctly configured and valid to avoid authentication errors.
  • If the node throws errors about empty Session ID or invalid template selection, verify the corresponding input fields are filled properly.

Discussion