Resources · Make integration

Tinify Make integrationAutomate Tinify with Make.

Heavy images slowing things down, and no time to run each one through Tinify by hand? The Tinify Make integration gives you 3 action modules: compress an image, convert it to another type, or call the Tinify API directly. This guide connects your account and walks you through a first scenario.

Try the Tinify integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tinify Make integration do for you?

The Tinify Make integration lets Make send images to your Tinify account and get back a lighter or converted file, with no code. You build a scenario, the automation Make runs for you, out of modules, the bricks of that scenario, and Tinify supplies three of them, all actions.

Lighter uploads without the manual step. A photographer drops shots into a shared storage folder; a trigger from that storage app starts the scenario, and Compress an Image hands each file to Tinify before it moves on. Every image travels as a bundle, one item passed from module to module.

Images in the type your site expects. A web shop receives supplier visuals in mixed formats. Convert an Image turns each one into another image type, so the product team stops converting files one by one. Tinify's own description mentions WebP, JPEG and PNG.

Anything the two modules leave out. Make an API Call reaches any endpoint of the Tinify API with the same connection, for the cases the other modules do not cover.

What Make will not do here: Tinify has no trigger, so the scenario never starts by itself on the Tinify side. Another app, or the schedule you set, has to start it. If you are weighing tools, Tinify may also have an n8n node, and our n8n vs Make comparison lays out the criteria. To judge Make as a whole, read the Make review, and check Make pricing before you count operations.

Connect

How do you connect Tinify to Make?

  1. 01

    Copy your Tinify API key

    You need an active Tinify account and an API key. Log in to Tinify, open the Developers section, click the link that creates or manages your API key, then copy the key shown on screen.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Give the connection a clear label in the Connection name field if you like, it is optional. Paste the API key you copied from Tinify, confirm, and the module is ready to use.

First scenario

Your first scenario with Tinify

GoalWhen a new image lands in the app you store files in, Make sends it to Tinify, compresses it, then converts it to the image type you need.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Tinify has no trigger, start with the app where your images arrive.

  2. 02

    Add Compress an Image

    Click the + to the right of that first module, search for Tinify and pick Compress an Image. Click Create a connection and paste your API key.

  3. 03

    Map the image from the first module

    Fill the module fields by mapping the file the first module passes along. Make shows the data it received, so you pick it from the list instead of typing anything.

  4. 04

    Chain Convert an Image

    Add Convert an Image after the compression, map the lighter file coming out of the previous module, and choose the image type your site or your team expects.

  5. 05

    Test with Run once

    Click Run once and drop a test image where the first module looks. Open each module's bubble to read the bundles it received and check the file that came out.

  6. 06

    Schedule and switch it on

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

Modules

What the Tinify modules do

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

Tinify1

Compress an Image

Action

In Make“Uploads an image for compression.”

Sends one image to Tinify and gives you back a lighter version you can pass to the next module, whether that is a storage folder, a CMS or an email.

When to use it
a blog team uploads full-size photos and you want every file slimmed down before it goes anywhere public.
Watch out
on the Make Free plan, files are capped at 5 MB, so a very large original may stop the scenario before Tinify even sees it.
Tinify2

Convert an Image

Action

In Make“Converts an image to another image type.”

Turns an image into another image type and returns the new file, which saves you opening an editor for each visual a supplier or a colleague sends over.

When to use it
your shop or website expects one format, and incoming files keep arriving in several others.
Watch out
place it after Compress an Image if you want both steps, and map the output of that module, not the original file.
Tinify3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the Tinify API from your scenario, reusing the connection you already created, so you are not limited to the two ready-made modules.

When to use it
Tinify offers something in its API that neither Compress an Image nor Convert an Image exposes.
Watch out
you build the request yourself here, so keep the Tinify API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating Tinify with Make?

A person reads every message.

FAQ

Tinify and Make: common questions

01Is the Tinify Make integration free?
Yes, on the Make side. Tinify is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes, caps files at 5 MB and gives 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 per run; usage is counted in operations each month. Your Tinify subscription is a separate matter, covered on the Tinify pricing page.
02What do you need to connect Tinify to Make?
Two things: an active Tinify account and a Tinify API key. You find the key in the Developers section of your Tinify account, through the link that creates or manages API keys. In Make, add a Tinify module, click Create a connection, optionally name the connection, then paste the key. The connection is saved once and every Tinify module in your scenarios reuses it, so you never paste the key again for the next module.
03Does the Tinify Make integration have a real-time trigger?
No. Tinify has no trigger at all, scheduled or instant, so something else has to start the scenario. Two options. Begin with a trigger from the app where your images arrive, such as a storage service; if that app offers an instant trigger, it calls Make through a webhook as soon as a file lands. Or rely on the schedule of the first module, every 15 minutes by default on a new scenario. Tinify then only acts on the images the first module hands over.
04What if the Tinify module you need is missing in Make?
It depends on what you need. The two ready-made modules cover compression and conversion. For anything else the Tinify API offers, use Make an API Call: it reaches any endpoint of the API with your existing connection. The Make documentation for Tinify also carries a warning that it was generated with AI from the official Tinify docs and may contain mistakes, so check important details with Tinify directly before you build around them.
05Should you use Make or n8n for Tinify?
It depends on the tool you already run. Tinify may also have an n8n node, so the choice rarely comes down to the app itself. In Make, you get three modules, a guided connection with a single API key, and a visual editor where you test with Run once before switching anything on. If your automations already live in n8n, checking the Tinify node there is the logical first step. Neither option is ranked here: compare how each tool fits your team.
Same platform

Other docs you might need on this stack.

Browse all integrations