The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →You can automate this with an integration: Zoho Forms sends a submission by webhook to Zoho Flow or a custom endpoint, which passes the submitted website URL to a screenshot API and then saves or delivers the returned image. Zoho documents these building blocks, but the available documentation does not establish a native Forms action that automatically screenshots a separate website URL. Treat this as an integration pattern to configure and test for your workflow—not a prebuilt connector or verified recipe.
How the workflow fits together
- Collect the target URL. Add or identify a Zoho Forms field for the website URL. Validate that it is a URL and decide whether submissions may target any domain or only approved domains.
- Send the submission. Configure a Zoho Forms outgoing webhook to POST selected submission data to Zoho Flow or an endpoint you operate. Zoho Forms lets administrators configure the payload content type, authorization, URL parameters and custom headers. Zoho Forms webhook documentation
- Request the screenshot. The receiving flow or endpoint reads the submitted URL and calls a screenshot API using credentials stored securely on the server side.
- Handle the returned file. Save the image to your chosen storage, attach it to an appropriate record if the platform supports the required file handling, or send a link to the intended recipient. Confirm binary handling in the actual integration; the documented webhook capabilities do not establish that Zoho Flow or a Forms field will persist arbitrary screenshot bytes.
- Define failure handling. Decide what happens when a URL is invalid, a page is blocked or slow, the API call times out, or the same submission is delivered again. Use a queue or asynchronous callback when rendering could outlast a synchronous execution window.
Choose a route: Zoho Flow or custom Deluge
Zoho Flow for low-code orchestration
Zoho Flow can receive a webhook request at a generated URL and make the received values available to later flow steps. Its webhook trigger documentation describes JSON, form data and plain-text payload formats. Configure the trigger to match the Forms webhook payload, send a sample request, and map the URL field and any needed submission identifier into subsequent steps. Zoho Flow webhook trigger documentation
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Building Expert Business Solutions with Zoho CRM: An indispensable guide to developing future-proof... | $29.89 | Buy on Amazon |
| 2 |
|
Zoho User Manual for Businesses | $25.99 | Buy on Amazon |
Before committing to this route, verify how your chosen Flow steps handle a binary image response and how the image will reach its final destination. Do not assume that a screenshot API response can be mapped directly into an attachment without testing the complete path.
Deluge or a custom endpoint for custom logic
Deluge’s invokeUrl task can make HTTP requests to third-party APIs. It is subject to Zoho service-call limits and a documented 40-second socket timeout, so check the current limits for your account and function before placing a potentially slow rendering operation in a synchronous path. Deluge invokeUrl documentation
#1 Best Overall
A small endpoint you control can be useful when you need explicit validation, secure secret storage, job queues, retry logic, or storage handling. Those are implementation choices, not features established for a particular Zoho configuration. For longer renders, consider acknowledging the webhook promptly and processing the screenshot asynchronously rather than making the form submission wait.
Configure the webhook payload carefully
Choose the content type based on the fields you need and inspect an actual sample submission. Zoho Forms documents different behavior for attachments and subform data by format:
| Payload format | Documented consideration |
|---|---|
| JSON | Can carry subform data. |
| application/json | Excludes file attachments. |
| Form-encoded | Excludes file attachments and subform data. |
| Multipart | Excludes subform data. |
These distinctions can affect a workflow that needs more than the URL, such as a submission identifier or uploaded supporting files. Confirm the current Zoho documentation and the payload received by your endpoint before relying on a particular format. Zoho Forms webhook documentation
- Pass only the fields required for capture and delivery.
- Validate the submitted URL and, if appropriate, restrict it to approved domains. This is your implementation policy, not a documented automatic Forms restriction.
- Keep screenshot API keys out of public pages, client-side code and exposed URLs. Use server-side secret storage or an appropriately secured connection.
- Decide how to handle URLs with sensitive query parameters, authenticated pages and redirects before sending them to a third-party renderer.
Pick a screenshot API and verify the response path
A hosted screenshot API accepts a page URL and returns an image or other capture output. ScreenshotOne documents HTTPS URL capture, API-key authentication and format-specific responses; its default response by format is binary. Its documentation says captures are not stored on its servers by default unless caching, storage or similar options are enabled. That is provider-specific behavior, not a privacy or retention guarantee for every configuration. Check current provider documentation, options and plan limits before implementation. ScreenshotOne documentation · Getting started
For an India-based organization, account for where submitted data and screenshots are processed and stored. The India OAuth callback documented for Zoho Connections is https://deluge.zoho.in/delugeauth/callback; it is an OAuth setup detail and does not establish Zoho or a screenshot vendor’s data residency. Verify location, retention and access requirements with each provider rather than inferring them from that URL. Zoho Connections documentation
Keep website screenshots distinct from Zoho’s submission PDF
Zoho Forms documents a feature that generates a PDF of a form submission. That PDF represents the submission; it is not a screenshot of the separate website URL a respondent entered. Use the webhook-and-rendering pattern when the goal is to capture that external page. Zoho Forms PDF and document help
Rank #2
Plan storage, retries and access before launch
The right destination depends on why you need the image: audit evidence, lead review, visual monitoring or customer delivery require different access and retention choices. Decide whether the image belongs in object storage, a record attachment, an email or a link. Confirm that the receiving system accepts the returned image bytes or a file URL, and set permissions and retention deliberately.
- Duplicate submissions: use a stable submission identifier as an idempotency key or storage key, so retries do not create uncontrolled duplicate files.
- Transient failures: define retry limits and backoff for network or provider errors, and record a useful status for later review.
- Slow or inaccessible pages: set a timeout strategy and decide whether to retry, mark the job failed or send it for manual review.
- Authenticated pages: confirm that the screenshot service can access the page through an approved mechanism. A submitted URL alone does not grant access.
- Sensitive URLs: avoid unnecessary logging of query strings and consider whether sending the full URL to a third-party API is acceptable.
- Quotas and cost: check Zoho account limits and the screenshot provider’s current plan limits against expected form volume, retries and capture behavior.
Test the complete submission-to-image path
Test in a non-production workflow where possible. These cases expose integration gaps that a successful sample URL will not:
- A valid public page, including one that redirects.
- An invalid URL and a URL outside any permitted-domain policy.
- A slow page, a blocked page and a page that fails to load.
- A large page or one with content that loads lazily.
- A repeated webhook delivery for the same form submission.
- A screenshot API error, timeout or malformed response.
- Final delivery: verify the image opens, is associated with the intended submission and has the intended access permissions.
Troubleshooting common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| The receiving flow has no URL value | The wrong field was selected, the payload format does not match the trigger, or the mapping is incorrect. | Inspect a real Forms webhook payload, confirm the Flow trigger format and remap the URL field. |
| Subform values or file attachments are missing | The selected payload format excludes that data. | Review Zoho’s format-specific behavior and choose a compatible format or a separate transfer path. |
| The screenshot request fails or returns an error | The URL may be invalid or inaccessible, credentials may be wrong, or the provider may reject the request. | Check the endpoint response and request configuration; validate the URL and keep credentials server-side. |
| The Zoho function times out | Rendering or downstream delivery exceeded the available synchronous window. | Account for Deluge’s documented 40-second socket timeout and consider queue-based or asynchronous processing. |
| The API response arrives, but no image is saved | The integration may not be handling binary data or may lack a configured destination action. | Test response bytes and destination handling independently, then verify the saved file against the original response. |
| Retries create duplicate images | The receiving workflow treats a repeated submission as a new job. | Use a submission identifier for idempotency and define duplicate behavior. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A GET request with a URL can return a PNG, JPEG, WebP or PDF. In your server-side endpoint, pass the validated submitted URL in place of the example target below; keep your access key private. See the ScreenshotNeo API documentation for request options and response handling.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpBefore capture, ScreenshotNeo can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. See ScreenshotNeo for product details and current plan information.
Sign up for 1,000 free screenshots a month, with no card required.
Frequently Asked Questions
Can Zoho Forms generate a PDF of the website URL someone submits?
Zoho Forms’ documented submission PDF is a PDF of the form submission, not a capture of the separate website. Capturing that page requires an integration that sends the URL to a screenshot service.
Does the India OAuth callback mean my screenshots are stored in India?
No. The callback URL is an OAuth setup detail; it does not establish the data location of Zoho or a screenshot provider.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
