WhatsApi

Connect with WhatApp HTTP API

Actions29

Overview

The node enables sending bulk messages through a WhatsApp HTTP API by specifying message details in JSON format. It is useful for automating the distribution of messages to multiple recipients or groups, such as broadcasting announcements, alerts, or marketing campaigns. For example, a user can send a text message to a WhatsApp group by providing the group's ID and the message content.

Properties

Name	Meaning
Phone	The session identifier, typically the phone number associated with the WhatsApp session.
Body	The message payload in JSON format, including recipient ID (`jid`), message type, and the actual message content. Example: a group message with text "Okay then!".

Output

The node outputs JSON data representing the response from the WhatsApp HTTP API after attempting to send the bulk message. This typically includes status information about the message delivery. If binary data were involved (not indicated here), it would represent media attachments or similar content.

Dependencies

Requires connection to a WhatsApp HTTP API service.
Needs an API URL and authentication credentials configured in n8n (e.g., an API key or token).
Uses the @devlikeapro/n8n-openapi-node package internally to build request properties based on an OpenAPI specification.

Troubleshooting

Common issues:
- Invalid or missing session ID (Phone) may cause authentication failures.
- Malformed JSON in the Body property can lead to request errors.
- Incorrect jid (recipient ID) or unsupported message types may result in message delivery failure.
Error messages:
- Authentication errors indicate problems with the provided API credentials or session ID.
- Validation errors suggest incorrect or incomplete message payloads.
Resolutions:
- Verify that the session ID corresponds to an active WhatsApp session.
- Ensure the JSON body is correctly formatted and includes all required fields.
- Confirm the recipient IDs are valid WhatsApp numbers or group IDs.