Resources · Make integration

Wishpond Make integrationAutomate Wishpond with Make.

What if every new Wishpond lead landed in the right list without a single copy-paste? The Wishpond Make integration gives you 17 modules to watch, create and sort leads and lists. This guide connects your account and walks you through a first working scenario.

Try the Wishpond integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Wishpond Make integration do for you?

The Wishpond Make integration links your Wishpond account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Wishpond brings 4 triggers that spot new leads, lists or lead activity, plus 11 actions and 2 searches that create, update, sort, find or delete them.

Leads from anywhere, in Wishpond. A signup collected by another tool becomes a Wishpond lead with Create a Lead, then joins the right campaign audience through Add a Lead to a List. Nobody retypes contact details, and the list stays current.

Follow-up that reacts to behavior. Watch Events on a Lead picks up the activity of a lead you choose. Pair it with Update a Lead or Remove a Lead from a List to move that person forward once they have acted.

Tidy lists without clicking around. Search Lists finds the lists you already have, Create a List builds a new static list, and Watch Lists tells the rest of your stack when a colleague adds one.

If a Wishpond feature has no ready-made module, Make an API Call reaches the Wishpond API with the same connection. Wishpond often has an n8n node too; the n8n vs Make comparison helps you pick. To see how Make counts usage, read Make pricing, and for hands-on practice, the Make training covers the editor step by step.

Connect

How do you connect Wishpond to Make?

  1. 01

    Copy your Wishpond API key

    In Wishpond, click your account name in the top right corner, open API Keys and copy the key shown in the window. You need an active Wishpond account for this menu to be there.

  2. 02

    Add a Wishpond module in Make

    In your scenario, add any Wishpond module and click Create a connection. The Connection name field is optional, but a clear name helps when several accounts share one Make workspace.

  3. 03

    Paste the key and save

    Paste the API key into the credentials field, or follow the on-screen instructions, then confirm. This connection, your Wishpond account linked to Make, is reused by every other Wishpond module you add later.

First scenario

Build your first scenario with Wishpond

GoalWhen a signup arrives in another app, Make creates the lead in Wishpond and adds it to your campaign list.

  1. 01

    Start a new scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your signups arrive: it opens the flow.

  2. 02

    Add Create a Lead

    Click the + on the right of that first module, search for Wishpond and choose Create a Lead. Click Create a connection and paste your API key.

  3. 03

    Map the contact details

    Fill the lead fields by mapping data from the first module. Each bundle, one signup here, becomes one lead in Wishpond.

  4. 04

    Send the lead to a list

    Add Add a Lead to a List after it. Make shows the lists it can read from your account, so pick the target list and map the lead returned by the previous module.

  5. 05

    Test, schedule and switch on

    Click Run once and read the bundles each module received. When the lead shows up in the list, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Triggers

Which Wishpond triggers start a scenario?

4 modules start a scenario when something happens in Wishpond. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Wishpond as soon as it happens.

Wishpond1Watch Events on a Lead

Watch Events on a Lead

Scheduled trigger

In Make“Triggers when a chosen lead performs an event or activity.”

This trigger follows one lead you pick and starts your scenario each time that person performs an event or activity in Wishpond. You get a way to react to what a known contact actually does, instead of only to their arrival.

How it fires
scheduled, so Make checks Wishpond on the scenario's schedule and picks up the new events since the last check.
When to use it
a high-value prospect you want to follow closely, where each action should update their record or alert sales.
Watch out
it watches a single chosen lead, so it does not replace Watch Leads for your whole audience.
Wishpond2Watch Leads

Watch Leads

Scheduled trigger

In Make“Triggers when a new lead is created.”

Watch Leads hands every newly created Wishpond lead to your scenario, one bundle per lead. It is the simplest way to push fresh contacts from your landing pages and forms to the rest of your tools.

How it fires
scheduled; Make checks Wishpond on the scenario's schedule, every 15 minutes by default, and collects the leads created in between.
When to use it
any flow that should start from a new lead, whatever campaign brought them in.
Watch out
each lead it returns counts as an operation, one run of one module that Make bills against your plan.
Wishpond3Watch Leads in a List

