Resources · Make integration

SCRNIFY.com Make integrationAutomate SCRNIFY.com with Make.

Need a screenshot of a web page every time a new link shows up in your tools? The SCRNIFY.com Make integration gives you 2 action modules, one for captures and one for any other API request. This guide shows who it suits, how to connect it and how to build your first scenario.

Try the SCRNIFY.com integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SCRNIFY.com Make integration do for you?

The SCRNIFY.com Make integration lets a Make scenario, the automation you build in Make, ask SCRNIFY.com for a screenshot of a web page and hand the result to the next step. You pick the page, Make sends the request, and no code is involved at any point.

A visual record of the pages you publish. When a marketer adds a landing page address to a tracking sheet, the Capture Website Screenshot module grabs the page and the next module stores it where the team looks. Nobody has to open a browser and press a shortcut.

Proof for a client report. An agency can pair a form or CRM trigger with the same module, so every URL a client submits comes back as a picture attached to the right record.

Anything the listed module leaves out. The Make an API Call module reaches any endpoint of the SCRNIFY.com API with the same connection, which is the way to cover requests that have no dedicated module.

Be aware of one real limit: the official Make documentation for SCRNIFY.com is thin, and Make itself says there is not enough public information to describe the app in detail. Test each field with Run once before relying on it. The Make troubleshooting guide helps when a run fails, and the Make review gives the wider picture of the platform. SCRNIFY.com may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect SCRNIFY.com to Make?

  1. 01

    Add a SCRNIFY.com module

    In your scenario, add either SCRNIFY.com module and click Create a connection. A connection is your SCRNIFY.com account linked to Make once, then reused by both modules of the app. You only do it once.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the project or client it belongs to. This step is optional, yet it saves guesswork once several accounts sit side by side in Make.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the SCRNIFY.com page, or paste the key SCRNIFY.com gives you. Then click Save, and the module is ready for its fields.

First scenario

Build your first scenario with SCRNIFY.com

GoalWhen a new web address appears in another app, Make asks SCRNIFY.com for a screenshot of that page.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. It will be the app where your links live, since SCRNIFY.com has no trigger of its own.

  2. 02

    Pick the source of URLs

    Choose a module of that other app, for example one that watches new rows of a sheet, and connect its account. Each new row will travel through the scenario as one bundle, a single item passed along.

  3. 03

    Add the capture

    Click the + on the right of that module, search for SCRNIFY.com and pick Capture Website Screenshot. Connect your account, then map the web address from the previous module into the field that expects it.

  4. 04

    Test with Run once

    Click Run once and add a test row. Open the bubble above each module to read the bundles it received, and check that SCRNIFY.com sent back what you expected before going further.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default and never shorter on the Free plan, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the SCRNIFY.com modules do

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

SCRNIFY.com1

Capture Website Screenshot

ActionIn the docs only

As its name says, this module asks SCRNIFY.com for a picture of a web page; Make gives no description, so read the result it returns before the next module stores, attaches or sends it.

When to use it
a new link lands in a sheet, a form or a CRM record, and you want a visual copy of the page without opening it yourself.
Watch out
Make lists no fields for it, so test it with Run once and a real URL first.
SCRNIFY.com2

Make an API Call

ActionIn the docs only

With this module you send your own request to any endpoint of the SCRNIFY.com API, reusing the connection you already created, so no second login is needed.

When to use it
the capture module does not expose an option you need, and the SCRNIFY.com API documentation shows an endpoint that does.
Watch out
you write the path and the body yourself here, so a typo only shows up at run time; test it with Run once first.
Need help

Need help automating SCRNIFY.com with Make?

A person reads every message.

FAQ

SCRNIFY.com and Make: common questions

01Is the SCRNIFY.com Make integration free?
Yes, on the Make side. SCRNIFY.com is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, runs no closer than 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. What SCRNIFY.com charges for its own service is a separate matter that this page does not cover.
02What do you need to connect SCRNIFY.com to Make?
All it takes is a SCRNIFY.com account and a Make account, nothing more. The Make documentation lists no special prerequisite and no official connection steps for this app, so you follow the generic flow: add a module, click Create a connection, optionally name it, then approve Make on the SCRNIFY.com page or paste the key the app provides, and save. The same connection then serves both modules, so you only go through these steps once.
03Can SCRNIFY.com trigger a Make scenario in real time?
No, because SCRNIFY.com has no trigger module in Make. The scenario has to start elsewhere: on a trigger from another app that holds your links, such as a sheet or a form, or on the schedule you set on the first module, every 15 minutes by default. If that other app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, the capture follows right away.
04What if the SCRNIFY.com module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SCRNIFY.com API with the connection you already have, so you are not limited to the screenshot module. Keep in mind that Make itself flags its SCRNIFY.com documentation as limited, because too little public information exists about the app. Check the SCRNIFY.com API reference for the exact request, then test it with Run once before switching the scenario on. Each call counts as one operation.
05Should you use Make or n8n for SCRNIFY.com?
It depends on the tool your team already works in. Many apps also have an n8n node, so check whether SCRNIFY.com does before deciding. In Make you get 2 modules, including Make an API Call for anything the capture module does not cover, and a visual editor where you test each step with Run once. Compare the two platforms on the workflows you already run rather than on this single app.
Same platform

Other docs you might need on this stack.

Browse all integrations