Resources · Make integration

GetScreenshot Make integrationAutomate GetScreenshot with Make.

Need a screenshot every time a page matters, without opening a browser? The GetScreenshot Make integration gives you 6 action modules to capture a full page or a single element, email the result or check your API usage. This guide connects your account and builds a first scenario.

Try the GetScreenshot integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GetScreenshot Make integration do for you?

The GetScreenshot Make integration lets a Make scenario (the automation you build, a chain of steps) ask GetScreenshot for a capture of a web page and pass the image to the next step. Each step is a module, one brick of the scenario. GetScreenshot brings six of them, all actions: they do something when the scenario reaches them.

A visual record of client pages. An agency that ships landing pages can add a row to a sheet for each page, then let Take Screenshot capture it and file the image next to the row. Nobody has to remember to grab a screenshot before a redesign.

A pricing block sent to the team. When only one part of a page matters, Take Element Screenshot + Send it via Email captures that element and mails it, so a sales lead sees the change in the inbox instead of in a shared drive.

A usage check before a big batch. Get API Usage reads how much of your GetScreenshot plan you have used, which helps before a scenario captures a long list of pages.

What Make does not do here: GetScreenshot has no trigger module, so it never starts a scenario on its own. Something else has to kick it off, a module from another app or the schedule of the scenario. Make's own documentation for this app also warns that it was written with AI help and may contain mistakes, so test each module with a real page first. If you weigh the same job on n8n, the n8n vs Make comparison lays out the differences, and Make pricing explains how operations are counted. To learn the editor properly, the Make training starts from zero.

Connect

How do you connect GetScreenshot to Make?

  1. 01

    Add a GetScreenshot module

    In your scenario, click the + and search for GetScreenshot, then pick any of its modules, for example Take Screenshot. Make asks for a connection (your GetScreenshot account linked to Make once and reused by every module of the app). Click Create a connection.

  2. 02

    Give the connection a name

    The Connection name field is optional, but a clear name helps when a colleague opens the scenario later or when you run a test account next to the real one. Something like the account owner plus the word screenshots does the job.

  3. 03

    Paste your API key

    Log in to GetScreenshot, open your account dashboard and copy the API key shown there. Back in Make, paste it into the credentials field and save. The connection is ready and every GetScreenshot module in your scenarios can use it.

First scenario

Your first scenario with GetScreenshot

GoalWhen a new page to watch shows up in another app, Make captures it with GetScreenshot and hands the image to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the editor. This first module decides when the scenario starts, so pick the app where your list of pages lives.

  2. 02

    Set the starting module

    Search for that app, choose the module that returns the new page to capture, and link its account with Create a connection. Fill its fields: Make lists what it can read once the connection exists.

  3. 03

    Add Take Screenshot

    Click the + on the right of the first module, search for GetScreenshot and pick Take Screenshot. Connect it with your API key, then map in the page to capture, taken from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passing from a module to the next, here one page and its capture).

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Pick your interval, then switch the scenario on.

Modules

What each GetScreenshot module does

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

GetScreenshot1

Get API Usage

ActionIn the docs only

Get API Usage returns how much of your GetScreenshot API you have consumed, so a scenario can look at the numbers before it starts capturing.

When to use it
put it ahead of a run that will capture a long list of pages and check that enough of your quota is left for the batch.
Watch out
this reads GetScreenshot's side only; Make still counts one operation for every module that runs, this one included.
GetScreenshot2

Make an API Call

ActionIn the docs only

Make an API Call gives you a way around the ready-made modules: it sends a request to any endpoint of the GetScreenshot API, reusing the connection you already created.

When to use it
the GetScreenshot API offers something none of the five other modules covers and you still want it inside the same scenario.
Watch out
you write the request yourself here, so keep the GetScreenshot API documentation open while you set it up.
GetScreenshot3

Take Element Screenshot

ActionIn the docs only

Take Element Screenshot captures one part of a page instead of the whole thing, which gives you a tight image of the block you actually care about.

When to use it
a competitor's price table, a hero banner or a stock badge is the only thing worth keeping, and a full-page image would bury it.
Watch out
click Run once on a real page and open the image before you rely on it, to confirm the capture frames the right element.
GetScreenshot4

Take Element Screenshot + Send it via Email

ActionIn the docs only

This module does two jobs in one: it captures a single element of a page and emails the image, so the result lands in someone's inbox without an extra email module.

When to use it
a manager wants to see one changing block, such as a pricing card, and would never open a shared folder to find it.
Watch out
the image leaves by email only; if you also need it stored, add a storage module after it or use Take Element Screenshot instead.
GetScreenshot5

Take Screenshot

ActionIn the docs only

Take Screenshot turns a web page into an image that the next module can store, attach or post, which makes it the natural first pick on this app.

When to use it
you want a dated visual record of a landing page, an order confirmation or a published article, kept wherever your team already files documents.
Watch out
the capture comes back to the scenario, not to a folder, so plan the module that saves it right after this one.
GetScreenshot6

Take Screenshot + Send it via Email

ActionIn the docs only

Here the capture of the whole page goes straight out by email, which saves you from chaining Take Screenshot with a separate mail app.

When to use it
a client or a teammate should receive the page as it looks right now, triggered by an event such as a form submission or a new row.
Watch out
test with Run once and your own address first, so a wrong recipient does not get a flood of images once the scenario is on.
Need help

Need help automating GetScreenshot with Make?

A person reads every message.

FAQ

GetScreenshot and Make: common questions

01Is the GetScreenshot Make integration free?
Yes, on the Make side. GetScreenshot is a standard app, so its modules work from the Free plan onward. The Free plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes and handles files up to 5 MB. Every module that runs counts as one operation on your plan. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. GetScreenshot itself needs an active account with an API key, and its own pricing page tells you what that subscription costs.
02What do you need to connect GetScreenshot to Make?
Two things: an active GetScreenshot account and its API key. Log in to GetScreenshot, open the account dashboard and copy the key displayed there. In Make, add any GetScreenshot module to a scenario, click Create a connection, optionally fill the Connection name field, then paste the key. The same connection then serves all six GetScreenshot modules, so you only do this once per account. If the dashboard shows no key, check your subscription on GetScreenshot first.
03Can GetScreenshot start a Make scenario on its own?
No. GetScreenshot has no trigger module, only six actions, so it never wakes a scenario by itself. Two ways to start anyway. Put a module from another app first, for example the app where new pages or form entries arrive, and let GetScreenshot act on each bundle it passes along. Or rely on the scenario's schedule: every new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute. In both cases the capture happens when the scenario runs, not the moment a page changes.
04What if the GetScreenshot module you need is missing in Make?
Use Make an API Call. It is part of the six GetScreenshot modules and can reach any endpoint of the GetScreenshot API through the connection you already set up, so you are not stuck with the five ready-made actions. You write the request yourself, so keep the GetScreenshot API documentation open. Also note that Make's page for this app was written with AI help and warns it may contain mistakes, so verify anything important with GetScreenshot directly before building a large scenario on it.
05Should you use Make or n8n for GetScreenshot?
It depends on the tool your team already works in. On Make, GetScreenshot comes with six modules, including Make an API Call, a connection based on a single API key, and it is available from the Free plan. If your other automations already live in n8n, check whether GetScreenshot has a node there before you decide. Neither tool is ranked here: list the captures you need, then compare what each one covers for that exact job, module by module.
Same platform

Other docs you might need on this stack.

Browse all integrations