- Home
- Resources
- Integrations
- PicDefense
PicDefense Make integrationAutomate PicDefense with Make.
Every image that reaches your team can get a PicDefense check without anyone opening a dashboard. The PicDefense Make integration gives you 10 action modules, no trigger. This guide is for people who already use PicDefense and want their first scenario running.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PicDefense Make integration do?
The PicDefense Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) send an image to PicDefense and pass the answer to your other tools. All 10 modules are actions: they run when an earlier step or a schedule starts the scenario, never on their own.
A safer image library. Before a photo goes into your media folder, Image Copyright Risk Assessment can assess it, and Reverse Image Search can look for other places the picture appears online. You decide what happens next, based on what the modules return.
Cleaner user uploads. A community site or marketplace can pass each submitted picture through Detect Inappropriate Content, then through Detect Faces in Image when faces matter for your publishing rules.
Richer image records. Extract EXIF Data From Image, Identify Landmarks in Image and Image Content Labeling turn a bare file into details you can store next to it in a sheet or a database.
Know the limits before you start. PicDefense has no trigger in Make, so another app or Make's own schedule has to start the scenario. The official documentation lists module names without describing their fields, and it warns that its own text was generated by AI and may contain mistakes. Test every module with a real image before trusting it. If you are still weighing the platform, the Make review and the n8n vs Make comparison cover the bigger picture, and Make pricing explains how operations are counted.
How do you connect PicDefense to Make?
- 01
Copy your API token
You need an active PicDefense account. Sign in, open the Settings page from the dashboard and copy the API token shown there. A connection in Make is simply this account linked once, then reused by every PicDefense module.
- 02
Add a PicDefense module
In your Make scenario, add any PicDefense module, for example Check PicDefense Account Credits, and click Create a connection. The Connection name field is optional, but a clear name helps once you have several accounts.
- 03
Paste the token and save
Paste the token you copied into the credentials field and follow the on-screen instructions to finish. From then on, each PicDefense module in any scenario can pick this connection from its list.
Your first scenario with PicDefense
GoalWhen another app hands Make an image, PicDefense runs a reverse search and a copyright risk check on it.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to place the first module. Pick the app where your images already arrive, since PicDefense cannot start a scenario itself.
- 02
Add Reverse Image Search
Click the + to the right of that first module, search for PicDefense and choose Reverse Image Search. Select your connection, then map the image from the previous module into its fields.
- 03
Chain the risk check
Add Image Copyright Risk Assessment after it and map the same image again. Each bundle, meaning one item passed from module to module, now goes through both checks in turn.
- 04
Test with Run once
Click Run once with a single test image waiting in the source app. Open the bubble above each module to read what PicDefense sent back before you build anything on top of it.
- 05
Schedule and switch on
On the first module, open Scheduling: a new scenario runs every 15 minutes by default. Keep that or change it, then turn the scenario on so it runs without you.
What each PicDefense module does
PicDefense gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Modules index
Check Image for Logo Detection
ActionIn the docs onlyYou learn whether a logo shows up in the picture you pass along, so a brand mark does not slip into a post or an ad unnoticed. That is what its name announces; the docs do not describe it further.
Check PicDefense Account Credits
ActionIn the docs onlyHere you get your account's credit status back inside the scenario instead of checking the PicDefense dashboard by hand. It is also the easiest module for proving a new connection works.
Detect Faces in Image
ActionIn the docs onlyAs its name says, this module tells you whether a picture contains faces. That answer helps you decide if an image needs consent paperwork or a different use.
Detect Inappropriate Content
ActionIn the docs onlyThis one screens a picture for content you would not want to publish, giving your scenario a verdict to act on before a human ever sees the file.
Extract EXIF Data From Image
ActionIn the docs onlyEXIF is the hidden metadata a camera writes into a photo. This module pulls it out, so you can store it in a sheet or database next to the file instead of opening each image.
Identify Landmarks in Image
ActionIn the docs onlySend it a travel or city picture and PicDefense tries to name the landmark it shows. You end up with a label you can file or tag by, without guessing from the file name.
Image Content Labeling
ActionIn the docs onlyInstead of one yes or no answer, this module describes what the picture contains with labels. Those labels become tags or alt text drafts that your team reviews instead of writing from scratch.
Image Copyright Risk Assessment
ActionIn the docs onlyThis module rates how risky an image is to use from a copyright point of view, so a questionable picture gets caught before publication.
Make an API Call
ActionIn the docs onlyYour fallback when none of the nine named modules covers what you need. It calls any endpoint of the PicDefense API from inside the scenario, reusing the same connection, so you never paste the token twice.
Reverse Image Search
ActionIn the docs onlyReverse Image Search looks for other places a picture shows up, which tells you whether an image you plan to use is already circulating elsewhere.
Need help automating PicDefense with Make?
A person reads every message.