Whatsable
Form to WhatsApp in under a minute
A Typeform or Google Forms submission hits Make. Whatsable sends a personalized template immediately and logs the send in your team inbox.
Outcome: Every form lead gets a WhatsApp touch without copy-paste.
All integrations
Make integration
Make integrationWhatsApp automation scenarios in Make
Connect forms, CRMs, and spreadsheets to Whatsable in Make. Branch on incoming and outgoing messages — including replies typed in the WhatsApp Business app. You do not delete the app.
Capabilities
What you can do with Whatsable
- Trigger WhatsApp sends from any Make module
- Branch scenarios on delivery status or inbound replies
- Schedule messages for later delivery
- Schedule a follow-up that sends only if the contact does not reply within your chosen window.
- Incoming and outgoing Messages from console trigger, including WhatsApp Business app replies
- Meta WhatsApp Coexistence: keep the WhatsApp Business app on your phone. You do not delete it. The same number works in the app, the Notifyer inbox, and automations.
- Payload fields: incoming_message (false when your business sent it), send_by (WhatsApp App, teammate name, or automation), was_message_by_human (true if a person sent it).
Use cases
Real workflows teams run today
Appointment booking confirmation
When a booking lands in Google Calendar, Make sends a confirmation template with date variables, then waits 24 hours and sends a reminder only if there is no reply.
Outcome: Fewer no-shows for clinics, salons, and field services.
Pipeline stall nudges
Pipedrive deal stage unchanged for 3 days triggers Make. Whatsable sends a short check-in template and schedules a second message if still no reply.
Outcome: Deals move without reps living in spreadsheets.
Log replies typed in the WhatsApp Business app
Use Incoming & Outgoing Messages from console. When the owner types on their phone, Make receives incoming_message false, send_by WhatsApp App, and was_message_by_human true. A Router logs the event to a CRM without requiring the team to leave the phone app.
Outcome: Phone-app coexistence: keep WhatsApp Business, still capture every outgoing message in Make.
Examples
Triggers, parameters, and patterns
Concrete fields you can map in automation tools or cite in your own docs.
Outgoing message typed in the WhatsApp Business app
A teammate replies by hand on their phone. Your webhook, n8n, Make, or Zapier trigger still fires. You do not delete the WhatsApp Business app.
TriggerIncoming and outgoing WhatsApp message (outgoing enabled)
| Parameter | Type | Description | Example |
|---|---|---|---|
incoming_message | boolean | false when your business sent the message; true when the contact sent it | false |
send_by | string | WhatsApp App for the phone app; the teammate's name for the Notifyer inbox; the automation name for Make, Zapier, n8n, or API | WhatsApp App |
was_message_by_human | boolean | true when a person sent it (phone app or inbox); false for bots and automations | true |
last_message_of_bot | string | Last message your business sent, whether a human or a bot typed it | Hello n8n |
Appointment confirmation scenario
Module 1: Calendar watch. Module 2: Whatsable send template. Module 3: Sleep 24h. Module 4: Router checks inbox for reply. Module 5: Whatsable reminder template on the no-reply path.
TriggerGoogle Calendar: Watch Events
| Parameter | Type | Description | Example |
|---|---|---|---|
phone | string | E.164 phone from calendar attendee or form field | +14155550198 |
template_name | string | Whatsable template to send | booking_confirmed |
sleep_hours | number | Make Sleep module duration before reminder | 24 |
Setup
Get connected in minutes
- 1Install the Whatsable app in Make from the integrations directory.
- 2Connect your Whatsable API key in Make credentials. Keep the WhatsApp Business app — coexistence is supported.
- 3Add Incoming & Outgoing Messages from console if you need phone-app and inbox replies. Map incoming_message, send_by, and was_message_by_human.
- 4Add Whatsable Send Message and map phone, template, and variables from the trigger output.
- 5Add Sleep and Router modules for follow-up logic, then activate the scenario.
FAQ
Common questions
No. Notifyer System supports Meta WhatsApp Coexistence. Keep chatting from the WhatsApp Business app on your phone. Hand-typed replies reach your webhook or Make, Zapier, and n8n trigger with incoming_message: false, send_by: "WhatsApp App", and was_message_by_human: true.
Yes. Enable outgoing events. The JSON payload includes incoming_message (direction), send_by (which system or teammate sent it), and was_message_by_human (person vs bot). Messages typed in the WhatsApp Business app arrive with send_by: "WhatsApp App". Messages sent from the Notifyer chat inbox arrive with the teammate's name in send_by.
Yes. Use a Router after a delay that checks Whatsable inbox or webhook data for inbound messages before sending the next template.
Inbound voice messages can be transcribed in Whatsable and passed to Make as text for AI or CRM modules.
Run Make and WhatsApp together
Unlimited messaging from your own number, team inbox, AI assistant, and automations included.
Pro includes a 7-day free trial · 6-minute setup · Cancel anytime