Resources · Make integration

AltTextLab Make integrationAutomate AltTextLab with Make.

Images keep arriving and nobody has time to describe them? The AltTextLab Make integration gives you 2 action modules that produce alt text inside an automation. This guide shows how to link your account, build a first scenario and pick the right module.

Try the AltTextLab integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AltTextLab Make integration do?

With the AltTextLab Make integration, Make asks AltTextLab for alt text as part of a scenario, which is the automation you build in Make: a chain of modules that runs on a schedule or when an app calls Make. AltTextLab has no trigger of its own, so the image always comes from another app or from a schedule you set.

Describe every new image on its way through. Start the scenario from the app where your images arrive, then add Generate alt text right after it. Each image travels as a bundle, meaning one item passed from a module to the next, and comes out with a description you can map into the following step.

Reach what the listed modules leave out. With only 2 modules, the catalog is short. Make an API Call uses the same connection to call any endpoint of the AltTextLab API, which is the route when you need something the first module does not offer.

Keep one account for everything. The connection is your AltTextLab account linked to Make once, and both modules reuse it. You set it up a single time and every future scenario picks it from a list.

Be aware of one limit: the Make documentation for AltTextLab is marked as limited, because little public information exists about the app. Field names and formats are not documented there, so test with Run once and read what each module returns before you rely on it. The Make troubleshooting guide helps when a run fails, and the Make training covers scenario basics step by step.

Weighing another tool? n8n often has a node for the same app, and the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect AltTextLab to Make?

  1. 01

    Add an AltTextLab module

    In your scenario, add Generate alt text or Make an API Call, then click Create a connection. Make opens a small window where the link to your account gets set up.

  2. 02

    Name it and authorize

    Give the connection a name if you like, so you can recognize it later. Then either authorize Make on the AltTextLab page that opens, or paste the key AltTextLab gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the list of every AltTextLab module, so the second module and any later scenario use it without asking you again.

First scenario

Build your first scenario with AltTextLab

GoalWhen a new image shows up in the app you already use, Make asks AltTextLab for its alt text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the one from the app where your images arrive, since AltTextLab cannot start a scenario itself.

  2. 02

    Add Generate alt text

    Click the + on the right of that first module, search for AltTextLab and pick Generate alt text. Select your connection or create it here.

  3. 03

    Map the image

    Fill the module fields by mapping the image data coming from the first module. Make shows the items it received, so you click the value instead of typing it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received and the alt text AltTextLab sent back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. The alt text is now ready to map into whatever module you add next.

Modules

What AltTextLab modules can you use in Make?

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

AltTextLab1

Generate alt text

ActionIn the docs only

You get a written description of an image, produced by AltTextLab, that the next module can store or publish. It is the core of this integration and the module most scenarios need.

When to use it
right after the module that brings in a new image, so every picture leaves the scenario with its alt text attached.
Watch out
the documentation does not list its fields, so run the scenario once and check the output before mapping it further.
AltTextLab2

Make an API Call

ActionIn the docs only

This gives you direct access to any endpoint of the AltTextLab API, reusing the connection you already created. Pick it only when Generate alt text does not cover your need.

When to use it
an option from the AltTextLab API that has no dedicated module in Make.
Watch out
you write the request yourself, so check what AltTextLab expects and test each call with Run once first.
Need help

Need help automating AltTextLab with Make?

A person reads every message.

FAQ

AltTextLab and Make: common questions

01Is the AltTextLab Make integration free?
Yes, on the Make side. AltTextLab is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. What AltTextLab charges for its own service is outside Make and is not covered here.
02What do you need to connect AltTextLab to Make?
An AltTextLab account and a Make account. The Make documentation lists no extra prerequisite and no official connection steps, so the generic flow applies: add an AltTextLab module, click Create a connection, give it a name if you want, authorize Make on the AltTextLab page or paste the key the app provides, then click Save. Both modules then share that single connection, and any later scenario can select it from the list without repeating the setup.
03Can AltTextLab start a Make scenario in real time?
No. AltTextLab has no trigger module in Make, neither scheduled nor instant. The scenario starts from something else: a trigger of the app where your images come from, placed as the first module, or the scheduling clock of Make, which runs a new scenario every 15 minutes by default. Whether the start is instant then depends on that other app's trigger, not on AltTextLab. Generate alt text simply runs each time the scenario reaches it.
04What if a feature is missing from the AltTextLab Make modules?
Use Make an API Call. It calls any endpoint of the AltTextLab API with the connection you already have, so an option without a dedicated module is still reachable. Keep in mind that the Make documentation for AltTextLab is marked as limited, since little public information exists about the app, so field details are not spelled out. Test each request with Run once and read the returned bundle before building the rest of the scenario on it.
05Should you use Make or n8n for AltTextLab?
It depends on the tool your team already works in. On Make, AltTextLab offers 2 modules, Generate alt text and Make an API Call, and runs on the Free plan as a standard app. n8n often has a node for the same app, so check its catalog before deciding. The honest criterion is where the rest of your image workflow lives: keeping every step in one tool is simpler to maintain. The comparison page on this site sets the criteria out in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations