WhatsApp — BizFirstAI Node Reference

What it does: The WhatsApp node (whatsapp) exposes Meta's WhatsApp Business Cloud API as workflow steps. It covers 72 operations across 8 resources — messaging (text, media, templates, interactive messages), media management, message templates, business profile and contact management, phone number lifecycle, QR-code deep links, WhatsApp groups, and commerce (product catalogs, collections, and orders).

Quick Start

Add a WhatsApp node to your workflow
Set resource to message and operation to send-text
Supply accessToken (or a vault credential) and phoneNumberId
Enter to (recipient in E.164 format, e.g. +14155551234) and text
Run the workflow — the node sends the message and returns the WhatsApp message ID and delivery status

Tip: Nearly every operation shares the same credential pair — accessToken and phoneNumberId — plus a small set of operation-specific fields. Learn the pattern once on Input & Output and every operation below follows it. First time setting up? Start with Authentication & Setup.

Pages in This Guide

Configuration

appsettings.json, HTTP client settings, and registration.

Authentication & Setup

Meta app setup, access tokens, and phone number IDs.

Message Operations

15 ops — text, media, interactive, template, and status messages.

Media Operations

Upload, download, delete, and inspect media assets.

Template Operations

Create, manage, and send pre-approved message templates.

Profile Operations

Contact names, business profile, account and verification info.

Phone Number Operations

QR Code Operations

Prefilled-message deep-link QR codes for click-to-chat.

Group Operations

Create groups, manage membership and admins, broadcast messages.

Commerce Operations

18 ops — catalogs, collections, products, and order webhooks.

Input & Output

The shared credential pattern and how errors surface.

Examples

Worked workflow patterns using this node.

Troubleshooting

Common errors and how to fix them.

Roadmap

send-and-wait completion and inbound webhook triggers.

Core Concepts

Cloud API, not a bot framework

Every operation on this node calls Meta's WhatsApp Business Cloud API (graph.facebook.com/v22.0 by default) directly over HTTPS. There's no on-premise WhatsApp Business App, no QR-code device pairing, and no unofficial browser automation involved — this is the same Cloud API used by Meta's own Business Platform integrations.

Resources

Operations are grouped by resource, matching the shape of the Cloud API itself:

message — send text, media, interactive, reaction, and template messages; mark as read; typing indicator
media — upload, download, delete, and inspect media handles
template — create, list, get, update, delete, and send message templates
profile — contact names, business profile, account info, verification status
phone-number — list, register, deregister, verify, and rename business phone numbers
qrcode — click-to-chat deep-link QR codes
group — group lifecycle, membership, admin roles, and broadcast
commerce — product catalogs, collections, products, and order intake

Credentials

Every operation needs an accessToken; most also need a phoneNumberId. See Authentication & Setup for how to obtain both from Meta and how the vault credential overrides inline config.

Operation Summary

Resource	Operations	Guide Page
`message`	15	Message Operations
`media`	4	Media Operations
`template`	6	Template Operations
`profile`	6	Profile Operations
`phone-number`	7	Phone Number Operations
`qrcode`	5	QR Code Operations
`group`	11	Group Operations
`commerce`	18	Commerce Operations

Total: 72 operations. One more — message/send-and-wait — is routed but not yet backed by a service implementation; see Roadmap.