Capture the webpage URL in Zoho Flow, then pass it to your screenshot provider with a Send Webhook action—or a Deluge custom function using invokeURL when you need custom request or response handling. Map the URL into the exact parameter or body field specified by that provider. Because no screenshot API vendor is specified here, its endpoint, authentication, required field names, and response format cannot be given as a universal copy-and-paste request.
Choose how Zoho Flow receives the webpage URL
Your flow needs a step that supplies the URL before it can request a screenshot. That value might come from an earlier app action or from an external system. If an external system starts the flow, Zoho’s webhook trigger can receive JSON, form data, or plain text. Configure the trigger for the format the sender actually transmits; Flow exposes the received values to later steps. Zoho’s webhook-trigger documentation explains the setup.
- Add the appropriate trigger in the Flow builder. For an incoming webhook, choose the payload format that matches the sender.
- Send a sample request if you use the webhook trigger, then inspect the received fields and identify the field containing the webpage URL.
- Confirm that the value is a complete URL, including its scheme, such as
https://example.com/page.
Send the URL with a Send Webhook action
For a straightforward HTTP request, add Zoho Flow’s Send Webhook action. Look up the screenshot API’s documentation before filling in the action: the provider determines the endpoint, HTTP method, URL field name, authentication, and whether the URL belongs in query parameters or the request body. Zoho’s action supports configurable request data, including headers, parameters, and body fields. See the Send Webhook action documentation and its request-field documentation.
- Set the endpoint and method exactly as required by the screenshot API.
- Map the Flow variable containing the webpage URL into the provider’s documented query parameter or body field. Do not assume the field is named
url. - Add the required authentication and headers, including the content type if the API requires one.
- Configure the action to handle the response in the way your next Flow step needs. The response might contain a URL, a file, or another representation; this depends on the provider.
Flow variables can be inserted into later action fields; use the variable picker to map the URL rather than typing a sample value that will remain fixed. Provider-specific encoding requirements also matter: follow the API documentation if the URL must be encoded or sent in a particular format.
#1 Best Overall
Use a Deluge custom function when the request needs logic
If the standard action cannot perform a needed transformation or response-handling step, use a custom function. Zoho documents Deluge’s invokeURL task for making HTTP/API calls, and custom-function outputs can be mapped into later flow steps. The exact Deluge request must follow the screenshot provider’s API contract; neither a method, endpoint, authentication header, nor parameter can safely be assumed without knowing the provider. See Zoho Flow custom functions and Deluge’s invokeURL task.
Choose between the webhook action and a custom function
| Route | When it may fit | What to check |
|---|---|---|
| Send Webhook action | The provider’s request can be expressed using Flow’s configurable request fields. | Required method and fields, authentication setup, and how easily you can test the request. |
Custom function with invokeURL |
You need custom Deluge logic or more control over request or response handling. | Transformation needs, authentication setup, code requirements, and mapping the function output to later actions. |
Zoho documents both routes but does not establish a performance or reliability winner between them. Choose based on the request behavior your provider requires and how you need to use its response.
Test the flow and check the result
- Run the flow with a known public webpage URL and inspect the incoming trigger fields if a webhook supplies the value.
- Test the outgoing call against the screenshot provider’s documented API contract. Check the HTTP response and any error details the provider returns.
- Confirm that the returned result is usable by the next Flow action. Depending on the API, it may be a result URL, file, or another data representation.
- Test the complete workflow again with the actual source that will provide URLs, so you catch differences in payload format or field mapping.
Zoho documents testing the incoming webhook setup; the screenshot API’s own documentation governs how to validate its outgoing response. Do not treat a successful Flow run alone as proof that a screenshot was captured correctly.
Troubleshoot common integration failures
- The URL field is missing: Check that the trigger’s selected format matches the sender’s JSON, form-data, or plain-text payload. Send a sample and inspect the fields Flow exposes.
- The API rejects the request: Verify the endpoint, method, required parameter or body field, authentication, and content type against the provider’s current documentation. A field name that looks plausible is not a substitute for the API contract.
- The provider receives a malformed URL: Check that the mapped value is the complete URL, and follow the provider’s guidance for query encoding or body formatting.
- The request succeeds but later steps cannot use the result: Inspect the response structure and map the actual returned property or file representation into the next action; response formats are provider-specific.
- The action cannot express the needed behavior: Consider a Deluge custom function with
invokeURLfor custom request construction or response handling, while retaining the same provider-specific endpoint and authentication requirements.
Or skip the browser setup
If you would rather call a screenshot API directly than assemble browser infrastructure, ScreenshotNeo accepts a webpage URL in one GET request. Its API can return a PNG, JPEG, WebP, or PDF. Cookie banners are accepted and removed before capture, along with supported newsletter popups and chat widgets; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents use screenshot tools, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. 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.webpTo use this from Zoho Flow, configure its outgoing webhook with the API endpoint, your access key, and the webpage URL as documented. Keep the access key private. Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Can I use Zoho Flow without knowing the screenshot API’s exact field names?
No. The provider’s API documentation must specify the endpoint, method, authentication, and field where the webpage URL belongs; Zoho Flow cannot determine those details for an unnamed API.
Does a successful webhook call guarantee that a screenshot was captured?
No. Check the screenshot provider’s response and confirm that the returned result can be used by the next step in your flow.
Quick Recap
Rank #4
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.
Recommended Free Tools
