Resources · Make integration

Campaign Cleaner Make integrationAutomate Campaign Cleaner with Make.

Can Make send and check your Campaign Cleaner campaigns for you? The Campaign Cleaner Make integration gives you 7 action modules and no trigger. This page is for marketers new to Make: it shows how to link your account, then walks you through a first scenario.

Try the Campaign Cleaner integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Campaign Cleaner Make integration do for you?

The Campaign Cleaner Make integration lets a Make scenario (the automation you build, a chain of steps) work on your Campaign Cleaner campaigns without code. Each step is a module, one brick of the scenario, and all 7 modules here are actions: they run when something earlier in the scenario tells them to.

A send that follows your approval. A campaign gets the green light in another tool your team already uses. Make picks up that event, runs Get Campaign Status to show where the campaign stands, then Send a Campaign releases it. Nobody has to open Campaign Cleaner to press the button.

A clean campaign list. Get a List of Campaigns hands Make every campaign on your account, most likely one bundle (one item passed between modules) per campaign, as the name suggests. From there you can copy names into a sheet or pass one ID to Delete a Campaign when a draft is no longer needed.

A credit check before the big send. Retrieve Available Credits reads the credit balance the module name refers to, so a scenario can alert your team before a send rather than after.

Know the limit before you start: the Make documentation for Campaign Cleaner is marked as limited, with no official description for each module. Run every module once and read what it returns before you rely on it. When a listed module stops short, Make an API Call reaches the rest of the app's API with the same connection. The same app may also exist as an n8n node; the n8n vs Make comparison helps you weigh the two, and the Make training covers the editor basics.

Connect

How do you connect Campaign Cleaner to Make?

  1. 01

    Add a Campaign Cleaner module

    In your scenario, click the + and search for Campaign Cleaner. Pick any of its modules, then click Create a connection. A connection is your Campaign Cleaner account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    Make offers a default name. Changing it is optional, but a clear label such as the account owner or the client name saves guesswork later, when several people or several accounts share the same Make organization.

  3. 03

    Authorize and save

    Depending on what Campaign Cleaner asks for, either approve Make on the app's own page or paste the key the app gives you. Then click Save. The module can now read your campaigns.

First scenario

Your first scenario with Campaign Cleaner

GoalWhen a campaign is approved in another app, Make checks its status in Campaign Cleaner and sends it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Campaign Cleaner has no trigger, pick the app where the approval happens and its module that starts the flow.

  2. 02

    Add Get Campaign Status

    Click the + on the right of that first module, search Campaign Cleaner and choose Get Campaign Status. Click Create a connection if you have not linked the account yet, then map the campaign from the first module.

  3. 03

    Add Send a Campaign

    Click the + again and add Send a Campaign. Map the same campaign from the earlier modules, so the send targets exactly the campaign whose status you just read.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Expect this run to send for real, so test on a campaign you mean to release.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or leave it on the other app's own timing if its trigger is instant. Then switch the scenario on.

Modules

What each Campaign Cleaner module does

Campaign Cleaner gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Campaign Cleaner1

Delete a Campaign

ActionIn the docs only

Removes a campaign you no longer need from Campaign Cleaner, so old tests and abandoned drafts stop cluttering your account and your campaign lists.

When to use it
at the end of a cleanup scenario, after Get a List of Campaigns has helped you pick out the drafts to drop.
Watch out
the documentation says nothing about undoing a delete, so treat it as final and test it with Run once on a throwaway campaign first.
Campaign Cleaner2

Get Campaign Status

ActionIn the docs only

Tells your scenario where a given campaign stands right now, so the next module can act on that answer instead of on a guess made by a teammate.

When to use it
just before Send a Campaign, or in a scenario that reports progress to your team channel.
Watch out
the documentation does not list the possible statuses; read them in a Run once test before building a filter on them.
Campaign Cleaner3

Get a Campaign

ActionIn the docs only

Fetches one campaign you already know, so later modules can reuse its details, for instance to copy them into a sheet or into a message for a reviewer.

When to use it
when an earlier module hands you a campaign ID and you need more than its status.
Watch out
it works on one campaign only; to go through all of them, start with Get a List of Campaigns.
Campaign Cleaner4

Get a List of Campaigns

ActionIn the docs only

Judging by its name, gives you the campaigns of your Campaign Cleaner account in one go, each likely passed to the next module as its own bundle, ready to be logged, filtered or cleaned up.

When to use it
to build an inventory in a spreadsheet, or to feed a cleanup that ends with Delete a Campaign.
Watch out
every following module runs once per campaign, and each run is an operation Make counts on your plan.
Campaign Cleaner5

Make an API Call

ActionIn the docs only

Opens the rest of the Campaign Cleaner API to your scenario, using the connection you already created, so you are not limited to the six ready-made modules.

When to use it
when the task you have in mind has no dedicated module on this page.
Watch out
you write the request yourself, so keep the Campaign Cleaner API reference open and test the call with Run once.
Campaign Cleaner6

Retrieve Available Credits

ActionIn the docs only

Reads the credits left on your Campaign Cleaner account, so the scenario can warn someone before the balance becomes a problem during a send.

When to use it
at the start of a sending scenario, followed by a filter and an alert to the person who manages the account.
Watch out
the documentation does not say what one credit covers, so check this in your Campaign Cleaner account.
Campaign Cleaner7

Send a Campaign

ActionIn the docs only

Sends a Campaign Cleaner campaign straight from your scenario, so the approval in another tool and the actual send become one step instead of two.

When to use it
after an approval event elsewhere, ideally with Get Campaign Status just before it.
Watch out
expect a Run once test to send for real, since nothing documents a test mode; use a campaign you are ready to release.
Need help

Need help automating Campaign Cleaner with Make?

A person reads every message.

FAQ

Campaign Cleaner and Make: common questions

01Is the Campaign Cleaner Make integration free?
Yes, Campaign Cleaner is a standard app in Make, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits per month. Your Campaign Cleaner subscription is separate and not covered here.
02What do you need to connect Campaign Cleaner to Make?
A Campaign Cleaner account and a Make account. The Make documentation lists no prerequisite and no official connection steps for this app, so the generic path applies: add a Campaign Cleaner module, click Create a connection, name it if you like, authorize Make on the app's page or paste the key Campaign Cleaner provides, then click Save. Every Campaign Cleaner module then reuses that same connection. Name each connection clearly if several accounts share one Make organization.
03Does the Campaign Cleaner Make integration react in real time?
No, not on its own: Campaign Cleaner has no trigger in Make, only 7 actions. A scenario therefore starts elsewhere. Either another app's trigger opens the flow, instantly through a webhook if that app offers an instant trigger, or you set a schedule on the first module, every 15 minutes by default on a new scenario. The Campaign Cleaner actions then run each time the scenario does. Before switching the scenario on, test it once with Run once to see the bundles each action receives.
04What if a Campaign Cleaner module is missing in Make?
It depends on what you need. Campaign Cleaner has Make an API Call, which reaches any endpoint of the app's API with the connection you already set up, so a missing action can usually be covered that way. Keep in mind that Make marks its documentation for this app as limited, with no official description per module, so test each module with Run once and read its output before building on it.
05Should you use Make or n8n for Campaign Cleaner?
It depends on the tool your team already uses. On Make, Campaign Cleaner comes with 7 action modules, including Make an API Call for anything they do not cover, and no trigger. The same app often has an n8n node too. Compare the modules each side offers for the job you have in mind, then pick the editor your team is comfortable maintaining. The comparison page linked above goes through both.
Same platform

Other docs you might need on this stack.

Browse all integrations