WaAPI

Interact with WaAPI API

Actions83

Overview

The node provides an operation to send a "typing" indicator to a WhatsApp chat via the WaAPI service. This is useful in scenarios where you want to simulate or notify that a user (or bot) is currently typing a message in a specific chat, enhancing the interactivity and responsiveness of chatbots or automation workflows.

Practical examples include:

Indicating to a customer that a support agent or bot is preparing a response.
Creating more natural conversational flows by showing typing status before sending messages.
Integrating with other systems to trigger typing notifications based on external events.

Properties

Name	Meaning
Id	Instance ID (a required numeric identifier for the WaAPI instance).
Chat Id	The target chat's unique identifier in WhatsApp format: `<countrycode><usernumber>@c.us` for individual chats or `@g.us` for groups.

Output

The node outputs JSON data representing the result of the "send typing" request to the WaAPI API. This typically includes confirmation of the typing event being sent successfully or error details if it failed.

No binary data output is involved.

Dependencies

Requires an active connection to the WaAPI service via its REST API at https://waapi.app/api/v1.
Needs an API key credential configured in n8n to authenticate requests to WaAPI.
The node depends on the @devlikeapro/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted Chat Ids may lead to errors or no effect.
- Network connectivity problems can prevent communication with the WaAPI endpoint.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Validation errors on Chat Id suggest checking the format matches WhatsApp standards.
- Timeout or network errors require checking internet access and WaAPI service status.