Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Send Text In Session" operation of the WTS Chat node allows sending a text message directly within an existing chat session identified by its Session ID. This is useful for continuing conversations in ongoing sessions without starting new ones, ensuring context continuity.
Typical use cases include:
- Customer support agents sending follow-up messages in active chat sessions.
- Automated workflows that send notifications or updates to users within their current chat session.
- Bots or integrations that need to inject messages into a specific session context.
Example: Sending a confirmation message to a user in a support session after processing their request.
Properties
| Name | Meaning |
|---|---|
| Text | The actual text content you want to send in the session. |
| Session ID | The unique identifier of the chat session where the text message will be sent. |
| Send Synchronous Message | Boolean flag indicating whether the message should be sent synchronously (true) or asynchronously (false). |
Output
The node outputs JSON data representing the response from the API after sending the text message in the session. This typically includes details about the sent message such as message ID, status, timestamps, and any metadata returned by the service.
If the operation succeeds, the output JSON contains the message object confirming the message was sent within the specified session.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the WTS Chat API.
- The node depends on the external WTS Chat service endpoints to send messages.
- Proper configuration of the API base URL and credentials in n8n is necessary.
Troubleshooting
SessionID is empty!
Error thrown if the Session ID property is missing or empty. Ensure the Session ID is correctly provided.API errors
If the API key is invalid or expired, the node will throw authentication errors. Verify the API key credential is valid.Empty Text message
Although not explicitly checked here, sending an empty text might cause API rejection. Always provide non-empty text.Network or service downtime
Temporary failures in connecting to the WTS Chat API can cause errors. Retry or check service status.
Links and References
- WTS Chat API Documentation (generic link, replace with actual if available)
- n8n documentation on Creating Custom Nodes
- General info on chat session management and messaging APIs