Resources · Make integration

Screenshotbase Make integrationAutomate Screenshotbase with Make.

Need a screenshot of a web page every time a new link shows up? The Screenshotbase Make integration gives you 2 action modules, no trigger. This guide connects your account and walks you through a first scenario that captures a page from its URL.

Try the Screenshotbase integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Screenshotbase Make integration do for you?

The Screenshotbase Make integration lets a Make scenario (the automation you build, a chain of modules) ask Screenshotbase for a capture of a web page, starting from nothing more than its URL. Every module is one brick of that chain, and the capture lands in the next brick without anyone opening a browser.

A visual record of every page you publish. A marketing team logs each new landing page in a sheet. The scenario reads the new row, hands the address to Take a Screenshot of a URL, and passes the result along so the team keeps a picture of the page as it looked on launch.

Proof of what a competitor page showed. Someone on the sales side drops a link into a form. Make captures the page with the same module, so the discussion that follows is about a picture, not a memory.

Anything the list does not cover. The app ships only two modules. When you need another Screenshotbase feature, Make an API Call reaches it through the connection you already set up.

Know the limits before you build: Screenshotbase has no trigger in Make, so a scenario always starts from another app or from Make's own schedule. Its Make documentation is AI-generated from the vendor docs and asks you to verify important details, so check the output of your first run. If Screenshotbase also has an n8n node, our n8n vs Make comparison lays out the criteria. To go further, see the Make training or the Make troubleshooting guide.

Connect

How do you connect Screenshotbase to Make?

  1. 01

    Copy your API key

    You need an active Screenshotbase account first. Log in, open the Dashboard, and copy the API key shown there. That key is the only credential Make asks for.

  2. 02

    Open the connection window

    In your Make scenario, add a Screenshotbase module and click Create a connection. A connection is your Screenshotbase account linked to Make once, then reused by both modules of the app.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (it is optional), paste the API key you copied, and save. The module is now ready to fill in.

First scenario

Build your first scenario with Screenshotbase

GoalWhen a new page address reaches another app, Make captures that page with Screenshotbase.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your URLs arrive, a sheet or a form for example, and choose the module that reads new entries.

  2. 02

    Add Take a Screenshot of a URL

    Click the + on the right of that first module, search for Screenshotbase and pick Take a Screenshot of a URL. Select the connection you created earlier.

  3. 03

    Map the address

    In the module, map the address coming from the first module instead of typing one. Each bundle (one item, here one row or one entry) then brings its own page to capture.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open the bubble above each module to read the bundles it received and check what Screenshotbase sent back before you add the next app.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module with the clock; a new scenario checks every 15 minutes by default. Then switch the scenario on so each new address is captured without you.

Modules

What the Screenshotbase modules do

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

Screenshotbase1

Make an API Call

ActionIn the docs only

This module opens the rest of the Screenshotbase API to your scenario, with the same connection and the same API key, so you are not stuck with the one ready-made capture module.

When to use it
pick it when you need a Screenshotbase feature that Take a Screenshot of a URL does not offer.
Watch out
you write the request yourself, so keep the vendor's API documentation open and test with Run once before switching the scenario on.
Screenshotbase2

Take a Screenshot of a URL

ActionIn the docs only

You get a capture of any web page from a single address, handed to the next module of your scenario so another app can store or share it.

When to use it
choose it whenever a new link lands in a sheet, a form or a message and you want a picture of that page right after.
Watch out
the Make documentation for this app is AI-generated and lists no output detail, so read the bundle after Run once before mapping it.
Need help

Need help automating Screenshotbase with Make?

A person reads every message.

FAQ

Screenshotbase and Make: frequently asked questions

01Is the Screenshotbase Make integration free?
Yes, on the Make side. Screenshotbase 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, and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute and remove the cap on active scenarios. Make counts usage in operations, one execution of one module on one bundle. Your Screenshotbase subscription is separate: check its own pricing page.
02What do you need to connect Screenshotbase to Make?
An active Screenshotbase account and its API key. The key sits on your Screenshotbase Dashboard: copy it, add any Screenshotbase module to a scenario, click Create a connection, paste the key and save. Naming the connection is optional. The same connection then serves both modules, including Make an API Call, so you only go through this once per account. If the key is refused, copy it again from the Dashboard and make sure the account is still active.
03Does Screenshotbase trigger a Make scenario in real time?
No, because the app has no trigger module in Make. A scenario that uses Screenshotbase has to start elsewhere. You can open it with a trigger from the app that receives your links, a sheet or a form for instance, or let Make start it on a schedule. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. Whether the start is instant then depends on the trigger of that other app, not on Screenshotbase.
04What if a Screenshotbase module is missing in Make?
Use Make an API Call. It calls any endpoint of the Screenshotbase API with the connection you already have, so an option that Take a Screenshot of a URL does not expose stays reachable. You write the request yourself, which means reading the Screenshotbase API documentation first. Keep in mind that the Make documentation for this app is AI-generated from the vendor docs and invites you to verify important details, so test each new call with Run once.
05Should you use Make or n8n for Screenshotbase?
It depends on the tool your team already builds in. In Make, Screenshotbase offers two actions and no trigger, so every scenario starts from another app or from a schedule, and Make an API Call covers the rest of the API. The same app often has an n8n node too. Compare what each tool actually exposes for Screenshotbase before choosing, then build a small test scenario and check the capture you get back.
Same platform

Other docs you might need on this stack.

Browse all integrations