Resources · Make integration

BackgroundErase Make integrationAutomate BackgroundErase with Make.

Tired of cutting out product photos by hand? The BackgroundErase Make integration gives you 3 action modules that remove the background from a file or an image URL. This guide shows you how to link your API key and build a first scenario, step by step.

Try the BackgroundErase integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BackgroundErase Make integration do for you?

The BackgroundErase Make integration lets a Make scenario (the automation you build, a chain of modules) send pictures to BackgroundErase and get them back without their background. You pick an image, from a file or from a link, and the cleaned version flows on to the next step of the chain.

Clean catalog shots from a shared link. A supplier posts product pictures online, and your store needs them on a plain background. The Remove background from an image URL module takes the link straight from the previous step, so nobody downloads anything first.

Cutouts for files your team already handles. When a designer drops a photo into another app of the scenario, Remove background from a file receives that file as a bundle (one item passed from a module to the next) and returns the cutout, ready for the following module.

Anything the two ready-made modules skip. Make an API call reaches any endpoint of the BackgroundErase API with the same connection, so you are not stuck when a need falls outside the listed modules.

What Make does not give you here: BackgroundErase has no trigger, so the app never starts a scenario by itself. Another app or the Make schedule has to kick things off. The documentation also warns that it was produced with AI from the vendor's own material, so check important details with BackgroundErase. Budget questions are covered in Make pricing, and n8n vs Make helps if you still hesitate between the two tools. For a guided start, see Make training.

Connect

How do you connect BackgroundErase to Make?

  1. 01

    Generate your API key

    Log in to BackgroundErase, open the account dashboard, then the API Access section. If no key exists yet, click the button that generates one, then copy the key shown on screen. You need an active BackgroundErase account for this.

  2. 02

    Add a BackgroundErase module

    In your Make scenario, add any BackgroundErase module and click Create a connection. A connection is your BackgroundErase account linked to Make once, then reused by all three modules of the app.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (the field is optional), paste the API key you copied, and confirm. Make can now call BackgroundErase on your behalf.

First scenario

Your first scenario with BackgroundErase

GoalWhen an image file shows up in another app, Make sends it to BackgroundErase and hands the cutout to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Since BackgroundErase has no trigger, this first module belongs to the app where your images arrive.

  2. 02

    Add the background removal

    Click the + on the right of that first module, search for BackgroundErase and choose Remove background from a file. Pick your connection, or create it with the three steps above.

  3. 03

    Map the incoming file

    Fill the module fields by mapping the file delivered by the first module. Each image travels as one bundle, and each module run on a bundle counts as one operation on your Make plan.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received to confirm the cutout came back from BackgroundErase.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default, the minimum on the Free plan) and switch the scenario on. Add the module that stores the result whenever you are ready.

Modules

What each BackgroundErase module does

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

BackgroundErase1

Make an API call

ActionIn the docs only

This module lets your scenario reach any endpoint of the BackgroundErase API while reusing the connection you already set up. You get access to what the two ready-made modules leave aside, without handling authentication yourself.

When to use it
a need your team spotted in the BackgroundErase documentation has no dedicated module in Make.
Watch out
you write the request yourself, so read the vendor documentation for the exact endpoint first.
BackgroundErase2

Remove background from a file

ActionIn the docs only

Hand this module an image file coming from an earlier step and it returns the same picture with its background removed. The result flows on as a bundle, so the next module can store or send it right away.

When to use it
the photo already sits in your scenario as a file, for example an attachment picked up by another app.
Watch out
on the Free plan, Make handles files up to 5 MB.
BackgroundErase3

Remove background from an image URL

ActionIn the docs only

Give BackgroundErase a public link to a picture and you get a cutout back, with no download step in between. That keeps your scenario short when your images live on the web rather than in a folder.

When to use it
a form, a spreadsheet row or a product feed already stores the image address.
Watch out
BackgroundErase fetches the picture itself, so a link that needs a login will most likely fail; check it with Run once.
Need help

Need help automating BackgroundErase with Make?

A person reads every message.

FAQ

BackgroundErase and Make: common questions

01Is the BackgroundErase Make integration free?
Yes on the Make side: BackgroundErase is a standard app, 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 Make plans lower the interval to 1 minute and count usage in operations per month. BackgroundErase itself needs an active account with an API key, and its subscription follows the vendor's own pricing page, which this guide does not cover.
02What do you need to connect BackgroundErase to Make?
An active BackgroundErase account and an API key. Open the account dashboard, go to API Access, generate a key if none exists yet and copy it. In Make, add any BackgroundErase module, click Create a connection, optionally name it, then paste the key. The same connection then serves all 3 modules of the app, including Make an API call, so you only do this once per BackgroundErase account. Nothing else is required on the Make side.
03Does BackgroundErase start a Make scenario in real time?
No, because BackgroundErase has no trigger module at all. The scenario has to start elsewhere: either with a trigger from another app, such as the one where your images arrive, or with the Make schedule on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. If the other app offers an instant trigger, it calls Make through a webhook as soon as something happens, and BackgroundErase simply runs next in the chain.
04What if a BackgroundErase module is missing in Make?
Use Make an API call. It reaches any endpoint of the BackgroundErase API with the connection you already created, so a feature without its own module is still within reach. You write the request yourself, which means reading the vendor documentation first. The Make documentation for this app also states that it was generated with AI from BackgroundErase material and may contain mistakes, so confirm important details directly with BackgroundErase before relying on them.
05Should you use Make or n8n with BackgroundErase?
It depends on the tool your team already runs. In Make, BackgroundErase comes with 3 action modules: one for a file, one for an image URL and Make an API call for everything else, all usable from the Free plan. Many apps also exist as an n8n node, but this guide does not document whether BackgroundErase does, so check that before choosing. Compare the modules each side offers for your exact case rather than picking a tool on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations