How to Archive a Webpage Screenshot to Google Drive on a Schedule with Make

Use a Make scenario to capture the webpage, pass the resulting image file data to Google Drive, and set the scenario’s schedule. Make publishes a template for a related workflow: it reads URLs from Google Sheets, takes screenshots after pages finish loading, uploads them to Google Drive, and writes image links back to the sheet. Treat the template as a starting point and verify its current modules and connection requirements in your Make account.

The key detail is the handoff: Google Drive’s upload action needs a destination folder and file data, so confirm that your capture step produces file data the upload step can use. A temporary image URL alone may require an additional download step before Drive can upload the image.

1. Decide what to capture and how often

For one page, use a fixed URL in the scenario. For a collection of pages, a Google Sheet can hold the URL list and a column for the resulting Drive links. Make’s published template demonstrates that URL-list → screenshot → Drive upload flow, including writing image links back to the sheet. Its description says screenshots are taken once pages are fully loaded, but it does not specify a particular wait setting or guarantee behavior for dynamically rendered pages. Check the results for your own targets.

Choose the cadence based on what you need to preserve: for example, a daily capture for a daily record or a weekly capture for a less frequent archive. These are workflow choices, not Make recommendations. Make documents regular intervals, once, daily, weekdays, weekly, monthly, specified dates, and on-demand schedule options. The documented default is every 15 minutes, while the minimum interval depends on your plan; check the schedule choices available to your account before relying on a particular frequency. Make scheduling documentation

2. Build the capture and upload scenario

Create a scenario in Make’s Scenario Builder.
Add a source for the URL. Use a fixed URL for a single page, or use Google Sheets if you want to process a list. For a sheet-based workflow, include the target URL and a field where the scenario can write the resulting image link.
Add a screenshot capture action. Make’s template lists Google Sheets, Cloudmersive, and Google Drive among its apps. Check the currently available capture action and its requirements in Make; the template’s public description does not specify a capture endpoint, connection setup, or provider pricing.
Inspect the capture output. Identify whether it provides the image as file data or only as a URL. If it returns only a URL, determine whether your scenario needs a step to retrieve the image file before uploading it.
Add Google Drive’s Upload a File action. Choose the destination folder and map both the screenshot data and a filename. Drive’s module documentation describes the destination and file fields, including filename and data. Google Drive module documentation
Use a filename that distinguishes captures. For example, combine a short site label with the capture date and time, such as example-com-2026-10-04-0900.png. This is a practical naming convention; choose a format that fits your archive and avoids collisions.
If using a sheet, record the output link. Map the Drive result into the relevant row so you can find the archived file from the URL list. Confirm which Drive link field is returned by the modules you selected.
Run the scenario once manually. Check that the screenshot is legible, the capture output reaches the upload action, the file lands in the intended folder, and the filename is as expected.

Make’s screenshot-to-Drive template is a useful reference for the multi-URL version. Its description says it pulls URLs from a Google Sheet and takes screenshots once they are fully loaded. Confirm that the template’s current modules and setup still match your account before using it as-is.

3. Configure and activate the schedule

Scheduling is configured on the Make scenario, separately from the capture and upload actions. Open the scenario’s schedule settings, choose the cadence or date pattern you need, and activate the scenario. Available documented choices include regular intervals, once, daily, weekdays, weekly, monthly, specified dates, and on-demand runs. The minimum regular interval depends on your plan, so verify it in the account rather than assuming a cadence. Make’s schedule options

After activation, check a later run in the scenario history and confirm that it created a new file. For a sheet-driven scenario, also check that the intended row was processed and its link was written back.

Choosing a capture action

The official template establishes the overall workflow, but the reviewed documentation does not establish provider-by-provider capture behavior or limits. Before choosing a capture action, compare these points in its current Make listing and documentation:

Output type: Does it return binary file data that Drive can upload, or a temporary URL that needs to be downloaded?
Rendering: Does it capture the viewport or the full page? How does it handle pages that add content after initial load?
Requirements: Does it need a separate account, API key, or paid plan?
Limits: Check documented file-size and execution limits that apply to the capture and upload steps.
Schedule: Confirm that your Make plan supports the cadence you need.

Do not assume that a module supports a particular rendering option, limit, or wait behavior unless its current documentation says so. Test representative target pages and review each step’s output.

Google Drive folders and access

Choose a folder that the connected Google account can upload to. If you are using a Google Shared Drive, the module documentation describes those options for Google Workspace users; make sure the intended account has access to the chosen folder. Google Drive module documentation

Keep the output location consistent if you want captures to be easy to browse. For a multi-page archive, use filenames that identify both the page and capture time, and retain a sheet or other index of URLs and Drive links if that is useful for your workflow.

Reliability, performance, and cost considerations

Dynamic pages: A page can look loaded while client-side content is still changing. The template’s “fully loaded” description does not define a universal rendering or wait guarantee. Check the captured output for your actual pages and adjust the capture action if it exposes suitable wait controls.
Multiple URLs: A URL list makes the workflow easier to maintain, but each capture and upload must complete for its row. Run a small representative set first and inspect scenario history before relying on a larger archive.
Run frequency: Make documents several schedule types, but the minimum interval depends on plan. Pick an available cadence and verify the scenario is active.
File size and execution limits: The cited template and module pages do not establish universal limits for every capture provider or plan. Check current module and account documentation for limits that apply to your workflow.
Costs: The reviewed sources do not establish the current cost of the capture module, Make usage, or Google Drive storage for your account. Check each provider’s current plan and usage terms; do not infer a total from the template alone.
Failure visibility: Inspect scenario history after the initial run and after schedule changes. Confirm both the uploaded file and any sheet link, since a successful capture does not by itself prove that the Drive upload or sheet update completed.

Troubleshooting

Symptom	Likely cause	What to check or fix
Drive upload fails because data is missing	The capture step returned a URL or metadata rather than file data, or the wrong output field was mapped.	Inspect the capture output. Map the image data field, or add the appropriate retrieval step if the capture action returns a URL.
The file is uploaded but cannot be identified	The filename is blank, generic, or reused for every run.	Map an informative filename containing the page label and capture date or time.
The screenshot is blank or incomplete	The target may need more time to render, or the capture action may not handle its loading behavior as expected.	Review the captured page and the action’s documented wait or rendering options. Test the actual target page; the template does not promise a specific dynamic-content wait behavior.
The file does not appear in the intended folder	The destination folder mapping may be wrong, or the connected account may lack upload access.	Check the selected folder and connection. For a Shared Drive, confirm the Google Workspace account has access.
The scenario does not run at the expected time	The scenario may not be activated, the schedule may differ from the intended setting, or the requested interval may not be available on the plan.	Review the scenario schedule and activation state, then confirm the cadence available to your plan.
A sheet row has no image link	The Drive upload or subsequent sheet update may not have completed, or the wrong output field was mapped.	Inspect the run history step by step. Confirm the Drive result contains the link field you mapped and that the update targets the intended row.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Make can call its screenshot endpoint, then pass the returned image file data to Google Drive’s Upload a File action. Map the target URL and access key in the HTTP request, then map the response file data and a filename into Drive. See the ScreenshotNeo API documentation for request details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers identify the page verdict and billing status.
An MCP server lets AI agents use screenshot, page-info, and PDF-capture tools.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000 screenshots.

FAQ

Can I archive more than one webpage per run?

Yes. A sheet can hold a list of URLs, as in Make’s published template. Verify that your chosen capture action and plan can handle the number of URLs you intend to process.

How often can a Make scenario run?

Make documents regular intervals, daily, weekdays, weekly, monthly, specified dates, once, and on-demand options. The minimum interval depends on the plan, so check the options available to your account. Scheduling documentation

Does the template guarantee screenshots of dynamically loaded content?

No such guarantee is documented in the reviewed template description. It says screenshots are taken once pages are fully loaded, but does not define a wait setting or dynamic-rendering behavior. Test the pages you need to archive.

Can I upload to a Google Shared Drive?

The Drive module documentation includes Shared Drive options for Google Workspace users. Confirm that the account connected to Make can upload to the selected Shared Drive folder. Drive module documentation