Watch Leads in a List

Scheduled trigger

In Make“Triggers when a new lead is added to the chosen list.”

Here the scenario starts only when a lead is added to the list you choose. That gives you a narrower, cleaner starting point than Watch Leads, since the list already reflects a segment you built in Wishpond.

How it fires
scheduled, which means Make looks at that list on the scenario's schedule rather than being pinged by Wishpond.
When to use it
a webinar or demo request list whose members need a specific follow-up somewhere else.
Watch out
pick the list carefully in the module; a lead added to a different list will not start this scenario.
Wishpond4Watch Lists

Watch Lists

Scheduled trigger

In Make“Triggers when a new list is created.”

Watch Lists reacts to structure rather than people: it starts your scenario whenever a new list is created in Wishpond. Useful for teams that want each new segment mirrored or announced elsewhere without anyone having to remember.

How it fires
scheduled, with Make checking Wishpond on the scenario's schedule and returning the lists created since its previous look.
When to use it
a marketer creates a list for a new campaign and you want a matching audience or a heads-up for the team.
Watch out
it returns lists, not the leads inside them; add Watch Leads in a List for the people.
Modules

What can the Wishpond modules do in a scenario?

Wishpond gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Wishpond1

Add a Lead to a List

Action

In Make“Adds a specific lead to the list.”

Drops an existing lead into the list you choose, so segmenting happens as part of the flow instead of by hand later. Pair it with Create a Lead or Search Leads to get the lead first.

When to use it
after a purchase or a form reply, to move the contact into the audience of the next campaign.
Wishpond2

Create a Lead

Action

In Make“Creates a new lead.”

Turns data from any other app into a brand new Wishpond lead, which is how outside signups become part of your marketing base. Map the contact details from the module before it.

When to use it
event registrations, chat conversations or CRM contacts that should also exist in Wishpond.
Watch out
search first with Search Leads if the same person may already be there, to avoid duplicates.
Wishpond3

Create a List

Action

In Make“Creates a new static list.”

Builds a new static list in Wishpond straight from your scenario, ready to receive leads through Add a Lead to a List. You skip opening Wishpond just to prepare a segment.

When to use it
a new product, event or campaign starts in your planning tool and needs its own audience.
Watch out
the list is static, so leads join it only when a module or a person adds them.
Wishpond4

Delete a Lead

Action

In Make“Deletes a specific lead.”

Removes one lead from Wishpond for good, which keeps your base clean when a contact must disappear. Feed it the lead from Search Leads or Get a Lead.

When to use it
a deletion request received in your support tool that must be applied in Wishpond as well.
Watch out
a delete cannot be undone; test with Run once on a dummy lead before switching on.
Wishpond5

Delete a List

Action

In Make“Deletes a specific list.”

Wipes a whole list from Wishpond, useful for clearing temporary segments once a campaign is over. It acts on the list itself, not on each lead one by one.

When to use it
when a campaign is marked as closed in your project tool and its list has no further use.
Watch out
nothing brings the list back, so confirm the target with Get a List first.
Wishpond6

Get a Lead

Action

In Make“Gets a specific lead.”

Fetches the full record of one lead you already know, so later modules can use its details. Think of it as a lookup when the trigger only handed you a partial view.

When to use it
after Watch Events on a Lead, to enrich an alert to sales with the lead's current information.
Watch out
it needs a specific lead; when you only have a search term, use Search Leads.
Wishpond7

Get a List

Action

In Make“Gets a specific list.”

Returns the details of one specific list, handy when a report or a check needs to know what a list holds before acting. It reads, it changes nothing.

When to use it
right before Update a List or Delete a List, to confirm you are pointing at the right segment.
Watch out
to find a list by name rather than by its identity, start with Search Lists.
Wishpond8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Wishpond API to your scenario, reusing the connection you already made. When no listed module does what you need, this one lets you call the endpoint directly.

When to use it
a Wishpond feature your campaigns rely on that no other module in the list covers.
Watch out
you write the request yourself, so keep the Wishpond API documentation open beside the editor.
Wishpond9

Remove a Lead from a List

Action

In Make“Removes a specific lead from the list.”

Takes a lead out of one list while keeping the lead in Wishpond, so the person stops receiving what that list is for. It is the gentle counterpart of Delete a Lead.

When to use it
a prospect becomes a customer and should leave the nurture list for the onboarding one.
Watch out
chain Add a Lead to a List after it if the contact must land somewhere else.
Wishpond10

Update a Lead

Action

In Make“Updates a specific lead.”

Changes the details of an existing lead so Wishpond reflects what your other tools know about that person.

When to use it
a deal moves forward in your CRM and the lead record in Wishpond should follow.
Watch out
double-check which field receives which data during Run once.
Wishpond11

Update a List

Action

In Make“Updates a specific list.”

Edits an existing list from your scenario, so a segment keeps matching the campaign it serves without anyone opening Wishpond. Get the list first with Search Lists or Get a List.

When to use it
a campaign is renamed or repositioned in your planning tool and its list should reflect that.
Watch out
this changes the list, not its members; lead moves go through the lead modules.
Wishpond12

Search Leads

Search

In Make“Searches for leads or lists them all.”

Looks up leads matching your criteria, or lists them all, and passes each match along as its own bundle. It is the usual first step before updating, moving or deleting someone.

When to use it
checking whether a contact already exists before Create a Lead adds a duplicate.
Watch out
it can return zero, one or many leads, and every module after it runs once per result.
Wishpond13

Search Lists

Search

In Make“Searches for lists or list them all.”

Finds lists in your Wishpond account, or returns every one of them, so the scenario can pick a segment by what you know about it. Each list comes out as a separate bundle.

When to use it
choosing the right list dynamically before Add a Lead to a List, instead of hard-coding one.
Watch out
with no match the modules after it do not run; check that case with Run once.
Need help

Need help automating Wishpond with Make?

A person reads every message.

FAQ

Wishpond and Make: frequently asked questions

01Is the Wishpond Make integration free?
Yes, on the Make side. Wishpond is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and stops a run after 5 minutes. Paid plans go down to a 1 minute interval, remove the cap on active scenarios and count usage in credits each month. Your Wishpond subscription is separate: you need an active Wishpond account, and its price depends on Wishpond, not on Make.
02What do you need to connect Wishpond to Make?
An active Wishpond account and its API key. In Wishpond, click your account name in the top right corner, open API Keys and copy the key shown. In Make, add any Wishpond module, click Create a connection, optionally name it, then paste the key. That single connection is then reused by all 17 Wishpond modules, so you only do this once per Wishpond account. If Make refuses the key, copy it again from API Keys in full.
03Do the Wishpond triggers in Make fire instantly?
No. All 4 Wishpond triggers are scheduled: Make checks Wishpond on the scenario's schedule instead of being called by Wishpond when something happens. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. On a paid plan you can shorten that interval to 1 minute. Since Wishpond has no instant trigger in Make, that interval is the setting to adjust when you want new leads picked up sooner.
04What if a Wishpond module you need is missing in Make?
It depends on what is missing. The 17 modules cover leads and lists: watch, create, get, update, search, move and delete. For anything else the Wishpond API offers, the Make an API Call module sends a request to any endpoint using the same connection, so you do not set up a second authentication. You write that request yourself, with the Wishpond API documentation at hand, and Make runs it like any other module.
05Should you use Make or n8n for Wishpond?
It depends on the tool your team already works in. Make offers 17 ready-made Wishpond modules, 4 of them scheduled triggers, plus Make an API Call for the rest of the API. Wishpond often has an n8n node too, so both routes can work. Compare which modules each side offers for your use case, and pick the editor your team is most at ease with. Neither choice is wrong by default.
Same platform

Other docs you might need on this stack.

Browse all integrations