The BackgroundErase Make.com integration lets you remove image backgrounds as part of a scenario. You can process a file from a previous module, process an image URL that already exists in your workflow, or use the universal API module for advanced BackgroundErase requests.

Best fit: Use this integration for catalog cleanup, ecommerce image workflows, Airtable attachment processing, Shopify product image updates, CMS asset cleanup, folder watches, and internal operations flows where Make already moves the image.

Install the Make integration

Start by installing the BackgroundErase app in Make. Once it is installed, add a BackgroundErase module to a scenario and create a connection with your BackgroundErase API key.

Coming soon

Create and connect an API key

BackgroundErase uses API key authentication. In Make, the connection stores your key and sends it as the x-api-key header automatically.

Create a Business account BackgroundErase API access is available on Business and Enterprise plans.
Generate an API key Open your account page, create an API key, and keep it somewhere private while you connect Make.
Connect BackgroundErase in Make When the BackgroundErase module asks for a connection, paste your API key. Make stores it in the connection, so you do not need to map it into every scenario step.

Keep the key inside the Make connection. You should not expose it in public forms, spreadsheet columns, browser code, or mapped scenario output.

How billing works

BackgroundErase uses metered monthly billing for Make scenarios. Each successfully processed image counts as one billable image for the billing period.

The Make modules return billing fields such as billing_model, usage_unit, and billable_units so your team can understand how scenario runs map to BackgroundErase usage.

Choose the right module

The integration includes three modules. Most workflows should use one of the two dedicated background removal modules. The universal API module is there for advanced requests and account checks.

Remove Background from File

Use this when an earlier Make module gives you a file buffer, such as Google Drive > Download a file, Dropbox, OneDrive, HTTP > Get a file, or an email attachment.

Remove Background from Image URL

Use this when your scenario already has a public or signed image URL from Airtable, Shopify, Webflow, Google Sheets, a webhook, or an external CMS.

Make an API call

Use the universal module for advanced BackgroundErase API requests, account checks, future endpoints, or debugging authenticated calls.

Walkthrough: remove background from a file

Use the file module when a previous Make step produces a file buffer. Common examples include downloading a file from Google Drive, Dropbox, OneDrive, an HTTP URL, or an email attachment.

Add the trigger or source module that finds the image, such as Google Drive > Watch files.
Add a download step if the trigger only gives you file metadata. The BackgroundErase file module needs both file name and file data.
Add BackgroundErase > Remove Background from File.
Map File Name from the source filename and File Data from the downloaded binary file.
Choose output options such as transparent PNG, WebP, JPG with a background color, crop, despill, or alpha mask.
Send the returned file buffer to the next app, such as Google Drive, Airtable, Dropbox, Shopify, a CMS, or your own storage step.

If you are unsure which module to use, start with the file module. It avoids many URL permission issues because Make passes the image file directly to BackgroundErase.

Walkthrough: remove background from an image URL

Use the URL module when the image already exists at a public or signed URL. This is common for Airtable attachments, Shopify product images, Webflow CMS assets, Google Sheets rows, webhook payloads, and external CMS assets.

Start with a module that provides an image URL, such as a spreadsheet row, product update, form response, or webhook.
Add BackgroundErase > Remove Background from Image URL.
Map the URL into Image URL. Optionally set an output base name to control the filename used by later modules.
Choose the output type, format, size, crop, despill, and background color options for the destination app.
Save the returned file buffer to storage, attach it to a record, update a product image, or pass it into another Make module.

The URL must be reachable by BackgroundErase's backend. Private Google Drive links, expired signed URLs, login-protected URLs, and internal network URLs may fail. If that happens, download the file in Make first and use Remove Background from File instead.

Universal module for advanced API calls

The Make an API call module is for advanced BackgroundErase requests. Use it when you want to call an endpoint directly, test a new API parameter, debug authentication, or check account status.

A good first test is GET /v2/account. Leave headers, query string, and body empty. The Make connection adds your API key automatically, and the response should show whether the key is valid and what billing model the account uses.

For normal image processing, use the dedicated file or URL module instead. They provide a cleaner interface and return the processed image as a file buffer ready for downstream Make modules.

Supported options

The file and URL modules expose the same practical controls as the BackgroundErase API. Start simple, then add options as your destination requires them.

Output type

Choose Transparent Image for normal cutouts or Alpha Mask when the next step handles compositing.

Format

Choose PNG, WebP, or JPG. PNG is best for transparency. Alpha mask output is always returned as PNG.

Size

Choose preview, medium, HD, full, or auto depending on how much detail the downstream app needs.

Crop

Enable Crop to Subject when you want the output trimmed around the detected foreground.

Despill

Enable Remove Green Spill for green-screen style photos where color bleed appears around edges.

Background color

Set bg_color to flatten the result onto a color such as #FFFFFF or white. Leave it empty for transparent output.

For the full API reference, see the request fields and flags docs.

Limits to know before you turn on a scenario

Max file size: images can be up to 30 MB.
Max pixels: source images can be up to 100,000,000 pixels.
Private URLs: image URLs must be reachable by BackgroundErase. Private, expired, login-protected, or internal URLs may fail.
Multipart handling: for the dedicated file and URL modules, Make handles the multipart form boundary automatically.

Troubleshooting common Make errors

Invalid API key

Reconnect the BackgroundErase app in Make and paste a fresh API key from your account. Make adds the x-api-key header through the connection, so you should not need to add it manually.

API key help

Image too large

BackgroundErase accepts images up to 30 MB and 100,000,000 pixels. Resize the source image or use a smaller export before sending it through the scenario.

Size help

Private image URL

The URL module can only process URLs that BackgroundErase can fetch from its backend. Private Drive links, expired signed URLs, login-protected URLs, and internal network URLs may fail.

URL help

Bad background color

Use a valid hex color such as #FFFFFF or a supported named color such as white. If you do not need a flattened background, leave bg_color empty.

Color help

Support and API docs

If your Make scenario fails and the troubleshooting steps do not resolve it, contact BackgroundErase support with the module name, the error message, and whether you were using a file or image URL.