How to Send Website Screenshots to a WhatsApp Business Number with Make in India
Build a Make workflow that captures a website and sends the screenshot through WhatsApp Business Cloud, with India setup notes, message rules, and troubleshooting.
To send website screenshots to a WhatsApp Business number with Make in India, create a scenario that captures a URL, then sends the resulting image through WhatsApp Business Cloud. Make lists a HTML/CSS to Image → Create a Screenshot of a URL action and a WhatsApp Business Cloud → Send a Message action. The exact output-to-media field mapping can vary with the current module interface, so inspect the capture output and add a media upload or HTTP step if the send module does not accept it directly.
This is a cloud workflow; no special hardware is needed. Before building it, connect an approved business sender and decide whether your first message requires an approved template. Make’s documentation says the business phone number must be approved by WhatsApp before sending, and free-form messages require that you previously sent a template to that specific customer and received a reply. Check Make’s current WhatsApp Business Cloud setup and module guidance before launch.
What you need
- A Make account and a scenario with the screenshot and WhatsApp Business Cloud modules.
- A Facebook account, Meta Business Suite account, and valid WhatsApp Business number. Make’s documented connection flow asks you to create a business portfolio and WhatsApp Business account before connecting.
- A recipient you are authorized to message, and an approved WhatsApp sender number.
- A website URL that the capture service can reach. For private or authenticated pages, confirm that the screenshot action supports the access method you need.
Make documents regular signup and a Coexistence signup path, but says Coexistence is not available in every country. The available documentation does not establish whether India is currently supported. Check the country availability in Meta’s live setup flow rather than assuming it will work. Connection screens and credential requirements can change; follow the current Make and Meta prompts.
Build the Make scenario
- Create a scenario. Choose a trigger that fits your workflow: for example, a scheduled run or an incoming record containing a page URL. Make sure each run has a valid URL and the intended WhatsApp recipient.
- Add the screenshot action. Add HTML/CSS to Image → Create a Screenshot of a URL. Map the URL from the trigger. Set any viewport or image options exposed by the live module. The integration listing confirms the screenshot action exists; it does not document every option or output field.
- Inspect the screenshot output. Run a controlled scenario and open the module output. Determine whether the result is a file/binary value, a downloadable URL, or another representation. Do not assume the WhatsApp module accepts it directly.
- Prepare media if needed. If WhatsApp’s media field cannot accept the capture output, add an HTTP download step when the capture result is a URL, then use the documented WhatsApp media-upload path or an HTTP API request to upload the image. Map the resulting media identifier or accepted media input into the send step. Make’s HTTP app documents making API requests and downloading files; consult its live field requirements.
- Add WhatsApp Business Cloud → Send a Message. Select the connected business account and sender, choose the appropriate message type, map the recipient, and attach the screenshot using the media field the current module exposes.
- Run a limited test. Use a page and recipient you control. Check the actual delivered image, crop and viewport, recipient, sender approval, and each module’s output before scheduling or processing more URLs.
This sequence is a workflow design based on the listed Make modules, not a verified field-by-field scenario blueprint. Make’s interface and accepted media mappings may change, so confirm them in the current scenario editor.
Choose the right WhatsApp message mode
For an automated first outbound contact, use a WhatsApp-approved template in the documented Make flow. Make says a non-template Send a Message can be used only after you have sent a template to that particular customer and the customer has replied. Do not configure the scenario as if it can freely send unsolicited messages to any number.
Keep the template appropriate to the message and recipient, and verify the current approval and delivery requirements in Meta’s setup. A successful Make operation alone may not establish that the recipient received the image; inspect the module result and WhatsApp delivery behavior.
Pick a screenshot capture route
| Route | When it fits | What to check |
|---|---|---|
| HTML/CSS to Image module | Start here for a direct Make scenario using the listed URL screenshot action. | Available capture controls, output type, and whether the result maps to WhatsApp media. |
| HTTP with a screenshot API | Useful when you want to call a screenshot endpoint that returns an image or downloadable result. | API credentials, response format, file download/upload mapping, and the combined service and Make operation cost. |
| GetScreenshot integration | An alternative named capture service listed by Make for page capture and monitoring. | Its current capture controls, output accessibility, regional availability, and pricing. The available research does not establish comparative speed, cost, or reliability. |
Compare options by setup effort, viewport or full-page controls actually offered, image format, output accessibility, need for another API account, failure handling, total costs, and availability in your region. Do not infer that one route is faster or more reliable without evidence.
Handle failures and edge cases
| Symptom | Likely cause | What to check or change |
|---|---|---|
| WhatsApp rejects the sender or connection | The business number has not been approved, or the connection setup is incomplete. | Review the current Make connection requirements and Meta business setup; confirm the sender approval before running the scenario. |
| The message is blocked or cannot be sent as free-form text | The recipient has not replied after a template message, or the initial outbound message is not using an approved template. | Use an approved template for initial contact. For a non-template message, follow Make’s documented template-and-reply condition for that same customer. |
| Image field is empty or the send step rejects the capture output | The screenshot module may return a URL, file, or another value the send module does not accept as-is. | Inspect the captured output. Add an HTTP download and the supported media-upload step, then map the upload result into the send action. |
| Screenshot is blank or incomplete | The page may load slowly, require interaction, block automated access, or depend on content outside the initial viewport. | Check the capture module’s available wait and page options, test the URL manually, and verify the output before sending it. |
| Wrong page or recipient receives the image | Trigger data was mapped to the wrong scenario fields or a prior test value was retained. | Inspect the resolved URL and recipient immediately before the send step. Test with controlled values and restrict scenario access. |
| Scenario reports success but recipient does not see the message | Module execution success may not prove delivery; billing or account requirements can also affect delivery. | Review WhatsApp’s current delivery status and Meta billing requirements. Do not treat a Make operation result as delivery confirmation. |
| Coexistence signup is unavailable | Make warns that Coexistence is not supported in every country; India availability is not established by the sources used here. | Check the live country options in Meta’s setup flow and use an available connection path. |
Performance, reliability, and cost
Each scenario run can involve a capture operation, possibly an HTTP download and media upload, and a WhatsApp send. Account for all modules when estimating Make usage and allow for retries without accidentally sending duplicate messages. Where the scenario supports error handling, separate capture failures from send failures and avoid retrying a send until you have checked whether the prior attempt delivered.
Image size and capture scope affect transfer time and media handling. Start with the smallest image and viewport that answer the recipient’s need, then confirm any size and format limits in the live capture and WhatsApp module documentation. The research material does not establish a numeric file limit or a benchmark for these routes, so verify current limits rather than hard-coding one.
Budget for Make operations, any separate screenshot service or API, and WhatsApp charges under the current Meta terms. Make’s documentation reports a service-message billing statement effective October 1, 2026: 1,000 free delivered service messages per month per business number, with additional delivery behavior tied to a payment method in Meta Billing Hub. This is a time-sensitive Make vendor statement, not independently verified here; check Meta’s live pricing and delivery terms before launch.
Or skip the browser setup
Use ScreenshotNeo when you want a screenshot API call instead of configuring browser capture. It is a website screenshot API and MCP server from ScreenshotNeo. The call below captures an example page; in Make, pass the returned image into the same media preparation and WhatsApp send steps described above. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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}`);ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Connect the returned image to your WhatsApp media step, then sign up free for 1,000 screenshots a month with no card.
Frequently asked questions
Can Make send a screenshot to a WhatsApp Business number in India?
The documented Make modules provide the building blocks. India-specific Coexistence availability is unsettled in the source material, so confirm the current Meta setup options for your account and country.
Does the screenshot action automatically attach its result to WhatsApp?
The source pages establish that the screenshot and WhatsApp actions exist, but do not validate direct field compatibility. Inspect the capture output and add download/upload steps if required by the current module UI.
Can I send the screenshot as the first message?
Make’s documented flow requires an approved template for initial outbound contact. Its non-template send action requires a template sent to that customer and a reply from them.
Can I use this for many URLs?
Use a trigger that provides one URL and recipient per item, and estimate operations and message charges for the expected volume. Test error and duplicate handling before enabling a high-volume schedule.
