What the app does
Triggers (Whappy → Make)
Watch closed leads, Watch new appointments, Watch dead leads and Watch Send data steps start your scenario the moment the event happens in Whappy.
Actions (Make → Whappy)
Create a lead adds a lead to a Whappy campaign. Make an API call sends any authorized request to the Whappy API.
Every trigger outputs the lead (
lead_id, name, phone, campaign_name, created_at, appointment) and, already parsed so you can map them directly: Lead info, Collected info, Conversation (a list of messages with sender, message and date) and Appointment details.
Setup
1
Install the Whappy app on Make
In Whappy, open Integrations → Make. Under Install the Whappy app on Make, click Open in Make (or Copy invite link to open it elsewhere) and install the app in your Make organization. The app is not listed in Make’s directory: this invite link is the way to install it.
2
Copy your Make API key
On the same page, under When Make asks for a key, paste this one, click Copy API key. The Make key is separate from your Zapier key: revoking one never stops the other.
3
Create the connection
In a Make scenario, add any Whappy module and click Create a connection. Paste the API key and save. Make checks the key immediately; a wrong or revoked key shows
[401] Invalid API key.4
Build your scenario
- Triggers: add the trigger, click Create a webhook, fill in its fields (hours for Watch dead leads, trigger name for Watch Send data steps) and save. Whappy starts sending events as soon as the scenario is on.
- Watch closed leads also asks for a Campaign name. Fill it in and the scenario only gets that campaign’s closed conversations; leave it empty for every campaign. The name must match the campaign’s name in Whappy (capitals and surrounding spaces do not matter). If you rename the campaign, update the name in the trigger too.
- Create a lead: map at least Phone (international format, e.g.
+393331234567) and Name. Turn on Test lead while you try it.
For Send Data Step, add a Send data step to your campaign funnel, choose Zapier or Make and pick the trigger name you used in Make.
API reference
Everything the Make app does goes through the public Whappy API. You can call it directly too, for example with Make an API call. Base URL:https://api.whappy.ai/v1
Authentication: send your API key in the X-API-Key header on every request. Keys are created in Integrations → Make (or Zapier, Webhook) and belong to one Whappy account.
Subscribe to an event
POST /zap/triggers
Response
201:
Unsubscribe
DELETE /zap/triggers/{id} with the id returned above, or DELETE /zap/triggers with the body { "targetUrl": "...", "zap_type": "DEAD" }. Both answer 200: {"status": "success"}, or {"status": "already_removed"} when nothing matched.
List subscriptions
GET /zap/triggers returns the account’s active subscriptions. Make uses it to verify the connection.
Sample payload
GET /zap/sample/{name} returns a list with one sample event payload. Every name returns the same sample, and the sample has no campaign_name.
Event payload
Whappy POSTs this JSON to eachtargetUrl when the event happens:
The API sends the four
*_json fields as JSON strings. The Make app parses them for you: in Make they are Lead info, Collected info, Conversation and Appointment details, and an empty one is simply left out.
Create a lead
POST /lead
Response
200: { "status": "success", "message": "...", "data": { "_id": "...", "name": "Anna", "phone": "+393331234567", ... } }
message says what happened:
Lead created successfully: a new lead.Lead already exists; details merged: the same person was already in that campaign. Whappy keeps one lead and adds the new details.Lead already exists; details merged and campaign restart requested: as above, and the conversation starts over because the campaign has Restart the campaign for a lead that comes back on (campaign Options).
409 (test leads are not refused).
Errors
Errors answer with a status code and a readable message, shown in Make as[status] message:
Troubleshooting
The connection fails with [401]
The connection fails with [401]
Copy the key again from Integrations → Make, with no spaces before or after it. A key revoked in Whappy stops working at once.
A trigger never fires
A trigger never fires
Check the scenario is on: Make refuses events for a scenario that is off. Check the campaign is running and that leads reach the step (Close, appointment, Send data) the trigger listens to. For Watch Send data steps, the trigger name in Make must match the one picked in the Send data step.
Create a lead fails with [400]
Create a lead fails with [400]
The phone number cannot be read. Send it with the international prefix, or set a default country in Whappy’s settings.
Create a lead fails with [409]
Create a lead fails with [409]
The campaign does not talk on WhatsApp, so it cannot take a lead by phone number. Turn on WhatsApp under the campaign’s Options → Channels (see Channel), or send the lead to another campaign.

