Resources · Make integration

Picnie Make integrationAutomate Picnie with Make.

Tired of editing the same images by hand before they go out? The Picnie Make integration gives you 7 action modules to create, resize, compress, convert, filter and merge images. This page connects your account and walks you through a first working scenario.

Try the Picnie integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Picnie Make integration do for you?

The Picnie Make integration lets a Make scenario (the automation you build, a chain of modules) send images to Picnie and get the edited result back, with no code. Each module is one brick of that chain. Picnie brings 7 of them, all actions: they act on an image another step hands them. Make gives no official description for them, so what this page says about each one is read from its name.

Web-ready product photos. A shop owner drops a large photo into another app. Resize an Image brings it to the size the storefront expects, then Compress an Image makes the file lighter before it gets published.

One file type across the team. Designers export in whatever format they like. Convert an Image sits in the middle of the flow and hands every file on in the same format, so the next tool never chokes on an odd extension.

Branded visuals without opening an editor. Merge Two Images lays a logo over a picture, Apply Filter on Image gives a whole series the same look, and Create an Image produces a new visual from Picnie.

What Make does not do here: Picnie has no trigger, so it never starts a scenario on its own. The flow opens on another app, or on the schedule you set in Make. For anything the listed modules leave out, Make an API Call reaches the rest of the Picnie API with the same connection.

Still weighing tools? Our n8n vs Make comparison lays out the criteria, the Make review covers the editor in depth, and Make pricing explains how operations are counted.

Connect

How do you connect your Picnie account to Make?

  1. 01

    Copy your API key and username

    You need an active Picnie account first. In the Picnie dashboard, open your profile section. Copy the API key shown there, then copy the username displayed on the same page. Keep both at hand for the next step.

  2. 02

    Add a Picnie module and open the connection

    In your scenario, add any Picnie module and click Create a connection. A connection is your Picnie account linked to Make once, then reused by every Picnie module you add later. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste the API key and the username you copied from your Picnie profile, then follow the on-screen instructions to finish. Once the connection is saved, the module fields open up and you can start filling them.

First scenario

Build your first scenario with Picnie

GoalWhen an image arrives from another app, Make sends it to Picnie to resize it and then compress it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Picnie has no trigger, so pick the module of the app where your images first land, such as a storage or form app.

  2. 02

    Add Resize an Image

    Click the + on the right of that first module, search for Picnie and pick Resize an Image. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the image

    Fill the module fields. Where the image goes, map the file coming out of the first module. Each item that flows between modules is called a bundle: here, one bundle is one image.

  4. 04

    Chain Compress an Image

    Click the + on the right of Resize an Image and add Compress an Image. Map the resized image from the previous step, so the lighter file is built from the right version.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check that the image went through both Picnie steps.

  6. 06

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Modules

What each Picnie module does

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

Picnie1

Apply Filter on Image

ActionIn the docs only

A consistent look across a batch of pictures, without touching an editor: this action runs a Picnie filter on the image your scenario hands it and passes the filtered version on.

When to use it
a gallery or a set of social posts where every picture should share one visual style.
Watch out
check the result with Run once on a real photo before switching on, since the filter applies to every image that reaches it.
Picnie2

Compress an Image

ActionIn the docs only

Lighter files are what you get here. The module sends an image to Picnie for compression and returns a smaller file, ready for a web page, an email or an upload.

When to use it
as the last Picnie step, right after a resize, so you squeeze the final version rather than the original.
Watch out
on the Make Free plan, a scenario handles files up to 5 MB, so very heavy originals may need a paid plan.
Picnie3

Convert an Image

ActionIn the docs only

Every image leaves in the format the next tool expects. This action takes the file from the previous module, has Picnie convert it, and hands the converted file to whatever comes after.

When to use it
files arrive from several people in mixed formats while your site, shop or archive wants a single one.
Watch out
place it before any resize or compression step, so those later modules work on the converted file.
Picnie4

Create an Image

ActionIn the docs only

Instead of editing an existing picture, this module asks Picnie to produce a new one inside the scenario, then passes it on as a bundle the next modules can reuse.

When to use it
you want a fresh visual each time a record appears elsewhere, for example a new product added to a sheet.
Watch out
each image created counts as one operation, the unit Make counts on your plan, so test with Run once first.
Picnie5

Make an API Call

ActionIn the docs only

Your way into the parts of Picnie the six other modules do not cover. It calls any endpoint of the Picnie API from the scenario, reusing the connection you already created.

When to use it
the Picnie feature you need has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the Picnie API documentation open and start with a single Run once to read the response.
Picnie6

Merge Two Images

ActionIn the docs only

Two pictures become one. Picnie combines the pair you map into the module, which is handy for stamping a logo or a badge on a photo without a design tool.

When to use it
branding product shots or event photos before they are shared or published.
Watch out
both images must be available in the scenario at this point, so map them from earlier modules and confirm with Run once that the right pair reached Picnie.
Picnie7

Resize an Image

ActionIn the docs only

Pictures come out at the size your destination needs. The action sends the incoming image to Picnie, changes its dimensions, and returns the resized file for the next step of the flow.

When to use it
a marketplace, a newsletter or a website asks for a set size and your photos arrive straight from a camera or a phone.
Watch out
resize before you compress, otherwise the compression works on pixels that get thrown away next.
Need help

Need help automating Picnie with Make?

A person reads every message.

FAQ

Picnie and Make: frequent questions

01Is the Picnie Make integration free?
Yes, on the Make side. Picnie 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 of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. Picnie itself needs its own active account, and its pricing is on the Picnie website.
02What do you need to connect Picnie to Make?
Two things: an active Picnie account and the credentials from its profile page. In the Picnie dashboard, open your profile section and copy the API key, then the username shown on the same screen. In Make, add a Picnie module, click Create a connection, optionally give it a name, and paste both values. The connection is stored once and every Picnie module in your scenarios can reuse it, so you will not repeat this step for each new module.
03Can a Picnie scenario start in real time?
Not from Picnie itself. The app has no trigger module, so nothing in Picnie can start a scenario. You have two ways to get going. Open the flow with the trigger of another app, for example a storage service where new images land. Or use the schedule on the first module: a new scenario runs every 15 minutes by default, and paid plans allow 1 minute. The Picnie modules then process whatever image that first step hands them.
04What if the Picnie module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Picnie API with the connection you already set up, so you are not limited to the six ready-made image modules. Keep in mind that Make's own documentation for Picnie is marked as AI-generated from the official Picnie docs and may contain mistakes, so check important details against the Picnie documentation. If a Make plan limit gets in the way, such as the 5 MB file size on the Free plan, a paid plan raises it.
05Should you use Make or n8n for Picnie?
It depends on your criteria. On Make, Picnie comes with 7 modules: six image actions plus Make an API Call, and no trigger. Whether n8n offers a Picnie node is not covered here, so check its catalog before deciding. Look at what matters for your team: which tool your other apps already run on, how you prefer to build (a visual editor with modules and bundles in Make), and how each tool counts usage. Make counts operations per month on its plans.
Same platform

Other docs you might need on this stack.

Browse all integrations