Skip to main content
The WhatsApp node adds WhatsApp operations to your workflows. Add it on the canvas or ask the AI builder for it by name, then pick an operation and fill in its fields. WhatsApp also includes 2 trigger operations (marked in the tables below) that can start a workflow when something happens in WhatsApp.
You can wire the WhatsApp node into an AI agent as a tool provider: the agent calls the operations you allow. See Agent tools.
Scan the QR code once per phone number. If that connection later drops, scan again for the credential you already have instead of making a second one: the scan reconnects it in place, keeps the triggers registered on it, and does not start a second monthly connection fee. See Connecting accounts and Credential problems. A dropped link is not reported the instant it goes quiet. A restart at the provider can flap every connection for under a minute, and re-scanning a link that was about to come back adds a second device link, which risks logging the phone out of all of them. NoClick waits for the link to stay down before it emails you, and if it recovers on its own after an email went out, a follow-up tells you so and to leave the QR code alone. See Email notifications. When a QR connection delivers a message to an agent, the chat ID is often an opaque identifier rather than a phone number. The turn the agent reads names the sender as well: their WhatsApp display name and, where WhatsApp supplies one different from the chat ID, their phone number. In a group, the participant who wrote the message is named alongside them. That makes a standing instruction keyed on a person, such as treating one number as the supervisor, match. The reply address is still the chat ID, and the turn says so, so the agent does not answer a phone number instead. On the Receive Message trigger, NoClick fills in the Webhook URL itself and the field is read-only. Verify Token (Optional) belongs to the Cloud API subscription handshake, so it appears only on an access token credential and is hidden on a QR connection, which does not use it. A trigger that could not register says why, for example that the phone link is disconnected and needs reconnecting, and clears the message once a later attempt succeeds.

Credentials

Connect WhatsApp under Credentials in the node settings. See Connecting credentials for the general flow.

QR code

Connect by scanning a QR code when prompted. Connect your WhatsApp by scanning a QR code. A persistent connection fee of $0.99/month will be charged to your balance.

Access token

Enter the values manually when creating the credential.
  1. Go to Meta Developer Console 2. Select your app -> WhatsApp -> API Setup 3. Copy Phone Number ID and Access Token 4. For permanent token: Business Settings -> System Users -> Generate New Token
Get your credentials here.

Operations

Account

Chats

Media

Message

Phone

Profile

Template

Other