Resources · Make integration

PiAPI/Toolkit Make integrationAutomate PiAPI/Toolkit with Make.

Need cleaner product shots and bigger clips without opening an editor each time? The PiAPI/Toolkit Make integration gives you 4 action modules for images and video. This guide connects your account, builds a first scenario and explains each module.

Try the PiAPI/Toolkit integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PiAPI/Toolkit Make integration do for you?

The PiAPI/Toolkit Make integration lets a Make scenario (the automation you build, a chain of steps) send your images and videos to PiAPI/Toolkit for processing. Each step is a module: here, four actions that remove a background, upscale an image, upscale a video or call the API directly.

Catalog-ready product photos. A shop owner drops raw pictures into a storage app whose trigger starts the scenario. Remove Background from an Image isolates the product, then Upscale an Image gives a larger version for the listing.

Bigger video for a content team. When an editor finishes a clip in another tool, Upscale a Video takes it from there, so nobody reexports by hand.

Anything the three ready-made modules skip. Make an API Call reaches any endpoint of the PiAPI/Toolkit API with the same connection. It asks more from you, since you write the request yourself.

Be aware of the limits. PiAPI/Toolkit has no trigger in Make, so another app or a schedule has to start the scenario. Make's own documentation for this app is marked as limited, which means fields and behavior are best checked in a test run. On the Free plan, files stay under 5 MB. The Make pricing page explains the plans, and Make troubleshooting helps when a run fails.

The same app often has an n8n node too. If you are choosing between the two tools, n8n vs Make sets the criteria side by side.

Connect

How do you connect PiAPI/Toolkit to Make?

  1. 01

    Open the connection window

    Add any PiAPI/Toolkit module to your scenario and click Create a connection. A connection is your PiAPI/Toolkit account linked to Make once, then reused by all four modules.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when several accounts coexist. Then either approve Make on the PiAPI/Toolkit page that opens, or paste the key PiAPI/Toolkit gives you, whichever the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, pick the connection you just saved. If saving fails, recheck the key or the authorization first, then confirm with Run once.

First scenario

Your first scenario with PiAPI/Toolkit

GoalWhen a new picture reaches your scenario from another app, Make removes its background in PiAPI/Toolkit and then upscales the result.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module comes from the app where your pictures land, or from a schedule, since PiAPI/Toolkit has no trigger.

  2. 02

    Add the background removal

    Click the + on the right of that first module, search PiAPI/Toolkit and pick Remove Background from an Image. Choose your connection or create one.

  3. 03

    Map the picture

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

  4. 04

    Chain the upscale

    Add Upscale an Image after it and map the output of the background removal, so the cleaned picture is the one that gets enlarged.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can open them and check what PiAPI/Toolkit sent back.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the PiAPI/Toolkit modules do

PiAPI/Toolkit gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PiAPI/Toolkit1

Make an API Call

ActionIn the docs only

You get access to the whole PiAPI/Toolkit API, beyond the three ready-made modules, while reusing the connection you already set up. You write the request yourself and Make sends it with your account.

When to use it
a feature you need exists in the PiAPI/Toolkit API but no dedicated module covers it.
Watch out
Make's documentation for this app is limited, so rely on the PiAPI/Toolkit API reference to build the request.
PiAPI/Toolkit2

Remove Background from an Image

ActionIn the docs only

This one hands you a picture with its background taken out, ready to drop on a clean page or a colored banner. It works on one image per bundle, so every photo coming in gets its own pass.

When to use it
product shots or portraits arrive with busy backgrounds and need to look consistent.
Watch out
on the Free plan, files over 5 MB are out of reach.
PiAPI/Toolkit3

Upscale a Video

ActionIn the docs only

Here the payoff is a larger version of a clip, produced without anyone reopening an editing tool. Pick it for video only; stills belong to the image upscaler below.

When to use it
a finished clip lands in your storage and has to be delivered at a bigger size.
Watch out
video files grow fast, and the Free plan caps files at 5 MB and each run at 5 minutes, so test with a short clip first.
PiAPI/Toolkit4

Upscale an Image

ActionIn the docs only

Small pictures come back enlarged, which saves you from asking for a new shoot. It pairs well after the background removal, when a cutout needs more pixels for print or a large banner.

When to use it
a still image is too small for where it has to go.
Watch out
map the output of the previous module, not the original file, or you upscale the wrong version.
Need help

Need help automating PiAPI/Toolkit with Make?

A person reads every message.

FAQ

Questions about the PiAPI/Toolkit Make integration

01Is the PiAPI/Toolkit Make integration free?
Yes, on the Make side. PiAPI/Toolkit is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, meaning operations, per month. Whatever PiAPI/Toolkit charges for its own service is a separate matter this page does not cover.
02What do you need to connect PiAPI/Toolkit to Make?
A PiAPI/Toolkit account and a Make account. Make's documentation lists no prerequisite for this app, so the generic flow applies: add a PiAPI/Toolkit module, click Create a connection, optionally name it, then either authorize Make on the PiAPI/Toolkit page or paste the key the app gives you, and click Save. The connection is shared by all four modules, so you only do this once. Since the documentation is marked as limited, a quick Run once on a single module is the safest way to confirm everything works.
03Does the PiAPI/Toolkit Make integration react in real time?
No, because PiAPI/Toolkit has no trigger in Make. All four modules are actions, so something else must start the scenario. Two options exist. Put a trigger from another app first, for instance the storage tool where your images land. Or rely on scheduling, the clock on the first module, which runs every 15 minutes by default on a new scenario. With an instant trigger from that other app, the scenario starts as soon as the event happens; with a scheduled one, it waits for the next check.
04What if a PiAPI/Toolkit module is missing in Make?
Use Make an API Call. When an app has this module, any endpoint of its API can be called from the scenario with the same connection, so features beyond background removal and upscaling stay reachable. You will need the PiAPI/Toolkit API reference to write the request, because Make's documentation for this app is limited and gives no field details. If the Free plan limits are the problem rather than a missing module, such as files above 5 MB or runs longer than 5 minutes, a paid plan lifts them.
05Should you use Make or n8n for PiAPI/Toolkit?
It depends on the tool your team already runs. In Make, PiAPI/Toolkit comes with 4 modules, including Make an API Call for the rest of the API, and every module is an action, so another app or a schedule starts the scenario. The same app often has an n8n node as well. Compare what each tool offers for your exact case, check which modules you need, and pick the one where your other automations already live. The n8n vs Make comparison linked above lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations