Resources · Zapier integration

GetScreenshot Zapier integrationAutomate GetScreenshot with Zapier.

The GetScreenshot Zapier integration gives you 0 triggers, 4 actions and 0 searches. It captures a live web page, or a single element of it, then emails the image or passes it to the next step. Another app has to start the Zap.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the GetScreenshot Zapier integration actually does

It lets a Zap (an automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens) photograph a web page for you. You hand GetScreenshot an address, it returns a capture of the live page. Nothing more, and that narrow scope is the point.

Three outcomes cover most uses. A page image waiting for the next step: Take Website Screenshot captures the page and passes it on, so a later action can post it or file it. A capture in someone's inbox: Take Website Screenshot and Send It via Email does the capture and the delivery in one go, which keeps the Zap at two steps. A crop on one block of the page: the two Advanced actions aim at a single element, a pricing table or a banner, instead of the whole screen.

Now the limits. GetScreenshot has no trigger, so it never starts a Zap on its own: a form, a spreadsheet or a CRM has to hand it the URL. It has no search either, which means it can't look up a capture made earlier. And it doesn't watch a page for changes. Each capture happens once, when the Zap reaches that step (no history, no comparison).

If you're weighing tools, the GetScreenshot Make integration covers the same app on another platform, and the Make vs Zapier comparison sets the two side by side. Before you build anything bigger, the Zapier review is a fair read on what the plans include.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are in plain English.

Zap
The automation itself: one trigger, then the actions that follow, run again every single time the trigger event happens.
Trigger
The event in an app that starts the Zap. GetScreenshot has none, so the trigger always comes from another app.
Action
What the Zap does once it has started: the step that writes, sends or moves something. All four GetScreenshot operations are actions.
Task
The unit Zapier bills. One task equals one action that completed successfully; your plan's monthly count is a count of those.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger reports the event itself, the moment it happens, with no waiting.
Filter
A step that lets the Zap continue only when what arrived meets your condition. Anything else stops right there, quietly.
Connection
Your account of an app, linked to Zapier once, then reused by every step of every Zap that needs that app.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and that requires a paid plan.
Cost

What a capture really costs you

GetScreenshot isn't a premium app, so it works on the free plan. The bill is counted in tasks, and only successful actions count.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Premium appNo, available on every plan
  • BilledEach GetScreenshot action that succeeds

The trigger from the other app costs nothing, however often Zapier checks it. Each GetScreenshot action that goes through costs one task; one that fails costs none. The catch: the free plan builds two-step Zaps only. Capture then post to Slack is three steps, so it needs a paid plan, while the email variants fit in two. A filter counts as a step too, so adding one to an email Zap also pushes it past the free limit. Plan the shape of the Zap before you pick the action.

Connect

Connect GetScreenshot to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You'll need a GetScreenshot account already, because Zapier links an existing account rather than creating one.

  2. 02

    Find GetScreenshot

    Type the app's name in the dialog, select it from the list, then click Add connection. A new tab opens on the GetScreenshot side so you can sign in there.

  3. 03

    Sign in and grant access

    Log in to GetScreenshot and allow Zapier to use the account. The connection is now saved, and every Zap that captures a page will reuse it without asking again.

First Zap

Your first Zap: capture each new competitor page

GoalA marketer logs competitor landing pages in Airtable. Each new record marked as ready gets captured, and the image lands in a Slack channel.

  1. 01

    Start with the Airtable trigger

    Create a Zap and pick Airtable with New Record. Test it: Zapier brings back the three most recent records, so you map fields on a real one.

  2. 02

    Add a filter

    From the plus icon, add Filter. Pick the status field you saw in the test, choose a text rule, type Ready. Half-filled rows stop here.

  3. 03

    Capture the page

    Add GetScreenshot with Take Website Screenshot. Map the record's URL into Website URL and decide on Full Page Capture, which is required.

  4. 04

    Post it to Slack

    Add Slack with Send Channel Message and map the capture from the previous step into the message. This makes four steps, so a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the image shows up in Slack, click Publish to switch the Zap on. From then on, every new ready record gets its capture.

Actions

The 4 GetScreenshot actions

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

1

Take Website Screenshot

Action

In Zapier“Takes a custom screenshot of a live website and makes it available to Zapier so it can get passed to a following action (You need a Starter plan to create Zaps with 3 or more steps).”

Give it a page address and it captures the live page, then hands the result to whatever step comes next. You choose between the visible top of the page and its full height, and you can ask for a PDF too.

When to use it
you want the capture filed in a drive, posted in a chat or attached to a CRM record.
Watch out
a step after it makes the Zap multi-step, which the free plan doesn't allow.
2

Take Website Screenshot and Send It via Email

Action

In Zapier“Takes a custom screenshot of a live website and sends it to an email address of your choice. e.g: john@example.com”

This one captures the page and emails it straight to the address you set, so no extra step is needed. The Zap stays at one trigger and one action, which the free plan accepts.

When to use it
a client or a manager should receive a fresh capture each time a row or a form comes in.
Watch out
Email Address is required, so map it or type it before testing.
3

Take Website Element Screenshot (Advanced)

Action

In Zapier“Takes a custom screenshot of a website element and makes it available to Zapier so it can get passed to a following action (You need a Starter plan to create Zaps with 3 or more steps). This requires knowing the selector of the element.”

Same idea, narrower frame. Instead of the whole screen, it captures one element of the page that you point to with its selector, then passes that crop on to the next step.

When to use it
only the price box or the hero banner of a page matters to the person reading it.
Watch out
without the exact selector of the element, the step has nothing to aim at.
4

Take Website Element Screenshot and Send It via Email (Advanced)

Action

In Zapier“Takes a custom screenshot of a website element and sends it to an email address of your choice. e.g: john@example.com. This requires knowing the selector of the element.”

The most targeted option: one element of the page, cropped by its selector, then sent by email to the address you choose. Capture and delivery happen in a single action.

When to use it
someone needs a daily look at one block of a page, such as a stock indicator, without opening the site.
Watch out
URL, email and selector are all required here.
When it breaks

When a GetScreenshot Zap breaks

Zapier links no help article to this app, so the cases below come from its own fields and from Zapier's general rules.

Most failures aren't bugs. They come from a slow page, a field set the wrong way, or the source app behaving differently from what you expected.

  • Slow page, failed step

    Run synchronously, the capture may fail when it takes more than 30 seconds. Turn on the asynchronous callback option so the step completes once the result is posted back.
  • Only the top of the page

    Full Page Capture set to False keeps only the first part of the page. Set it to True when you need everything down to the footer.
  • PDF looks different

    The PDF option emulates printing from the browser, and the rendering can change in that mode. Check one PDF by eye before relying on it.
  • Old rows are ignored

    A Zap only reacts to what happens after you publish it. Pages already listed in your sheet or base won't be captured unless you move them separately.
  • The Zap feeds itself

    If a later step writes a new record into the very table the trigger watches, the Zap sets itself off again and again and burns tasks fast.
  • Bulk import held back

    Paste hundreds of URLs at once and the trigger may return a huge batch. Zapier's flood protection can hold it back instead of running every capture.
Need help

Need help automating GetScreenshot with Zapier?

A person reads every message.

FAQ

GetScreenshot Zapier integration FAQ

01Is the GetScreenshot Zapier integration free?
Yes, on the Zapier side it works on the free plan, because GetScreenshot is not a premium app. The free plan gives you 100 tasks a month and unlimited Zaps. The real limit is size: a free Zap has two steps, one trigger and one action. So a Zap that starts in another app and ends with Take Website Screenshot and Send It via Email fits. A Zap that captures the page and then posts it somewhere else is three steps and needs a paid plan. What GetScreenshot itself charges for its own account isn't covered here.
02How many tasks does a screenshot Zap use?
One task per GetScreenshot action that succeeds. The trigger in the other app is free, and so are the checks Zapier runs to find new items. If the capture fails, it isn't counted. In a Zap with several actions, each one that works is billed on its own: capture plus a Slack message equals two tasks per run, so the same monthly count covers half as many runs. With 100 tasks a month on the free plan, that's 100 emailed captures at most. Keep a filter before the capture so only the rows that matter spend tasks, bearing in mind the filter itself needs a paid plan.
03Does GetScreenshot capture pages in real time?
It depends on the trigger, since GetScreenshot has none of its own. The capture runs when the Zap reaches it, and the Zap starts when the other app's trigger fires. With an instant trigger, the app reports the event straight away whatever your plan. With a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Look for the lightning bolt in the editor to know which kind you picked. Then the capture itself takes time, and slow pages can need the asynchronous option.
04What do you need to connect GetScreenshot to Zapier?
An existing GetScreenshot account, and access to the Zapier Apps page. From there you click + Add connection, search GetScreenshot, click Add connection, sign in on the tab that opens and grant access. The connection is saved once and reused by every Zap. Before the first test, have the inputs ready: a Website URL for every action, an email address for the two email variants, and the element's selector for the two Advanced ones. The official field help says the URL must start with a specific prefix, so paste full addresses rather than bare domain names.
05Why does a GetScreenshot step time out?
Because by default it can run synchronously, and a capture that takes more than 30 seconds may fail in that mode. Heavy pages, full-height captures and PDF output are the usual suspects. Every action has a field called Avoid Zapier timeouts with asynchronous callback. When it's on, the step returns immediately and completes once the result is posted back to Zapier. Turn it on for long pages and test again. If the step still fails, try a capture limited to the top of the page to see whether page length is the cause.
06What if the GetScreenshot action you want isn't listed?
Then it doesn't exist in Zapier today. The app offers four actions and nothing else: no trigger, no search, no way to read past captures. A common workaround is to let another app carry the logic: a spreadsheet, a form or a CRM decides which URL to send, and a filter decides when. If you need something GetScreenshot can't do, such as noticing that a page changed, it has to come from another tool. The list on the GetScreenshot app page in Zapier is the full list, so check it before you plan a Zap around a missing step.
07Zapier, Make or n8n for GetScreenshot?
Judge by criteria, not by a ranking. On Zapier, check three things: the four actions cover your need, your Zap fits in two steps if you want to stay on the free plan, and your source app has the trigger you need, ideally an instant one. Then count tasks: each successful capture costs one, so volume drives your plan. Compare those points with what the other platform's own GetScreenshot page lists, operation by operation, rather than assuming parity. The deciding factor is usually where the rest of your automations already live.