PagePixels
Start free

Make integration

Take website screenshots inside your Make scenarios.

Drop the PagePixels app into a scenario and any module chain can capture a page, act on it first, turn an email or a record into an image, and have AI read the result before it moves on. On every plan, including the free one.

  • Instant and multi-step captures inside any scenario.
  • Send images to thousands of Make apps, Google Drive and Telegram included.
  • Turn an Outlook email or another module's data into an image.
  • Have AI analyse the capture and pass the answer down the chain.
Get 25 free screenshots Read the Make guide

25 free screenshots / month · no credit card · no phone number

Scenario · 4 modules
  1. Trigger Watch new emails Outlook
  2. Module Custom HTML Screenshot PagePixels
  3. Module Upload the image Google Drive
  4. Module Send the file Telegram
An email arrives, becomes an image, and lands in Drive and Telegram. Module two is the only one that touches us.
01 / How it works

How to take a screenshot in Make in four steps

If you have built a scenario before, this is the part you can skim. The app behaves like any other module in the builder.

  1. Create a free account

    Sign up for PagePixels first, because the Make app connects to an account. Every feature is on the free plan.

    25 screenshots / mo

  2. Add the PagePixels app

    In the scenario builder, search for PagePixels Screenshots, drop in the module you want, and connect your account when prompted.

    search: PagePixels

  3. Choose the module

    A live URL, a multi-step capture for pages that need a login or a click, or Custom HTML Screenshot to render data from an earlier module.

    url · multi-step · html

  4. Map the output onward

    The module returns the image as a file. Route it into Google Drive, Telegram, Discord, an email, a database row, or anything else in the scenario.

    output → next module

Field-by-field screens are in the Make guide, and there are worked scenarios for Telegram, Discord, and AI analysis if you would rather copy a working one.

02 / What the modules do

Four modules, and only one of them starts with a URL.

The plain case is a live page. Past that, a capture can work for its subject: log in, dismiss the banner, click into the right tab, wait for the element, then shoot.

The Custom HTML module is the one that changes what a scenario can do. An Outlook email, a bundle from an earlier module, or a record from your database becomes a picture, which is how something unreadable in a notification becomes something a person takes in at a glance.

And because AI analysis is available as part of the capture, the scenario can branch on what the page says, not just on the fact that a file arrived.

  • A live page

    url

    Give the module a URL and the size you want, and it returns the capture for the rest of the scenario to use.

    url → image

  • A page that needs work first

    multi-step

    Log in, dismiss the consent wall, click into a tab, wait for an element, then capture. All inside the same module.

    login · click · wait → image

  • An email or a record

    custom html

    Render an Outlook message, a spreadsheet row, or another module's bundle into an image instead of passing along a wall of text.

    html → image

  • A capture the scenario can read

    ai analysis

    Ask a question of the capture and get a written answer back with it, so a later module can branch on what the page actually said.

    image → answer → route
03 / Where the image goes

Once the module returns it, the rest of the scenario treats it as a file.

Thousands of Make apps, with worked examples for Google Drive, Telegram, and Discord.

What you pass on Detail
The image png · jpeg · webp · pdf
The capture itself, full page or one selector, ready to upload, attach, or post from the next module.
A permanent link embed url
Always resolves to the latest capture of that config, with no API key in the URL, so it is safe to paste into a message or a doc.
The archive copy kept here
Every capture is filed in the archive and listable through the API, whatever the scenario does with its copy.
The AI answer written answer
The analysis text travels with the image, so a router or filter module can act on it.
Rendered HTML html
Optionally the fully rendered markup, for a module that needs to parse rather than look.

Worth knowing before you build: scheduling, change detection, and delivery to Slack, Dropbox, or a webhook are built in here, so a scenario is not required to make captures recur. Use Make when the capture has to start from another app, or land somewhere we do not integrate with directly.

04 / Before the shutter

A scenario that captures a login screen hourly is worse than no scenario.

The pages worth automating are usually gated: a dashboard behind a login, a report you have to generate, a consent wall in the way. Most screenshot modules accept a URL and nothing else, so they return the wrong screen reliably and forever.

Multi-step screenshots are part of the Make app, not a web-app-only feature. Fill the fields, submit, wait for the element, then capture, all in the one module.

Captures can also run through a Real Location in 150+ countries, states, and cities, so a geo-gated page reaches your scenario the way a local customer sees it.

One module, in order
  1. Open the login page url
  2. Fill email and password text_field ×2
  3. Click submit click
  4. Wait for the dashboard wait_for_selector
  5. Capture the page png · full page
  6. Return the file to the scenario module output
The same step list the web app, the API, Zapier, n8n, and Power Automate use.
05 / What teams build

Four scenarios worth ten minutes

Each is a trigger module, one PagePixels module, and a destination you already use.

  • Outlook → PagePixels → Drive

    Emails you can actually file

    Render each incoming invoice or report email as an image and file it in Drive, so the record is a picture of what arrived rather than a thread.

    custom html · on new email
  • Schedule → PagePixels → Telegram

    The daily page, in the group chat

    The scenario runs on its own schedule, captures the page, and sends the image to the Telegram group that needs to see it, following the worked tutorial.

    scheduled scenario · Telegram
  • Sheets → PagePixels → Discord

    A queue of pages to check

    Work through a list of URLs from a spreadsheet, capture each one, and post the batch into a Discord channel for review.

    iterator · Discord
  • PagePixels → AI → router

    Let the scenario decide

    Capture a page, ask the AI whether anything material changed, and route on the answer instead of pinging a human on every run.

    ai analysis · router
06 / What you get

The Make app is not a lite version.

This list is the same on the free plan and the largest one, and the same through the app, the API, and the web app.

Capture

5 INCLUDED
  • Multi-step capture Log in, click, fill forms, and wait for elements before the shutter fires.
  • Scheduled screenshots Recurring captures from every five minutes to once a year.
  • Real Locations Capture through a proxy network in 150+ countries, US states, and cities.
  • Ad, tracker, and banner removal Strip cookie consent walls, ads, and third-party scripts before capture.
  • CSS and JS injection Restyle or manipulate the page before the capture is taken.

Understand

4 INCLUDED
  • AI analysis Ask a question of any capture and get a written answer back with the image.
  • Custom HTML screenshots Render email, private spreadsheet rows, or API payloads into an image.
  • HTML extraction Pull fully rendered HTML from JavaScript-built pages, whole page or one selector.
  • Website domain research Extract structured fields across a list of domains, as JSON or CSV.

Watch

3 INCLUDED
  • Change notifications Watch a selector and get a webhook, Slack message, or Zap when it moves.
  • Archived history Every capture is kept and listable through the API, with dated thumbnails.
  • CDN embed URLs A permanent link that always shows the latest capture, no API key exposed.

Deliver

3 INCLUDED
  • Every integration Zapier, Make, n8n, Power Automate, Slack, Dropbox, webhooks, Chrome, and MCP.
  • Full REST API Every option is a parameter, with NPM, PyPI, and RubyGem packages.
  • Custom headers and cookies Send your own headers, cookies, user agent, language, and time zone.
07 / Common questions

Screenshots in Make, answered.

How do I take a screenshot in Make.com?

Create a free PagePixels account, add the PagePixels Screenshots app to your scenario, connect the account when prompted, and pick the module: a live URL, a multi-step capture, or Custom HTML Screenshot. The module returns the image as a file that any later module can upload, attach, or post.

Is this the same as the old Integromat app?

It is the same platform under its current name. Make was Integromat, and the PagePixels Screenshots app works in the current builder. If you are following an older Integromat tutorial, the module names in the Make guide are the ones to trust.

Is the Make app included on the free plan?

Yes. The Make app, and every other integration, is on every plan including the free one. There are no connector tiers and no per-destination fees. The free plan is 25 screenshots a month with no credit card and no phone number.

Can a scenario screenshot an email?

Yes, and it is one of the most used cases here. The Custom HTML Screenshot module renders the message body into an image, so an Outlook or Gmail email becomes something you can file in Drive, post to a channel, or attach to a record.

Can Make capture a page behind a login?

Yes. Multi-step actions run inside the module: fill the fields, submit, wait for the element to appear, then capture. The same thirteen action types the web app and the API use are available, so a gated dashboard reaches the scenario as the real page.

Do I need Make to schedule recurring screenshots?

No. Scheduling from every five minutes to once a year, change detection, and delivery to Slack, Dropbox, or a webhook are built in, so captures can recur with no scenario running. Use Make when the capture has to start from another app, when the image needs to reach an app we do not integrate with, or when the flow needs branching logic around it.

Other destinations

Make is one of ten. The same capture can go anywhere on this list.

Point it at a page. Walk away.

25 free screenshots every month. No credit card, no phone number.
Take a screenshot