Send Webpage Screenshots to WhatsApp: Make in India Guide

This guide shows you how to automatically capture a screenshot of any webpage and send it to a WhatsApp contact or group using the Make (formerly Integromat) platform, with a special focus on using the ‘Make in India’ data residency option. By the end, you’ll have an automated workflow that triggers on a schedule or an event, takes a clean screenshot, and delivers it straight to your WhatsApp chat—no manual copying or pasting.

What You’ll Need

A Make account (free or paid plan). If you’re in India, you can choose the ‘Make in India’ data center during signup for data residency.
A WhatsApp account (personal or WhatsApp Business) that you can link via the WhatsApp integration in Make.
A URL of the webpage you want to screenshot. It must be publicly accessible (no login walls).
Basic familiarity with Make’s interface (scenarios, modules, and connections).

Step-by-Step

Log in to Make and create a new scenario. Go to make.com, sign in, and click “Create a new scenario.” If you haven’t set up your Make in India account yet, do that first—choose the India data center when prompted.
Add the first module: a trigger. For a scheduled screenshot, use the “Schedule” app with the “Cron” trigger. Set it to run at your desired frequency (e.g., every hour). Alternatively, use a webhook if you want to trigger manually or from another app.
Add a module to capture the screenshot. Make doesn’t have a built-in screenshot module, so you’ll use an external service. Search for “Screenshot” in the module list. Popular options include “URL2PNG” or “Screenshot One.” For this guide, we’ll use URL2PNG. Add its “Create a screenshot” module. Connect your URL2PNG account (you’ll need an API key from their site).
Configure the screenshot module. In the “URL” field, enter the webpage URL you want to capture. You can hardcode it or use a variable from the trigger (if you’re using a webhook). Set the “Width” to 1280 and “Height” to 800 (or any size you prefer). Choose “Full page” if you want the entire page, or “Viewport” for just the visible area. Leave other options as default.
Add the WhatsApp module. Click the plus sign after the screenshot module and search for “WhatsApp.” Choose the “Send a Message” action. You’ll need to connect your WhatsApp account. Click “Add” next to the Connection field, then scan the QR code with your WhatsApp app (WhatsApp Web method). For WhatsApp Business, you’ll use the API, which requires a Meta developer account—this is more complex, so for personal use, the QR method is simpler.
Set up the WhatsApp message. In the “Send to” field, select a contact or group. You can type a phone number with country code (e.g., 919876543210 for India) or choose from your contacts. In the “Message Text” field, type something like “Here’s the latest screenshot:”. Then, in the “Attachments” field, click “Add” and select the “File” output from the screenshot module. Make will automatically attach the image file.
Test the scenario. Click the “Run once” button at the bottom left. Make will execute the scenario. Check your WhatsApp to see if you received the screenshot. If not, check the error message in Make.
Activate the scenario. Once the test succeeds, toggle the “Inactive” switch at the bottom to “Active.” Your scenario will now run automatically based on the schedule you set.

Common Mistakes

Using a login-protected URL: If the webpage requires a login, the screenshot service will capture a login page instead. Use public URLs or consider using a headless browser service that can handle sessions (more complex).
Incorrect WhatsApp number format: Always include the country code without a plus sign or spaces. For India, it’s 91 followed by the 10-digit number.
Forgetting to attach the file: In the WhatsApp module, if you don’t add the file from the screenshot module, you’ll send a text-only message. Double-check the attachment field.
Using the wrong trigger: If you use a webhook trigger, you need to manually send a request to the webhook URL to test. Many users expect it to run on its own—make sure you understand your trigger.
Not enabling the scenario: After testing, you must toggle the scenario to “Active.” Otherwise, it won’t run on schedule.

Tips

Use a delay: If the webpage loads slowly, add a “Sleep” module (from the Tools app) between the screenshot and WhatsApp modules to ensure the image is fully generated. Set it to 5-10 seconds.
Customize the screenshot: URL2PNG allows you to set a custom width, height, and even a delay before capture. If the page has dynamic content, set a delay of 2000-5000 ms in the screenshot module’s “Delay” field.
Send to multiple recipients: You can add multiple WhatsApp modules to send the same screenshot to several contacts, but be mindful of rate limits.
Use a filter: If you’re triggering via webhook, add a filter to only send when a certain condition is met (e.g., a query parameter like ?send=1). This prevents accidental sends.
Monitor errors: Make has a built-in error handler. Add a “Watch Errors” module to send yourself an email if something goes wrong, so you know when to check.

Troubleshooting

Scenario runs but no WhatsApp message arrives. Check the WhatsApp module’s output. If it shows an error like “Invalid number,” verify the phone number format. Also, ensure your WhatsApp is connected and has an active internet connection. Sometimes, WhatsApp Web sessions expire—reconnect by editing the connection.

Screenshot is blank or shows a loading spinner. The webpage might be too slow or use JavaScript that renders after the capture. Increase the “Delay” in the screenshot module to 5000 ms. If it’s still blank, try a different screenshot service like Screenshot One, which has a “Wait for full load” option.

Module error: “File not found.” This happens when the screenshot module fails to generate a file. Check the screenshot service’s response—it might have an error message (e.g., invalid URL). Also, ensure you’re using the correct output field (usually “File” or “Link”).

WhatsApp sends the screenshot but it’s low quality. Increase the “Width” and “Height” in the screenshot module. Also, check if the screenshot service compresses images—some have a “Quality” parameter.

Scenario stops after a few runs. Make has a monthly operation limit. If you exceed it, the scenario will pause. Check your usage in the dashboard. Also, WhatsApp may rate-limit you if you send too many messages—space out your schedule.

Frequently Asked Questions

Can I use this with WhatsApp Business API?

Yes, but you’ll need to set up a Meta Business account and use the WhatsApp Business API integration in Make. The setup is more involved (requires a verified business, phone number, and API keys). The QR method works only for personal WhatsApp.

Is there a way to send the screenshot as a PDF instead?

Yes, some screenshot services (like Screenshot One) offer a PDF output format. In the screenshot module, change the “Format” to “PDF” and then attach that file in WhatsApp.

Can I schedule it for only weekdays?

Yes, in the Cron trigger, you can set the “Days of the week” field to 1-5 (Monday to Friday). The exact syntax depends on the cron expression—use a cron builder to help.

What if I want to send a screenshot of a page that requires login?

You’ll need a headless browser service like Browserless or Puppeteer that can handle sessions. This is more advanced—you’d create a custom API endpoint that logs in and takes a screenshot, then call that via a webhook in Make.

Does the Make in India plan affect the WhatsApp integration?

No, the data center location only affects where your scenario data is stored. The WhatsApp integration works the same, but the connection might be slightly slower if you’re in India and using a US-based WhatsApp server, but it’s negligible.

Can I get the screenshot to include a custom text overlay?

Not directly with the standard screenshot modules. You’d need to use an image editing module (like Cloudinary) to add text, then send that edited image. That adds complexity but is possible.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →