Resources · Zapier integration

BackgroundErase Zapier integrationAutomate BackgroundErase with Zapier.

The BackgroundErase Zapier integration cuts the background out of images that other apps hand over, with nobody opening an editor. 0 triggers, 3 actions, 0 searches. Feed it a file or a link, and you get back a clean cut-out ready for the next step.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the BackgroundErase Zapier integration is for

BackgroundErase removes the background from an image and returns a transparent version. On Zapier it is a pure worker: three actions, nothing that starts an automation. Some other app supplies the picture, BackgroundErase processes it, and a later step stores or publishes the result.

Three results you can build today. A product shot dropped into a shared folder comes back as a PNG with no background, ready for the shop catalog, through Remove Background From File. A photo link pasted into a spreadsheet or sent by a form gets the same treatment through Remove Background From Image URL, which fetches the picture itself. And a portrait shot on a green screen loses the green halo around its edges, thanks to the spill-cleaning option both actions share.

For anything the two ready-made actions skip, Make an API Call sends a request of your own to BackgroundErase. It is the escape hatch, and it assumes someone on the team can read the BackgroundErase developer documentation.

What Zapier does not do here: nothing starts from BackgroundErase. There is no trigger, so a finished image never kicks off a Zap on its own; the next step has to sit in the same Zap. There is no search either. And the cut-out comes back to the Zap as a file, so plan the step that stores or publishes it.

Comparing platforms? The BackgroundErase Make integration covers the same app on Make, and our Make vs Zapier page puts the two tools side by side.

Vocabulary

The Zapier vocabulary, one line per word

Seven terms used across this page. Read them once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. BackgroundErase has none, so a storage app, a form or a sheet plays that role.
Action
What the Zap does once started: the step that writes, sends or moves something. All three BackgroundErase operations are actions.
Task
The unit Zapier bills: one action your Zap completes successfully. Each processed image is one task.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by its app the moment the event happens.
Filter
A step that lets the Zap go on only when the incoming data meets your condition, such as a file being an image.
Connection
Your BackgroundErase account linked to Zapier once, then reused by every step that calls it.
Cost

What a BackgroundErase Zap costs in tasks

BackgroundErase is not a premium app, so it runs on the free plan. Each image processed successfully counts as one task. The trigger in the other app is free, and a failed attempt is not billed.

  • Billed1 task per image processed
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo

The free plan gives 100 tasks a month and checks polling triggers every 15 minutes. The trap: it only builds two-step Zaps. Folder trigger plus a background removal fits. But a cut-out you cannot store is rarely useful, and adding the upload step makes the Zap multi-step, which requires a paid plan. On paid plans that second action counts too, so each image then costs two tasks. Whatever BackgroundErase charges on its own side is separate from Zapier.

Connect

Connect BackgroundErase to Zapier

  1. 01

    Find the app

    Open the Apps page of your Zapier account and click + Add connection. In the dialog, type BackgroundErase and select it from the list of results that appears.

  2. 02

    Sign in

    Click Add connection, then log in to BackgroundErase in the tab that opens. You need an account there first: Zapier links an existing one, it never creates it.

  3. 03

    Allow access

    Grant Zapier access to the account. If the images you plan to process belong to a colleague, make sure you can read them before you build the Zap around them.

First Zap

Your first Zap: product photos with the background removed

GoalEvery photo added to a folder comes back as a transparent PNG, saved next to the originals.

  1. 01

    Choose the starting folder

    Create a Zap and pick your storage app with its new-file event, pointed at the folder where raw photos land. BackgroundErase cannot start a Zap, so this step always belongs to another app.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent files of the connected account; choose a real photo so the mapping in the next step uses an actual image.

  3. 03

    Add the removal

    Add BackgroundErase and pick Remove Background From File. Map the file object to File Data and its name to File Name, then set Output Type, PNG as Output Format, and Size.

  4. 04

    Store the result

    Add a second action in your storage app to upload the processed file into an output folder. Use a different folder from the watched one, or the Zap will feed on its own results.

  5. 05

    Test, then publish

    Test each step and open the output folder to check the cut-out edges. When it looks right, click Publish. This Zap has two actions, so it needs a paid plan.

Actions

BackgroundErase actions on Zapier

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

1

Make an API Call

Action

In Zapier“Performs an arbitrary authorized API call.”

Sends a request you write yourself to BackgroundErase, using your existing connection, for whatever the two ready-made actions do not cover.

When to use it
a developer on the team has found an endpoint in the BackgroundErase documentation and needs it inside a Zap.
Watch out
URL takes a path relative to the BackgroundErase API, such as /v2/account, and Method is required too.
2

Remove Background From File

Action

In Zapier“Uploads an image file to BackgroundErase and returns the processed image.”

Takes an image file carried by an earlier step, sends it to BackgroundErase and hands back the processed picture, optionally cropped tight around the subject.

When to use it
photos arrive as attachments or files in a storage folder, rather than as links.
Watch out
File Data expects the file object itself, not a text link; mapping a URL here is the classic reason the step fails.
3

Remove Background From Image URL

Action

In Zapier“Downloads an image from a public or signed URL, removes the background, and returns the processed image as a file.”

Fetches a picture from a web address, strips its background and returns the result as a file that the following steps can store or attach.

When to use it
your sheet, form or catalog only holds image links, so there is no file to pass along.
Watch out
the link must be publicly reachable or properly signed; private Drive links, expired signatures and pages behind a login may fail.
When it breaks

When a BackgroundErase Zap breaks

Zapier links no help article to BackgroundErase. The cases below combine the app's own field notes with limits that hit every Zap.

Most failures trace back to the input, not to the removal itself. Check these first. For a step that keeps failing, our Zapier troubleshooting page is where to start.

  • The image link refuses to load

    Remove Background From Image URL needs a public or signed link. Private Drive links, expired signatures, login pages and internal addresses may all fail.

  • The Zap feeds on its own output

    Saving cut-outs into the folder your trigger watches sets the Zap off again on every result, and burns through your task count fast.

  • Old photos are never processed

    A Zap only reacts to files added after you switch it on. Images already in the folder stay untouched; processing that backlog is a separate job.

  • A big upload batch stalls

    Dropping hundreds of photos at once can make the trigger return a huge batch, and Zapier's flood protection may hold it back instead of running them all.
Need help

Need help automating BackgroundErase with Zapier?

A person reads every message.

FAQ

BackgroundErase Zapier integration: common questions

01Is the BackgroundErase Zapier integration free?
On the Zapier side, yes, within limits. BackgroundErase is not a premium app, so it works on the free plan, which includes 100 tasks a month. A Zap of one trigger plus one background removal fits. The moment you add a storage step for the result, a filter or a search, the Zap becomes multi-step and needs a paid plan. Whatever BackgroundErase bills for its own processing is a separate matter, and no price is published here.
02How many tasks does one image use?
One task for each image processed successfully. The trigger that spots the new file costs nothing, and Zapier checking for new files is free however often it looks. A removal that fails, because of a broken link for example, is not counted. Every extra action adds its own task, though: a Zap that removes the background and then uploads the result uses two tasks per photo, which halves what a monthly quota covers.
03Does BackgroundErase work in real time on Zapier?
That depends on the app that starts the Zap, since BackgroundErase has no trigger. If the starting app offers an instant trigger, the image is processed straight away whatever your plan. If it relies on a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, and every minute on Team and Enterprise. The removal itself runs as soon as the Zap reaches that step.
04What is required to connect BackgroundErase?
A BackgroundErase account, and read access to the images you want to process if they belong to someone else. From the Apps page of your Zapier account, add a connection, choose BackgroundErase, sign in in the tab that opens and grant access. The connection is then shared by all three actions and every Zap that uses them, so it only has to be set up once. Have a source app ready as well, since BackgroundErase never starts a Zap: a folder, a form or a sheet has to supply the image.
05Why does Remove Background From Image URL fail on some links?
Because the link has to be reachable by BackgroundErase without anyone signing in. The app's own help text warns that private Google Drive links, expired signed URLs, login-protected pages and internal network addresses may fail. A link that opens fine in your browser can still be private to your session. When images live in private storage, pass the file itself to Remove Background From File instead of its link. Zapier then carries the file between steps for you.
06What if the BackgroundErase operation needed is missing from Zapier?
Try Make an API Call first. It sends a custom request to BackgroundErase through your existing connection, so anything the app's developer interface supports can be reached, provided someone knows the right path and method. If that route is too technical for the team, check what other platforms offer for BackgroundErase, or ask the vendor whether a ready-made action is planned. Without a trigger, reacting to events inside BackgroundErase stays impossible.
07Zapier, Make or n8n for BackgroundErase?
Judge by criteria, not by a ranking. Coverage: on Zapier you get two ready-made removal actions plus a custom request, so compare with what the others list. Cost: Zapier bills every successful action, and a remove-then-store flow uses two tasks per image, which matters at catalog volume. Ownership: pick the tool the person who will maintain the flow is most at ease with. Run each candidate on a handful of real photos before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations