Resources · Make integration

Smoove Make integrationAutomate Smoove with Make.

Can Make keep your Smoove lists in sync without code? The Smoove Make integration gives you 12 modules: 8 triggers that watch leads, subscribers and campaigns, plus actions to add, update or unsubscribe contacts. This page is for marketers who run Smoove and want to wire it up themselves, starting with one working scenario.

Try the Smoove integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Smoove Make integration let you automate?

The Smoove Make integration links your Smoove account to Make so contacts, leads and unsubscribes move between Smoove and your other tools on their own. You build a scenario, the automation itself, out of modules, the bricks that each do one job, and Make runs it for you with no code to write.

Every new form entry lands in Smoove. Put the module of your form or CRM tool first, then add Add or Update Contact. Each person who signs up elsewhere becomes a Smoove contact, and someone already on file gets refreshed instead of duplicated.

Your sales team sees every new lead without an export. Start with Watch New Lead and send each lead to the tool your team already reads, such as a chat channel or a spreadsheet. The same pattern works with Watch New Subscriber when you want a welcome step outside Smoove.

Opt-outs stay consistent everywhere. Watch Unsubscribe Contact picks up people who left your list so another system can mark them too, and the Unsubscribe action does the reverse when the opt-out happens outside Smoove.

Keep the limits in mind. The Smoove documentation lists the modules by name without describing them, gives no numeric limit, and Make offers no Make an API Call module for Smoove, so what you can do is exactly these 12 modules. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make training walks you through your first builds.

Connect

How do you connect Smoove to Make?

  1. 01

    Create an API key in Smoove

    In Smoove, hover over your account name in the top bar and click API Keys & pixels. Click Add API Key, pick the permission type, give the source a context name, then click Save.

  2. 02

    Copy the key from the screen

    Smoove shows the new API key right after you save. Copy it and keep it at hand, since Make asks for it in the next step. You need an active Smoove account for this, as the Make documentation points out.

  3. 03

    Paste it into Make

    In your scenario, add any Smoove module and click Create a connection. Give it a name in Connection name if you like, paste the key, and confirm. Every other Smoove module then reuses that connection, your linked account.

First scenario

Build your first scenario with Smoove

GoalWhen someone signs up in another app, Make adds that person to Smoove or updates the existing contact.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. That first module decides when everything starts.

  2. 02

    Pick the source of new sign-ups

    Search for the app where people sign up, a form tool or a CRM, and choose its watch module. Connect that account the same way you will connect Smoove.

  3. 03

    Add the Smoove action

    Click the + to the right of the first module, search for Smoove and pick Add or Update Contact. Choose your Smoove connection, or create it with your API key.

  4. 04

    Map the contact data

    Fill the Smoove fields by clicking the values that came from the first module. Each bundle, one sign-up here, turns into one contact in Smoove.

  5. 05

    Test with Run once

    Click Run once and create a test sign-up in your source app. Read the bundles each module received, then check the contact in Smoove.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, and turn the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a Smoove scenario?

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

Smoove1Watch Automation Trigger

Watch Automation Trigger

triggerIn the docs only

This one hands your Smoove automations over to Make. The documentation gives only its name, so read it as a hook on the automation flows you set up in Smoove, and confirm what it returns with a first test.

How it fires
scheduled, meaning Make checks Smoove on the scenario's schedule and picks up what changed since the last check.
When to use it
a Smoove automation already reaches the right people and you want another tool to follow up on the same people.
Watch out
click Run once and inspect the bundles before mapping anything, since no official description tells you which data comes out.
Smoove2Watch Campaign Watched

Watch Campaign Watched

triggerIn the docs only

Campaign activity becomes something the rest of your stack can react to. Judging by its name, it reports campaigns being viewed or opened, though Smoove's documentation adds nothing beyond that title.

How it fires
scheduled; Make asks Smoove for news each time the scenario's clock comes around.
When to use it
you want engagement with a campaign logged in a CRM or a sheet so the sales side sees who paid attention.
Watch out
the exact meaning of "watched" is not documented, so run one test after a campaign goes out and check the bundles before you rely on it.
Smoove3Watch Contact Updated

Watch Contact Updated

triggerIn the docs only

Changes made to a Smoove contact can travel to your other systems instead of staying stuck in Smoove. The module name points to edited contacts; the doc has no further description.

How it fires
scheduled. Make polls Smoove at the interval set on the scenario, so an edit shows up at the next check, not the second it happens.
When to use it
your CRM should mirror the details people correct in Smoove, like a new company name after a job change.
Watch out
if the same scenario also writes back to Smoove with Add or Update Contact, each write may count as an update and restart the loop.
Smoove4Watch Contact from Automation

Watch Contact from Automation

triggerIn the docs only

You get the contacts that pass through one of your Smoove automations, ready for Make to handle. Unlike Watch Automation Trigger, the name suggests each bundle here is a person rather than the automation event itself.

How it fires
scheduled: Make fetches new contacts from Smoove on the scenario's schedule.
When to use it
a nurture sequence in Smoove should hand warm contacts to a sales tool once they reach a given step.
Watch out
Smoove documents no details for this module, so pick your automation, press Run once and check what each bundle holds.
Smoove5Watch New Lead

