How to automate website screenshots from Zoho Forms with Pabbly Connect

Direct answer: Add a website URL field to your Zoho Form, trigger a Pabbly Connect workflow when the form is submitted, map that field into Pabbly’s HTML to Image screenshot action, then add a downstream step if you want to store or send the result. Zoho Forms can POST selected submission fields to a webhook, and Pabbly lists both a Zoho Forms “New Form Submitted” trigger and a website screenshot action. The vendor listings confirm these building blocks, but do not document a complete, tested recipe for every account configuration.

What you need

A Zoho Form that includes a field for the website URL.
A Pabbly Connect workflow with a Zoho Forms submission trigger or a webhook trigger.
A screenshot action, such as “Capture Website Screenshot” in Pabbly’s HTML to Image integration.
An optional downstream action for the result, if you need to notify someone or store the image.

Ask respondents for a complete URL, including its scheme, such as https://example.com. This is implementation advice; the vendor listings do not prescribe a particular validation rule. A submitted URL also does not guarantee that the destination is publicly reachable or accessible to the screenshot service.

Set up the Zoho Forms to Pabbly workflow

Add the URL field. In Zoho Forms, add a clearly labeled field such as “Website URL to capture.” Decide whether it should be required. If your form builder supports validation, guide respondents to enter a complete URL.
Create a Pabbly Connect workflow. Choose the Zoho Forms “New Form Submitted” trigger if it is available in your account. Alternatively, choose a webhook trigger and copy the webhook URL Pabbly provides.
Connect Zoho Forms. For the direct webhook approach, open Integrations under Developer & Automation, choose Webhooks, and configure the Pabbly webhook URL. Zoho’s webhook setup uses HTTP POST and lets you set content type, authorization, payload parameters, URL parameters, and custom headers. See Zoho Forms’ webhook configuration guide.
Include the URL in the payload. Add a payload parameter and map it to the website URL form field. The parameter name is the key that the receiving workflow can use to identify the field.
Choose a content type. Zoho documents application/json, application/x-www-form-urlencoded, and multipart/form-data. Select the format your Pabbly trigger accepts. Zoho notes that JSON excludes file attachments, URL-encoded data excludes form attachments and subform data, and multipart data excludes subform data. The reviewed documentation does not definitively map every format to Pabbly’s behavior.
Capture a sample submission. Submit the form with a URL and inspect the trigger data in Pabbly. Confirm the field is present and note its exact name before mapping it. This is a setup check, not a claim that a particular account has been tested.
Add the screenshot action. Add the HTML to Image action named “Capture Website Screenshot,” then map the URL value received from Zoho into its URL input. Pabbly also lists a “Get Screenshot from URL” action in another HTML/CSS to Image integration. The listings do not establish that the two actions have identical inputs, limits, or result handling.
Configure the result destination. Add a suitable downstream Pabbly action if you need to store, forward, or notify someone about the image. The reviewed integration listings do not specify a universal result-file handoff or a required destination, so check the fields exposed in your own account.
Enable and monitor the workflow. Turn it on, submit a real form entry, and inspect the submitted URL, screenshot action output, and destination output. Confirm the workflow behaves as intended before relying on it.

Choose a trigger approach

Approach	How it works	When it fits
Pabbly Zoho Forms trigger	Select “New Form Submitted” and connect the form account in Pabbly.	Use this when the trigger exposes the fields your screenshot step needs.
Zoho Forms webhook to Pabbly	Configure Zoho to POST selected submission data to a Pabbly webhook URL.	Use this when you want to control payload fields, request format, authorization, or headers.

The official listings confirm both options but do not provide a full feature-by-feature comparison. In either case, the essential requirement is that the submitted URL arrives in the workflow and is mapped to the screenshot action.

URL and payload details to check

Complete URL: Include https:// where appropriate. A bare domain may not be accepted by a downstream action.
Field mapping: Confirm the captured sample shows the intended field, especially if the form has similarly named fields or nested data.
Payload format: Match the Zoho content type to the Pabbly trigger’s supported input. Attachments and subform data have format-specific exclusions described above.
Authentication and headers: Zoho offers authorization and custom header settings. Use these only when required by the receiving endpoint; do not put secrets into a respondent-facing URL field.
Payment forms: If the form collects payment, Zoho warns that payment status and submission can be asynchronous. Account for that timing if the screenshot should happen only after payment is complete. This does not usually affect a basic non-payment form.
Private or restricted destinations: The integration listings describe screenshot capture from a URL but do not define authenticated-page access behavior. Verify access requirements with the screenshot provider and your account configuration.

Troubleshooting

Symptom	Likely cause	What to check
Pabbly receives no trigger event	The webhook URL or trigger connection is incorrect, or the workflow is not listening.	Recheck the selected trigger, the webhook URL configured in Zoho, and whether the workflow is enabled for capture. Send a fresh sample submission.
The URL field is missing from trigger data	The field was not included as a Zoho payload parameter, or the trigger sample predates the field.	Add the URL field to the payload mapping and capture a new sample.
The screenshot action receives an empty value	The wrong trigger field was mapped, or its key differs from the expected field.	Inspect the sample payload and remap the exact URL value into the screenshot action’s URL input.
The action rejects the URL or captures the wrong page	The response may contain an incomplete URL, whitespace, or a different field’s value.	Submit a complete URL, inspect the captured trigger value, and confirm the action input points to that field.
The workflow runs but no usable image reaches the next step	The action output may not be connected to the downstream step in the format that step expects.	Inspect the screenshot action’s output fields in your Pabbly account and map the available result into the destination action.
A protected page cannot be captured	The destination may require a login or block automated access.	Check the destination’s accessibility and the screenshot provider’s documented access options. The researched listings do not establish authenticated-page support.
Attachments or subform values are absent	The chosen content type excludes that kind of data according to Zoho’s webhook documentation.	Review Zoho’s content-type limitations and choose a format compatible with the receiving trigger and the fields required.

Performance, reliability, and cost

Each submission adds a trigger event and a screenshot action, plus any downstream steps. The reviewed sources do not establish processing-time guarantees, retry behavior, service limits, screenshot pricing, or a specific delivery format for this combination. Check current plan details and action outputs in your Zoho and Pabbly accounts before estimating volume or depending on the flow for time-sensitive work.

For reliability, verify the field mapping with a sample, monitor actual runs, and decide how your team will handle failed or inaccessible URLs. If payment status matters, account for Zoho’s note that payment and submission can be asynchronous. Avoid assuming that a successful form submission means the screenshot or its downstream delivery also succeeded.

Or skip the browser setup

If you want a direct screenshot API call instead of configuring the screenshot step in Pabbly, ScreenshotNeo accepts a URL and returns an image or PDF. You can send the URL received from the form to the API from a workflow step that supports an HTTP request. See the ScreenshotNeo API documentation.

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, failed loads, timeouts, and cache hits are not billed. Response headers report the page verdict and billing status.
An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients.
The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is available on every plan.

FAQ

Does the form need to be submitted by a human?

The documented workflow starts with a new form submission. The sources do not specify restrictions on how submissions are created, so check the behavior and policies of your Zoho form and connected services for your use case.

Can I capture a URL that a respondent submits?

The URL can be mapped into the screenshot action, but the listings do not guarantee that every destination is reachable or capturable. Verify private, restricted, or blocked pages with the provider.

Which Pabbly screenshot action should I select?

Pabbly lists “Capture Website Screenshot” in HTML to Image and “Get Screenshot from URL” in another integration. Choose the action available in your account and inspect its inputs and outputs before configuring downstream steps.

Does the workflow require a physical device?

No physical product is required by the hosted-software workflow described here.