Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node operation, Send Stop Typing under the Chat resource, is designed to signal that a user has stopped typing in a chat conversation. It is useful in messaging automation workflows where you want to control or simulate typing indicators for chats, such as in customer support bots or interactive chat applications. For example, after sending a message or completing input processing, this node can notify the chat recipient that the typing indicator should be turned off.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a required numeric identifier for the specific instance of the service). |
| Chat Id | The unique identifier of the chat where the stop typing event will be sent. Format: <countrycode_short><usernumber>@c.us for individual chats or @g.us for groups. Default example: 50664083362@c.us. |
Output
The node outputs JSON data representing the response from the API call to send the "stop typing" event. This typically includes confirmation of the action or any relevant metadata returned by the API. There is no binary output associated with this operation.
Dependencies
- Requires an API key credential for authentication with the WaAPI service.
- Depends on the external WaAPI endpoint at
https://waapi.app/api/v1. - The node uses HTTP headers specifying JSON content type and accepts JSON responses.
- Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted Chat Ids may result in errors or no effect.
- Network connectivity problems can prevent reaching the WaAPI endpoint.
- Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Validation errors related to Chat Id format require ensuring the ID matches the expected pattern (
<countrycode><number>@c.usor@g.us). - Timeout or connection errors suggest checking network access and endpoint availability.
Links and References
- WaAPI Documentation (for detailed API usage and chat ID formats)
- n8n Documentation (for general node and credential setup guidance)