Resources · Make integration

Poof Make integrationAutomate Poof with Make.

Can Make clean up image backgrounds for you with Poof? The Poof Make integration gives you 3 action modules, including Remove background, and no trigger. This page is for builders who know Poof and are new to Make: connect the account, then run a first scenario.

Try the Poof integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Poof Make integration do?

The Poof Make integration links your Poof account to Make so a scenario (the automation you build in Make, a chain of modules) can call Poof without any code. Each module is one brick of that chain; Poof brings three actions and relies on another app or on a schedule to start the run.

Product photos ready for the shop. A picture lands in a storage or form app you already use, and Remove background hands it to Poof in the same scenario. The next module can take the result and store it wherever your catalog lives.

A quick look at your account. Get account info reads the details of the connected Poof account, which is handy as a check step before a batch of images starts moving through the scenario.

Anything the list does not cover. Make an API call reaches any endpoint of the Poof API with the same connection, so you are not stuck with the three named modules.

Know the limit before you start: Make itself says its documentation for Poof is limited, because little public information exists about the app. Expect to test each module with Run once and read what comes back. The Make troubleshooting guide helps when a run fails, and the Make pricing page explains how operations are counted. If you are weighing tools, the same app often has an n8n node too; the n8n vs Make comparison lays out the differences.

Connect

How do you connect Poof to Make?

  1. 01

    Add a Poof module

    In your scenario, add any Poof module, for example Remove background. In the module panel, click Create a connection. This connection is your Poof account linked to Make once, then reused by every Poof module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off later. A clear label such as the account owner or the client makes it easy to pick the right one when several Poof accounts sit in the same Make organization.

  3. 03

    Authorize and save

    Follow what Make shows: either authorize Make on the Poof page that opens, or paste the key Poof gives you. Then click Save. From now on, Make can list what it is allowed to read in the module fields.

First scenario

Your first scenario with Poof

GoalWhen a new image arrives in another app, Make sends it to Poof with Remove background and passes the result to the next module.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Poof has no trigger, pick the app where your images arrive and its module.

  2. 02

    Add Remove background

    Click the + on the right of that first module, search for Poof and choose Remove background. Click Create a connection if this is your first Poof module.

  3. 03

    Map the image

    Fill the module fields by mapping data from the first module. Each image travels as a bundle, one item passed from a module to the next.

  4. 04

    Add a check step

    Click the + again and add Get account info. It reads the account behind the connection, so the output tells you whether the scenario used the Poof account you meant.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and confirm the image went through.

  6. 06

    Schedule and switch on

    Set the schedule on the first module with the clock icon; a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Modules

What the Poof modules do in Make

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

Poof1

Get account info

ActionIn the docs only

You get the details of the Poof account behind your connection, returned as data the next module can use. It is a read step: nothing changes on the Poof side.

When to use it
right after connecting, or at the start of a scenario, to confirm Make talks to the account you expect before images start moving.
Watch out
Make does not document which details come back, so run it once and read the output before mapping anything.
Poof2

Make an API call

ActionIn the docs only

This module opens the whole Poof API to your scenario, reusing the connection you already made. Any endpoint the other two modules skip becomes reachable from here.

When to use it
when Remove background or Get account info does not do the exact job, and the Poof API does.
Watch out
you need to know the endpoint you are calling, and the Make documentation for Poof is limited, so test each call with Run once first.
Poof3

Remove background

ActionIn the docs only

Here is the module most people come for: it hands an image to Poof for background removal and returns the result to the scenario. Pair it with an app where pictures arrive, then a module that stores them.

When to use it
a product photo, a portrait or a visual lands somewhere and needs a clean version without opening an editor.
Watch out
each image is one operation on your Make plan, and the Free plan caps files at 5 MB.
Need help

Need help automating Poof with Make?

A person reads every message.

FAQ

Poof and Make: common questions

01Is the Poof Make integration free?
Yes, on the Make side. Poof is a standard app, 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 one minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on each bundle. Your Poof account is a separate matter handled with Poof.
02What do you need to connect Poof to Make?
A Poof account and a Make account. The Make documentation lists no prerequisite and no dedicated connection steps for Poof, so the generic path applies. Add a Poof module, click Create a connection, give it a name if you like, then either authorize Make on the Poof page or paste the key Poof provides, and click Save. The connection is created once and every Poof module in your scenarios reuses it. If it fails, recheck the key or the authorization before anything else.
03Can a Poof scenario start on its own without a trigger?
It depends on what you put first. Poof has no trigger module, so a Poof module cannot start a scenario by itself. You have two options. Place a trigger from another app first, for example the storage or form tool where images arrive, and let Remove background follow it. Or start the scenario on a schedule set with the clock on the first module; new scenarios run every 15 minutes by default, and the Free plan cannot go below that interval. Both ways work without code.
04What if a Poof module is missing in Make?
Use Make an API call. It reaches any endpoint of the Poof API with the connection you already have, so the three listed modules are not a hard ceiling. You do need to know which endpoint you want, and Make warns that its Poof documentation is limited because little public information exists about the app. The safe routine is to build the call, click Run once, read the bundle that comes back, and only then map its data into the next module.
05Should you use Make or n8n for Poof?
It depends on the tool you already run. On Make, Poof comes with three modules, Remove background, Get account info and Make an API call, and it is available from the Free plan. The same app often has an n8n node as well. If your other automations already live in Make, keeping Poof there means one place to build, test with Run once and monitor. If your team works in n8n, check the node there. Neither choice is ranked here: compare the modules each side offers for your case.
Same platform

Other docs you might need on this stack.

Browse all integrations