Watch New Lead

triggerIn the docs only

Fresh leads collected in Smoove reach your sales process without anyone exporting a file. That is what the name promises; the documentation has no description to add.

How it fires
scheduled, with Make looking for new leads each time the scenario runs on its clock.
When to use it
Smoove collects requests from prospects and your reps work from a CRM or a shared channel.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a lead can wait that long before Make passes it on; paid plans go down to 1 minute.
Smoove6Watch New Subscriber

Watch New Subscriber

triggerIn the docs only

Each person who joins a Smoove list can kick off whatever should happen next outside Smoove. The module name is all the documentation provides, and it clearly aims at new list members.

How it fires
scheduled; Make checks Smoove for new subscribers following the scenario's schedule.
When to use it
a subscriber should also appear in your CRM, or your team wants a note in a chat tool when someone signs up.
Watch out
each new subscriber is one bundle, and every module after the trigger spends an operation on it, so a busy list uses your plan faster.
Smoove7Watch Smoove Trigger

Watch Smoove Trigger

triggerIn the docs only

Smoove has its own triggers, and this module lets one of them start a Make scenario. The doc mentions Smoove triggers among the things you can monitor but does not describe the module itself.

How it fires
scheduled, which means Make checks Smoove on the scenario's schedule rather than being called by Smoove.
When to use it
you already defined an event inside Smoove and want Make to carry it to another app without rebuilding that logic.
Watch out
the output depends on the trigger you pick in Smoove, so test with Run once before you map the fields downstream.
Smoove8Watch Unsubscribe Contact

Watch Unsubscribe Contact

triggerIn the docs only

Opt-outs recorded in Smoove get passed to the other places that store the same person. The name refers to contacts who unsubscribed; no official description exists.

How it fires
scheduled: Make reads the new unsubscribes from Smoove at each scheduled check.
When to use it
your CRM or another sending tool must stop contacting someone who left your Smoove list.
Watch out
between two checks the other tool still sees the person as subscribed, so keep the schedule short if the delay matters to you.
Modules

What can Make do in Smoove?

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

Smoove1

Add or Update Contact

ActionIn the docs only

Your Smoove audience stays clean because one module both creates new people and refreshes existing ones. It is the natural endpoint for sign-ups arriving from forms, shops or a CRM.

When to use it
data about a person comes from outside Smoove and you do not want to check first whether they already exist.
Watch out
placed after Watch Contact Updated in one scenario, it can trigger itself again.
Smoove2

Create a List

ActionIn the docs only

A new Smoove list appears without anyone opening Smoove, ready to receive contacts. Handy when each event, product or client deserves its own audience.

When to use it
a new webinar is registered in another tool and its attendees need a dedicated list.
Watch out
every run makes another list, so start it from a real event, never from a trigger that fires for each contact.
Smoove3

Find Subscriber

SearchIn the docs only

Before acting on someone, you learn whether they are already in Smoove. As a search module, it can return no result, one, or several bundles.

When to use it
the next step differs for known and unknown people, for instance a different follow-up for existing subscribers.
Watch out
when the search comes back empty, the following modules simply do not run for that person, so plan what should happen then.
Smoove4

Unsubscribe

ActionIn the docs only

Someone who opted out elsewhere stops receiving your Smoove emails too, with no manual cleanup. It acts on one contact per bundle.

When to use it
a customer asks to leave through your support desk or CRM, and Smoove must reflect it.
Watch out
this changes a real subscription, so test it on your own address with Run once before pointing it at your list.
Need help

Need help automating Smoove with Make?

A person reads every message.

FAQ

Smoove and Make: common questions

01Is the Smoove Make integration free?
Yes, on the Make side. Smoove is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in credits, one per operation. You still need your own active Smoove account, which Smoove bills separately.
02What do you need to connect Smoove to Make?
An active Smoove account and an API key. In Smoove, hover over your account name, open API Keys & pixels, click Add API Key, choose the permission type, name the context and save. Copy the key shown on screen. In Make, add a Smoove module, click Create a connection, paste the key and confirm. The IP restriction field in Smoove is optional, so leave it empty unless you have a reason to fill it.
03Do Smoove triggers in Make work in real time?
No. Going by their names, all 8 Smoove triggers are scheduled watch modules: Make checks Smoove on the scenario's schedule instead of being called the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. If speed matters, a paid plan with a short schedule gets you closest, but none of the Smoove triggers is listed as instant in Make.
04What if a Smoove module is missing in Make?
Then you work around it, because Make has no Make an API Call module for Smoove. Anything outside the 12 listed modules stays out of reach from this app. Check whether another app in your scenario can cover the step, or combine existing modules, such as Find Subscriber followed by Add or Update Contact. For anything beyond that, the team can look at your case and suggest a workable setup.
05Should you use Make or n8n for Smoove?
It depends on your criteria. In Make, Smoove comes with 12 modules usable from the Free plan: 8 scheduled triggers, 3 actions and 1 search, all set up without code. Before choosing, list the Smoove events and actions your scenarios truly need, then check whether each platform covers them. If you already build on one of the two tools, staying there usually keeps your connections and habits in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations