Actions20
- Whatsapp Gupshup Actions
- Customer Actions
- Whatsapp Web Actions
Overview
This node integrates with the Cloudia platform to send messages, specifically supporting WhatsApp messaging via the Gupshup service. The "Send Text Template" operation under the "Whatsapp Gupshup" resource allows users to send templated text messages to customers on WhatsApp using predefined templates managed in Gupshup.
Typical use cases include:
- Sending automated notifications or alerts to customers.
- Delivering personalized messages using templates with variable parameters.
- Customer engagement through WhatsApp messaging campaigns.
For example, a business can send appointment reminders or promotional messages by specifying a template ID and filling in template parameters such as customer name or appointment date.
Properties
| Name | Meaning |
|---|---|
| Cloudia API Key | An API key for authenticating requests to Cloudia. Fill this if not using stored credentials. |
| Channel Integration ID | Numeric ID of the channel integration in Cloudia to which the message will be sent. |
| Phone Number | The recipient's phone number in international format (e.g., 5511999999999). |
| Name | The customer's name to personalize the message. |
| Template ID | Identifier of the WhatsApp message template to use. |
| Template Parameters | List of values to replace variables defined in the selected template. Each parameter is a string. |
| Additional Fields | Placeholder for any extra optional fields (currently empty in this context). |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output object contains the response from the Cloudia API after attempting to send the WhatsApp template message. This typically includes status information about the message delivery.
No binary data output is produced by this node.
Dependencies
- Requires access to the Cloudia API, specifically the endpoint handling WhatsApp Gupshup template messages.
- Needs either an API key provided directly in the node property or configured credentials within n8n.
- The "Channel Integration ID" must correspond to a valid integration set up in Cloudia.
- Network connectivity to Cloudia's API endpoints.
Troubleshooting
- Invalid API Key or Missing Credentials: If authentication fails, ensure the API key is correct and has necessary permissions.
- Incorrect Channel Integration ID: Using an invalid or inactive channel integration ID will cause message sending to fail.
- Template ID Not Found: Ensure the template ID exists and is active in the Gupshup account linked to Cloudia.
- Phone Number Format Issues: Phone numbers must be in the correct international format without spaces or special characters.
- Parameter Mismatch: The number and order of template parameters must match those expected by the template; otherwise, the message may not render correctly.
- API Request Errors: Network issues or Cloudia service downtime can cause errors; check logs and retry later.
Common error messages are surfaced from the Cloudia API and wrapped by the node. Users should verify all inputs and credentials when encountering errors.