Resources · Make integration

PiAPI/FaceSwap Make integrationAutomate PiAPI/FaceSwap with Make.

Need face swaps to happen on their own, right after an image lands somewhere? The PiAPI/FaceSwap Make integration gives you 4 action modules, for images, videos and custom API requests. This guide connects your API key and walks you through a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PiAPI/FaceSwap Make integration automate?

The PiAPI/FaceSwap Make integration lets a Make scenario (the automation you build, a chain of steps) send images or videos to PiAPI/FaceSwap and get the swapped result back, without writing code. Each step is a module, one brick of the scenario, and all 4 modules here are actions.

A product mockup with a new face. A marketing team uploads a photo through a form in another app, and Apply a Faceswap to an Image swaps the face before the file moves on to storage or review.

A group photo handled in one pass. When a picture holds several people, Apply Multi Faceswap based on an Image is the module named for that case, so you avoid chaining single swaps.

A short clip personalized. Apply a Faceswap based on a Video covers moving footage, and Make an API Call reaches any other endpoint of the PiAPI/FaceSwap API with the same connection.

Since the app has no trigger, something else has to start the scenario: a module from another app, or the schedule Make puts on the first module. The Make docs describe no module fields for this app, so open each module to see what it asks for. The Make review helps you judge the platform, and Make pricing explains how runs are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect PiAPI/FaceSwap to Make?

  1. 01

    Generate your API key

    Log in to PiAPI/FaceSwap, go to your workspace, open the API key section and click the button that generates a key. Copy the key shown on screen. You need an active account for this step.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any PiAPI/FaceSwap module and click Create a connection. A connection is your PiAPI/FaceSwap account linked to Make once, then reused by every module of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with PiAPI/FaceSwap

GoalWhen an image comes in from another app, Make sends it to PiAPI/FaceSwap and swaps the face.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your images, such as a form or a storage tool.

  2. 02

    Add the face swap module

    Click the + on the right of that first module, search for PiAPI/FaceSwap and choose Apply a Faceswap to an Image. Click Create a connection if this is your first module of the app.

  3. 03

    Map the image

    Fill the module fields by mapping the image from the previous module. Each item passed between modules is a bundle: here, one image per bundle.

  4. 04

    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 check the swap came back.

  5. 05

    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 on one bundle counts as an operation on your plan.

Modules

What each PiAPI/FaceSwap module does

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

PiAPI/FaceSwap1

Apply Multi Faceswap based on an Image

ActionIn the docs only

You get several faces swapped from a single image, which suits team pictures or event shots where more than one person appears. Pick it over the single swap module as soon as more than one face is in frame.

When to use it
a group photo arrives and every face needs replacing in the same run.
Watch out
the Make docs list no fields for this module, so open it after connecting and read what Make asks before mapping anything.
PiAPI/FaceSwap2

Apply a Faceswap based on a Video

ActionIn the docs only

Moving footage is what this one handles: it sends a video to PiAPI/FaceSwap for a face swap, so personalized clips can come out of your scenario instead of a manual editing tool.

When to use it
the source is a clip rather than a still picture.
Watch out
on the Make Free plan, files are capped at 5 MB, which a video can quickly exceed. Check the size before mapping.
PiAPI/FaceSwap3

Apply a Faceswap to an Image

ActionIn the docs only

This is the simplest starting point: one image in, one swapped face back, ready for the next module in your scenario. It is the module used in the first scenario above.

When to use it
a single portrait or product visual needs one face replaced.
Watch out
use only faces you have permission to use, and test with Run once before letting the scenario process real files.
PiAPI/FaceSwap4

Make an API Call

ActionIn the docs only

When the three swap modules stop short of what you need, this one lets you call any endpoint of the PiAPI/FaceSwap API, reusing the connection you already set up, so no second key to manage.

When to use it
the API offers an option none of the listed modules exposes.
Watch out
you write the request yourself here, so keep the PiAPI/FaceSwap API reference open while filling it.
Need help

Need help automating PiAPI/FaceSwap with Make?

A person reads every message.

FAQ

PiAPI/FaceSwap and Make: common questions

01Is the PiAPI/FaceSwap Make integration free?
Yes on the Make side: PiAPI/FaceSwap is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and raise execution time to 40 minutes. Your PiAPI/FaceSwap account is separate: check its own pricing page for the subscription it needs.
02What do you need to connect PiAPI/FaceSwap to Make?
An active PiAPI/FaceSwap account and an API key. You generate the key in your workspace, in the API key section, then copy it. In Make, add a PiAPI/FaceSwap module, click Create a connection, give it an optional name and paste the key. The same connection then serves all 4 modules of the app, so you only do this once per account. The Connection name field is optional, but a clear name saves confusion later if you manage more than one PiAPI/FaceSwap account.
03Does the PiAPI/FaceSwap Make integration react in real time?
No, because the app has no trigger module at all. The scenario has to start elsewhere: with a trigger from another app, such as the tool where your images arrive, or with the schedule on the first module, which runs every 15 minutes by default. Paid plans can go down to 1 minute. From there, the PiAPI/FaceSwap modules act on each bundle that reaches them. Keep in mind that each module run on one bundle counts as an operation on your Make plan.
04What if a PiAPI/FaceSwap module is missing in Make?
Use Make an API Call. It can reach any endpoint of the PiAPI/FaceSwap API with the same connection, so an option the three swap modules do not expose is still within reach. You write the request yourself, which takes the API reference on hand. The Make docs note that their content for this app is generated from vendor documentation and may contain mistakes, so for vendor questions, contact PiAPI/FaceSwap directly.
05Should you use Make or n8n for PiAPI/FaceSwap?
It depends on what you already run. On Make, this app comes with 4 ready modules: three for image and video swaps plus Make an API Call, all usable from the Free plan. The same app often has an n8n node too, so check the n8n side and its node before you choose. The deciding question is simple: which tool already hosts your other automations and offers the modules you need.