- Home
- Resources
- Integrations
- WhatConverts
WhatConverts Make integrationAutomate WhatConverts with Make.
What happens to a lead once WhatConverts has recorded it? The WhatConverts Make integration answers with 7 modules: 2 instant triggers, 4 actions and 1 search. This guide is for marketers and ops people who already track calls, forms and chats, and it walks you from the connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the WhatConverts Make integration let you automate?
The WhatConverts Make integration links your WhatConverts account to Make, a no-code tool where you build a scenario: a chain of modules, each one a small brick that watches, reads or writes something. Here the bricks react to leads being created or changed, and they can create, fetch, update or search leads for you.
Leads that reach the rest of your stack on their own. Start a scenario with Watch Lead Created and every new lead flows into whatever app comes next, a CRM, a spreadsheet or a team chat. Since the trigger is instant, WhatConverts pings Make the moment the lead exists.
A lead record that follows the deal. When your sales tool learns that a prospect is qualified, Update a Lead writes that back into WhatConverts, so your reports show which sources bring leads that sales actually wants.
Leads from outside WhatConverts, recorded in WhatConverts. Create a Lead adds a lead that another app captured, and Search Leads lets a scenario check what already exists before it writes anything.
What the listed modules do not cover, Make an API Call can reach through the same connection. The official documentation for this app is marked as AI-generated from the vendor's docs, so double-check any detail that matters with WhatConverts. If you weigh other tools, the n8n vs Make comparison lays out the criteria, and the Make review covers the editor itself. Teams that want help can talk to our Make agency.
How do you connect WhatConverts to Make?
- 01
Generate your API key in WhatConverts
In your WhatConverts dashboard, pick the right profile, open the Tracking menu, then Integrations and API Keys. Click Generate API Key and copy both the API token and the API secret shown on the page.
- 02
Add a WhatConverts module in Make
In your scenario, add any WhatConverts module and click Create a connection. A connection is your WhatConverts account linked to Make once, then reused by every WhatConverts module. The Connection name field is optional.
- 03
Paste the token and the secret
Enter the API token and the API secret you copied, then save. Make signs in with them as Basic Auth credentials. You need an active WhatConverts account for this to work.
Your first scenario: record outside leads in WhatConverts
GoalWhen a lead arrives in another app, Make creates it in WhatConverts so it sits next to your tracked calls, forms and chats.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. This first module belongs to the app where the lead shows up, a form tool for instance.
- 02
Pick the source trigger
Search that app by name, choose its trigger for new entries and connect your account. Each entry it picks up becomes a bundle: one item that travels from one module to the next.
- 03
Add Create a Lead
Click the + on the right of that module, search WhatConverts and choose Create a Lead. Use the connection from the section above, then map the details of the incoming entry into the WhatConverts fields.
- 04
Test with Run once
Submit a test entry in the source app, then click Run once. Make runs the scenario a single time and shows the bundle each module received, so you can open WhatConverts and see the lead.
- 05
Schedule and switch it on
If the first module is scheduled, set its clock (every 15 minutes by default, never less than 15 on the Free plan). Then switch the scenario on. Each module run counts as one operation on your plan.
What can start a WhatConverts scenario?
2 modules start a scenario when something happens in WhatConverts. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by WhatConverts as soon as it happens.
Watch Lead Created
Instant triggerIn Make“Triggers when a lead is created.”
You get every fresh lead handed to Make the moment WhatConverts records it, whether it came from a call, a form or a chat. The scenario then decides where that lead goes next, without anyone copying details by hand.
Watch Lead Updated
Instant triggerIn Make“Triggers when a lead is updated.”
This one reacts to change rather than arrival: each time a lead is edited in WhatConverts, Make receives the updated lead and can push the new state elsewhere, so your other tools never lag behind the record.
What can Make do inside WhatConverts?
WhatConverts gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Lead
ActionIn Make“Creates a new lead.”
Adds a brand new lead to WhatConverts, so prospects captured by a tool WhatConverts does not track still land in the same place as your calls and forms.
Get a Lead
ActionIn Make“Retrieves an existing lead.”
Brings back one lead you already know, as WhatConverts stores it, so later modules can use details the previous step did not carry.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Opens the rest of the WhatConverts API to your scenario: any endpoint the listed modules skip can be called here, and it reuses the connection you already set up, so there is no second login.
Update a Lead
ActionIn Make“Updates an existing lead.”
Changes an existing lead in WhatConverts, which is how the outcome of a sales conversation travels back to the tool that tracks where the lead came from.
Search Leads
SearchIn Make“Retrieves a list of existing leads.”
Returns a list of leads, each one as its own bundle, which lets a scenario look before it acts: check for a match, then create, update or skip.
Need help automating WhatConverts with Make?
A person reads every message.