Overview
This node sends chat messages to a service called "Lis" via its API. It is designed to post user messages into a specific chat thread managed by Lis, optionally specifying the chat interface type (API or WhatsApp) and controlling how many times the message handling should be retried in case of issues.
Common scenarios for this node include:
- Integrating automated workflows with the Lis chat system to send messages programmatically.
- Sending user inputs or notifications into a Lis-managed chat thread.
- Using different chat interfaces supported by Lis, such as a direct API or WhatsApp channel.
- Controlling retry attempts to improve message delivery reliability when interacting with AI-driven message handling.
Example use case: Automatically sending customer support queries collected from a form into a Lis chat thread, specifying retries to ensure the AI assistant processes the message correctly.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the chat thread where the message will be sent. |
| Data | The content of the chat message to send. |
| Maximum Retries | Number of times the AI should attempt to handle the message if issues occur during processing. |
| Chatinterface | The communication channel to use for sending the message; options are "API" or "WhatsApp". |
Output
The node outputs an array of JSON objects, each representing the response from the Lis API for each message sent. The structure of each JSON object corresponds to the API's response to posting a user message, which typically includes confirmation details or error information related to the message submission.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Lis service.
- The node makes HTTP POST requests to the Lis API endpoint
/agent/messages/user. - The Lis API base URL must be configured in the credentials used by the node.
Troubleshooting
- Authentication errors: Ensure the API key credential for Lis is correctly set up and has proper permissions.
- Invalid Thread ID: If the thread ID does not exist or is incorrect, the API may return an error. Verify the thread ID before sending messages.
- Message delivery failures: If messages fail to send, check network connectivity and Lis API status.
- Retries not effective: If the maximum retries do not resolve message handling issues, review the message content and Lis AI configuration.
- Unexpected API responses: Inspect the returned JSON for error messages or codes to diagnose issues.
Links and References
- Lis API documentation (not provided here; consult your Lis service provider for official docs)
- n8n HTTP Request node documentation for understanding request/response handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/