Incoming/outgoing WhatsApp message Trigger
AI-generatedOverview
This node acts as a trigger for incoming and outgoing WhatsApp messages from WhatsAble services. It listens for webhook HTTP POST requests and triggers workflows when messages are received. It supports automatic transcription of incoming audio messages to text, which is included in the webhook payload. This node is useful for automating responses or processing WhatsApp messages in real-time, such as customer support automation or message logging.
Use Case Examples
- Trigger a workflow when a new WhatsApp message arrives via WhatsAble services.
- Automatically transcribe incoming audio messages and use the text in subsequent workflow steps.
- Respond immediately or after the workflow finishes processing the message.
Properties
| Name | Meaning |
|---|---|
| Credential Type | Selects which WhatsAble API to use for the incoming or outgoing message trigger. Options include Notifyer System, WhatsAble Trigger, Notifier (Legacy), and Notifyer System for both incoming and outgoing messages. |
| HTTP Method | The HTTP method the webhook listens to, currently only POST is supported. |
| Respond | Determines when the webhook responds to the incoming request: immediately upon receipt or after the last node in the workflow finishes executing. |
Output
JSON
body- The JSON payload received from the WhatsAble webhook, containing message details including any transcribed audio text.
Dependencies
- Requires credentials for the selected WhatsAble API (Notifyer System, WhatsAble Trigger, Notifier Legacy, or Notifyer System All).
Troubleshooting
- Ensure the webhook URL is correctly configured in the WhatsAble service to send POST requests to the node's webhook path.
- If no messages trigger the workflow, verify that the correct Credential Type is selected and that the credentials are valid.
- If audio transcription is expected but missing, confirm that the incoming audio messages are supported and that transcription is enabled on the WhatsAble service side.