Resources · Make integration

Img2Go Make integrationAutomate Img2Go with Make.

What if your product photos came out resized, compressed and cleaned up without you opening an editor? The Img2Go Make integration gives you 9 action modules for image work. This page shows ops and marketing teams how to connect the account and build a first scenario.

Try the Img2Go integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Img2Go Make integration do for you?

The Img2Go Make integration lets Make send images to Img2Go and get the edited version back inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain. Img2Go brings 9 of them, all actions: they work on an image that another step hands over. Make's doc describes none of them, so what each one does below is read from its name: confirm it with a test run.

Catalog pictures ready for the shop. An online store receives supplier photos in all shapes. Chain Remove a Background, then Resize an Image, then Compress an Image, and every picture leaves the scenario with a clean backdrop and a web-friendly weight.

Old archive photos brought back. A local newspaper or a family business digitizing its history can run scans through Colorize an Image and Upscale an Image before filing them.

Visuals from a sentence. A marketing team drafting social posts can pass a short description to Text to image and pick up the picture in the next module, next to the caption.

Know the limits before you start. Make's own documentation for Img2Go is thin: it says there is not enough public information to describe the app fully, so field names and supported formats are not listed there. Img2Go also has no trigger, which means another app or Make's schedule has to start the scenario. If you are still choosing a platform, the n8n vs Make comparison and the Make review set out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Img2Go to Make?

  1. 01

    Open the connection window

    Add any Img2Go module to your scenario and click Create a connection. A connection is your Img2Go account linked to Make once; every Img2Go module in every scenario reuses it afterwards.

  2. 02

    Give it a clear name

    Naming the connection is optional, but a label such as the team or client it belongs to saves guesswork later, when several scenarios and several accounts sit side by side in Make.

  3. 03

    Authorize and save

    Follow what Img2Go asks for: either approve Make on the Img2Go page that opens, or paste the key your Img2Go account gives you. Then click Save and the module fields become available.

First scenario

Your first scenario with Img2Go and Make

GoalWhen a new product photo reaches another app, Make removes its background with Img2Go and then compresses it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Img2Go has no trigger, so this first bubble belongs to the app where your photos arrive.

  2. 02

    Add Remove a Background

    Click the + on the right of that first module, search for Img2Go and pick Remove a Background. Create the connection, then map the image coming from the previous module.

  3. 03

    Chain Compress an Image

    Add a third module with the next +, choose Compress an Image and map the cut-out picture that Remove a Background produced. Each photo travels as one bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and check that the final image looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and switch the scenario on. From then on, every run uses operations, one per module per bundle.

Modules

The 9 Img2Go modules, one by one

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

Img2Go1

Colorize an Image

ActionIn the docs only

You get a colored version of an image, which is what you want for black and white scans that look flat next to modern pictures.

When to use it
right after a scanner or a shared folder hands Make an archive photo, before you file or publish it.
Watch out
the Make doc gives no settings for this module, so run one test image and look at the output before processing a whole batch.
Img2Go2

Compare Images

ActionIn the docs only

Two pictures go in and you get Img2Go's comparison back, handy to spot whether a new version of a visual really differs from the approved one.

When to use it
a designer uploads a revised banner and you want the scenario to check it against the previous file before anyone reviews it.
Watch out
the documentation does not say what the comparison output contains, so read the bundle from a Run once before mapping it further.
Img2Go3

Compress an Image

ActionIn the docs only

Your image comes back lighter, which keeps pages fast and attachments small. It is usually the last Img2Go step in a chain.

When to use it
after resizing or background removal, just before the picture is uploaded to a website or sent by email.
Watch out
on the Free plan Make handles files up to 5 MB, so keep an eye on the size of the photos entering the scenario.
Img2Go4

Convert a File

ActionIn the docs only

This module turns a file into another format through Img2Go, so every picture that reaches the next app arrives in the format it expects.

When to use it
suppliers send images in mixed formats and your shop or your print partner accepts only one of them.
Watch out
Make's doc does not list the supported formats, so check the options the module shows once your connection exists.
Img2Go5

Make API call

ActionIn the docs only

Make lists this Img2Go module under the name Make API call, and the documentation says nothing more about what it sends or returns.

When to use it
only when none of the 8 named modules covers the edit you need and you are ready to explore it with test data.
Watch out
since nothing is documented, treat it as experimental: test with Run once and keep it out of scenarios that run unattended until the result is clear.
Img2Go6

Remove a Background

ActionIn the docs only

You get the subject of the photo without its backdrop, the classic need for product shots, team portraits or listings.

When to use it
as soon as a new product photo arrives from a supplier folder or a form, so the catalog stays visually consistent.
Watch out
each image processed counts as one operation on your Make plan, so filter out files you do not need before this module.
Img2Go7

Resize an Image

ActionIn the docs only

The picture leaves at the dimensions you set, which spares you opening an editor for every banner, thumbnail or social post.

When to use it
one source photo has to feed several channels; add this module once per size you need.
Watch out
the Make doc does not describe the resize options, so compare the output of a Run once with the size your target platform asks for.
Img2Go8

Text to image

ActionIn the docs only

From a written description, Img2Go generates a picture you can pass to the next module, which gives a visual to content that has none.

When to use it
a new blog draft or a new row in your content sheet arrives and you want a first illustration ready for the editor to review.
Watch out
keep a human check before anything is published, because the Make doc does not describe how the prompt is handled.
Img2Go9

Upscale an Image

ActionIn the docs only

A small picture comes back larger, useful when the only version you have was made for a screen and not for print.

When to use it
a client sends a low resolution logo or photo for a brochure and the scenario prepares a bigger copy for the designer.
Watch out
a bigger image is a heavier file, and the Free plan caps files at 5 MB, so follow it with Compress an Image when the size gets close.
Need help

Need help automating Img2Go with Make?

A person reads every message.

FAQ

Img2Go and Make: common questions

01Is the Img2Go Make integration free?
Yes, Img2Go is a standard app in Make, so it works from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Your own Img2Go account is a separate matter, and this page does not cover its pricing.
02What do you need to connect Img2Go to Make?
You need an Img2Go account and a Make account. Make's documentation lists no specific prerequisite for Img2Go and no dedicated connection guide, so the generic steps apply: add an Img2Go module, click Create a connection, optionally name it, then either approve Make on the Img2Go page or paste the key your account provides, and save. The connection is created once and reused by all 9 Img2Go modules in every scenario you build.
03Can an Img2Go scenario in Make start on its own?
Not from Img2Go itself, because the app has no trigger module, only actions. A scenario can still start by itself in two ways. You can place another app's trigger first, for example the module that watches your storage or your form tool, and chain Img2Go after it. Or you can put a schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan does not go below that interval.
04What if an Img2Go module is missing or a limit gets in the way in Make?
It depends on the gap. Make's documentation for Img2Go is limited and describes none of the 9 modules in detail, including the one listed as Make API call, so do not count on that module to fill a missing feature before testing it with Run once. If an edit is not covered, another image app available in Make may handle that step. For file size, remember the Free plan caps files at 5 MB. When you are stuck, the team can look at the scenario with you.
05Should you use Make or n8n for Img2Go?
It depends on where the rest of your automations already live. In Make, Img2Go comes with 9 action modules, available from the Free plan, and needs another app or a schedule to start. On the n8n side, check whether an Img2Go node exists and what it covers before deciding, since this page does not document it. Pick the platform your team already maintains, then compare what each one offers for the specific edits you need, such as background removal or compression.
Same platform

Other docs you might need on this stack.

Browse all integrations