WhatsApp Business API by Automations Builder icon

WhatsApp Business API by Automations Builder

Send WhatsApp Business API session and template messages

WhatsApp Business API by Automations Builder

AI-generated

Summary

Sends a WhatsApp Business message to one recipient per input item through the Automations Builder proxy (crmapi.1automations.com, Meta Graph-style API). The message kind is chosen by the node's operation: text, media, location, contacts, interactive buttons or list, reaction, or an approved template.

Inputs

  • Recipient Phone Number (to) (required) — E.164 number such as +15551234567. Spaces, dashes and parentheses are stripped, as is the leading +. An empty value throws an error.
  • Message Text / Enable URL Preview — sendText: the body text (required) and whether to expand the first URL into a preview card (default true).
  • Media Type, Source, Media URL / Media ID, Caption, Filename — sendMedia: audio, document, image, sticker or video. Send by public URL (link) or by an uploaded media ID. Caption applies to image, video and document. Filename applies to document.
  • Latitude, Longitude, Location Name, Address — sendLocation: coordinates are required. Name and address are optional and omitted if blank.
  • Contacts — sendContacts: one or more contact cards. Each can have name parts, formatted name (auto-built from first/middle/last if blank), birthday, organization, phones, emails, websites and addresses. At least one contact is required.
  • Interactive Type, Body Text, Header, Footer, Buttons / List Button Text and Sections — sendInteractive: Reply Buttons (id and title each) or List (button label and sections with rows). The body is required. The header can be text, or image, video or document by public URL for buttons (list allows text only). The footer is optional.
  • Message ID and Emoji — sendReaction: the wamid of the message to react to, and the emoji. An empty emoji removes a previous reaction.
  • Template Name and Variables — sendTemplate: pick an approved template loaded from the WABA on the credential, then fill its variables (such as body#1 or header#image). The {{waba}} placeholder is auto-filled with the recipient. The template's stored JSON payload is used as the base.
  • Reply to Message ID — A wamid to quote-reply to. It is added as context to every send operation except sendReaction. For sendTemplate it is set on the payload directly.

Output shape

One output item per input item, containing the API response JSON from the POST to /{phoneNumberId}/messages (typically message IDs and recipient contact info), paired to its input item.

The credential must include a Phone Number ID, and the WABA ID for template loading. With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow. A template that isn't found, or one with no json payload, raises an error.

Examples

Example 1: Send an order confirmation with quick-reply buttons

Operation: Send Interactive; Interactive Type: Reply Buttons; To: {{$json.phone}}; Body: 'Confirm your order?'; Buttons: id yes/title Yes, id no/title No.

Example 2: Send an approved template outside the 24-hour window

Operation: Send Template; To: {{$json.phone}}; Template Name: pick from list; Variables: fill body#1 with {{$json.name}}.

Example 3: Send a PDF invoice

Operation: Send Media; Media Type: Document; Source: By Public URL; Media URL: invoice link; Filename: invoice.pdf; Caption: 'Your invoice'.

Links

Discussion