Skip to main content

GoHighLevel → WhatsApp: Send a Message from a Workflow

Send WhatsApp messages automatically from GoHighLevel workflows using the Send WhatsApp via TimelinesAI action — choose a sender number, personalize with merge tags, and see example use cases.

This guide shows how to send a WhatsApp message automatically from a GoHighLevel workflow using the "Send WhatsApp via TimelinesAI" action — for example, sending an appointment reminder when a booking is confirmed, or a welcome message when a new lead enters your pipeline.

Example: When a new lead's status changes to "Booked," send a WhatsApp message: "Thanks for booking! We'll see you at your scheduled time."

Make sure the TimelinesAI integration is already connected to this sub-account first — see TimelinesAI and GoHighLevel Integration.

Build the workflow

  1. In your GHL sub-account, open Automation → Workflows.

  2. Create a new workflow, or open an existing one.

  3. Add the trigger you want to fire on — for example, Contact Tag Added, Opportunity Stage Changed, or Appointment Booked.

  4. Click Add Action and select Send WhatsApp via TimelinesAI.

  5. Configure the action:

    • Sender number — choose which connected WhatsApp number the message should send from.

    • Recipient — the workflow contact's phone number (mapped automatically from the trigger contact).

    • Message body — write your message. Use merge tags like {{contact.first_name}}, {{contact.phone}}, or any custom field to personalize it.

  6. Save the action, then publish/activate the workflow.

Use case ideas

  • Appointment reminders and confirmations

  • Order or shipping updates

  • Onboarding sequences for new customers

  • Lead-status follow-ups (e.g., a check-in message when a deal goes quiet)

Good practices

  • Run the workflow on a single test contact before turning it on for your full pipeline.

  • Keep phone numbers on contact records in E.164 format so the action can resolve a valid recipient.

  • If a contact has no phone number, the action will fail on that step — [CONFIRM: does the action surface an operator-readable error in the workflow log, per the "operator-readable errors" note in the submission spec, or fail silently? Worth confirming exact error copy for this article.]

Related Articles

Did this answer your question?