Resources · Make integration

Clipdrop Make integrationAutomate Clipdrop with Make.

What if every product line or photo went through Clipdrop without you opening it? The Clipdrop Make integration gives you 4 action modules for image work. This page shows how to link your account, build a first scenario and pick the right module.

Try the Clipdrop integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clipdrop Make integration do for you?

The Clipdrop Make integration lets a Make scenario, the automation you build as a chain of modules, send text or pictures to Clipdrop and get images back. Each module is one brick of that chain. Clipdrop brings 4 of them, all actions: they act on what an earlier step hands them.

Visuals from a list of ideas. A content team keeps short descriptions in a spreadsheet. Another app picks up each new line, and Generate an Image from a Text turns it into a picture ready to file or post.

Clean product shots. An online shop receives supplier photos with busy backgrounds. The module Removes a Text, Removes a Background, Reimagines and/or Portrait surface normals strips the background or the stray text before the photo reaches the catalog.

Depth data for portraits. A studio that edits portraits can send each one to Portrait Depth Estimation and keep the result next to the original.

What Make does not do here: Clipdrop has no trigger, so something else has to start the scenario, either another app or the schedule. Make also warns that its own documentation for Clipdrop is limited, which is why testing each step matters. When a module is missing, Make an API Call reaches the rest of the API. If you weigh another tool, read n8n vs Make; to go further on the editor, the Make training covers it, and the Make pricing page explains plans.

Connect

How do you connect Clipdrop to Make?

  1. 01

    Add a Clipdrop module

    In your scenario, add any Clipdrop module and click Create a connection. A connection is your Clipdrop account linked to Make once, then reused by every Clipdrop module you add later.

  2. 02

    Name it if you like

    Make offers a name field for the connection. It is optional, but a clear name helps when a client account and your own sit side by side in the same Make organization.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Clipdrop page or paste the key Clipdrop gives you. Then click Save, and the module is ready to fill.

First scenario

Your first scenario with Clipdrop and Make

GoalWhen a new description lands in another app, Make sends it to Clipdrop and gets an image back.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Clipdrop has no trigger, pick the app where your descriptions live.

  2. 02

    Set up the first module

    Choose that app's module, click Create a connection to link the account, then fill its fields. Make lists what it can read once the connection exists.

  3. 03

    Add the Clipdrop action

    Click the + on the right, search Clipdrop and pick Generate an Image from a Text. Connect your account, then map the description coming from the first module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time; open each module to read the bundles, the items passed from one module to the next, and check the image.

  5. 05

    Schedule and switch on

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

Modules

What each Clipdrop module does

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

Clipdrop1

Generate an Image from a Text

Action

In Make“Generates an image from a text.”

You write a description and get a finished picture back, without opening Clipdrop. The text can come from any earlier module of the scenario.

When to use it
a new article title or product line should come with an illustration, and you want that picture made each time new text comes in.
Watch out
Make documents this module briefly, so run it once and look at the output bundle before you plan the steps that follow.
Clipdrop2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This gives you access to parts of Clipdrop that the three other modules leave out. It sends a request of your choice to the Clipdrop API and reuses the connection you already created.

When to use it
the Clipdrop feature you need exists in its API but not as a ready module in Make.
Watch out
you describe the request yourself, so keep the Clipdrop API reference open and test with Run once before switching the scenario on.
Clipdrop3

Portrait Depth Estimation

Action

In Make“Processes an image using Portrait Depth Estimation.”

Hand it a portrait and you get back the depth estimation Clipdrop computes for that picture, with no manual editing. The photo comes from an earlier module of the scenario, such as a storage app.

When to use it
a studio or a creative team works on portraits and wants depth information for each new photo, stored next to the original file.
Watch out
it only estimates depth, it does not change the photo; add another step to store or use the result.
Clipdrop4

Removes a Text, Removes a Background, Reimagines and/or Portrait surface normals

Action

In Make“This module replaces a background, removes a background and/or removes text.”

One module gathers several cleanups: it can take out a background, swap it for another, or erase text printed on a picture. Pick this one over the others whenever the photo itself has to change.

When to use it
supplier or customer photos arrive with clutter behind the subject, or with unwanted text on them, and should look neat before publication.
Watch out
since the module does several jobs, check with Run once that it applied the edit you expected.
Need help

Need help automating Clipdrop with Make?

A person reads every message.

FAQ

Clipdrop and Make: frequent questions

01Is the Clipdrop Make integration free?
Yes, on the Make side. Clipdrop is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your Clipdrop account and its own terms are a separate matter.
02What do you need to connect Clipdrop to Make?
A Clipdrop account and a Make account. The Make documentation lists no other prerequisite for Clipdrop and gives no dedicated connection guide, so the generic path applies: add a Clipdrop module, click Create a connection, give it a name if you want, then either authorize Make on the Clipdrop page or paste the key Clipdrop provides, and click Save. The connection is then shared by every Clipdrop module in your scenarios, so you only do this once.
03Does the Clipdrop Make integration start a scenario in real time?
No, because Clipdrop has no trigger module in Make. All four modules are actions, so the scenario needs another starting point. You can open it with a trigger from another app, for example the tool where your texts or photos arrive, and let Make check it on the schedule. A new scenario runs every 15 minutes by default, and the Free plan does not go below that interval. If the other app offers an instant trigger, the scenario starts as soon as that app calls Make.
04What if the Clipdrop module you need is missing in Make?
Use Make an API Call. It is part of the Clipdrop app in Make and calls any endpoint of the Clipdrop API with the connection you already have, so you can reach features the three other modules do not cover. Keep in mind that Make states its Clipdrop documentation is limited for lack of public information, so the module pages will not explain much. Test each request with Run once and read the bundles to see exactly what Clipdrop sends back.
05Should you use Make or n8n for Clipdrop?
It depends on where your team already builds automations. Many apps exist both as a Make app and as an n8n node, so check whether n8n covers Clipdrop for your case before choosing. On Make, you get the 4 modules described on this page, including Make an API Call for the rest of the API, and a Free plan to test them. The comparison page linked above sets the two tools side by side without ranking them for you.
Same platform

Other docs you might need on this stack.

Browse all integrations