All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Send a WhatsApp or other message from an automation

The Send a WhatsApp message step sends your text from a number you choose, or replies in the same chat. It can attach the PDF an earlier step generated, and it supports reply buttons and lists.

7 min
Before you start · 1 thing · for owners and managers
A connected channel

Steps

1
Under Send from, choose the WhatsApp number.
The chat it came in on replies in the chat that started the run, for message triggers only.
2
Under Send to, choose who gets it.
The person who messaged, for message triggers, or The record: then pick the phone, in the trigger record, a linked record or a record you found.
3
Write the Message. Press Insert a detail to add record data.
4
Optional: under Attachments, press Attach and choose a document from Generated documents.
It’s the PDF an earlier Generate a document step makes, sent as a file, with your text as its caption.
5
Optional: under Let them tap an answer, add Buttons or a List.

Who receives the message?

Source
When
The same chat
Send from is The chat it came in on, with a message trigger
A mobile field in the record
Automations built on records
A number in a linked record
Such as {{lead.whatsapp_number}}, up to two relations
A number in a record you found
Such as {{found.client.phone}}
The sender’s number
The person who messaged, with a message trigger

If the chosen number is empty, the send is refused, and it’s not sent to anyone else.

Reply buttons and lists

Up to 3 buttons, or a list of up to 10 options. Channels that support them, such as WhatsApp Cloud, show them as real buttons. Other channels receive them as numbered text: “1) Yes… reply with the number”.

A Wait for a reply step chooses the path by the button pressed or the number.

Linking the chat to the record

A new chat is linked to the trigger record on its own. A chat linked to another record keeps its link.

Sending a document the automation generated

The Attachments list offers the PDFs that Generate a document steps before this one make. The generate step must be on the same path, before the message.

If something goes wrong

What you see
Why
What to do
“The session isn’t connected”
The sending channel is disconnected.
“The record has nothing in … to send to.”
The mobile field or the linked number is empty.
Fill in the number in the record.
“The file doesn’t point to a document in this run”
The generate document step didn’t run on this path.
Put the generate step before the send, on the same path.
The first message to a new client didn’t arrive
WhatsApp limits on new numbers.
The run is “Failed — uncertain”
A cut-off while sending; it’s not known whether it arrived.
Check the chat, then resume from Follow the run log, and retry or resume from the failed step, confirming the resend if needed.

A real example

Basma Clinics
The situation

Patients don’t confirm their appointments.

What they did
  1. Send a WhatsApp message: “Your appointment is tomorrow at {{appointment_time}}”, with two buttons: “Confirm” and “Cancel”.
  2. Wait for a reply for 3 hours, with a path for each button.
The result

The patient confirms with one tap, and the record updates on its own.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Reply buttons: up to 3 buttons, with a title of up to 20 characters.
The list: up to 10 options, the title up to 24 characters, the description up to 72, and the list button up to 20.
The message: up to 1,000 characters.
Buttons don’t work with attachments.
The message is never sent twice, even if the step is retried.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.