Actions19
- Agent Actions
- Campaign Actions
- Contact Actions
- Custom Field Actions
- Label Actions
- WhatsApp Actions
Overview
The Wasapi node integrates with the Wasapi API to send WhatsApp flows programmatically. Specifically, the Send Flow operation under the WhatsApp resource allows users to trigger a predefined WhatsApp flow (a sequence of messages or interactions) to a specified recipient phone number.
This node is beneficial in scenarios such as:
- Automating customer support conversations by sending interactive WhatsApp flows.
- Triggering marketing campaigns or notifications via WhatsApp flows.
- Integrating WhatsApp messaging into broader automation workflows for personalized communication.
For example, a business can use this node to send a welcome flow to new customers automatically after signup, or to deliver order updates through a structured WhatsApp conversation.
Properties
| Name | Meaning |
|---|---|
| Phone Wasapi Name or ID | Select the phone number associated with your Wasapi account from a list or specify its ID using an expression. This identifies the sender WhatsApp number. |
| WhatsApp ID | The recipient's phone number including country code but without the "+" sign. For example, "573203294920". |
| Flow Name or ID | Choose the WhatsApp flow to send from a searchable list or specify its ID via expression. This defines the message sequence that will be sent. |
| Screen Principal Name or ID | Select the screen within the flow to start from, either from a list or by specifying its ID. Screens represent specific steps or views in the flow. |
| Message | A custom message string to include or override in the flow. |
| Call to Action | A call-to-action text string to include in the flow, prompting the recipient to take a specific action. |
Output
The node outputs JSON data representing the response from the Wasapi API after attempting to send the WhatsApp flow. This typically includes status information about the message delivery, any errors, and metadata related to the flow execution.
If the API supports binary data (e.g., media attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON describing the flow send operation result.
Dependencies
- Requires an active Wasapi API account with valid credentials (an API key or token).
- The node configuration must include these credentials to authenticate requests.
- Network access to
https://api-ws.wasapi.io/api/v1is necessary. - The node uses helper methods to load options dynamically for phone numbers, flows, screens, labels, and agents.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect phone number format (missing country code or including "+") may lead to message rejection.
- Specifying non-existent flow or screen IDs will result in errors from the API.
- Network connectivity issues can prevent successful API calls.
Error Messages:
"Resource \"whatsapp\" with operation \"sendFlow\" is not supported"indicates a misconfiguration or unsupported operation selection.- API error responses usually contain descriptive messages; ensure to check the node output for details.
Resolutions:
- Verify and update API credentials in n8n.
- Ensure phone numbers are formatted correctly as per instructions.
- Use the dynamic option lists to select valid flows and screens.
- Check network connectivity and firewall settings.