How to Capture a Website Screenshot from a Tally Form Submission with Zapier

To capture a website screenshot when someone submits a Tally form, create a Zap with Tally’s New Submission trigger, then add ScreenshotOne’s Take Website Screenshot action and map the submitted website URL to its required Website URL field. Add a storage or notification step if you need to keep or send the result. Test the complete workflow with a sample submission before publishing it.

This is a documentation-based setup path; the exact output fields you see depend on the connected action and account. Check the live Zap editor and test result before mapping the screenshot to another step.

1. Prepare the Tally form and website URL

The screenshot step needs the address of the page to capture. The simplest option is to add a URL question to the Tally form and require a complete address such as https://example.com/page. Use a question label that makes the expected input clear.

If the form is embedded on the website being captured, you may be able to pass the page URL and query parameters into Tally and store them in hidden fields. Tally documents this for supported embed setups. Verify the embed type and test that the hidden field contains the intended page address before using it in the Zap.

Publish the form and make sure the URL field (or eligible hidden field) is included in a submission.
Submit a sample response with a URL you control.
Check the response record and confirm the URL is complete and points to the page you want captured.

Tally’s submission payload can also include a form-response PDF and preview URLs. Those represent the submitted form response; they are not screenshots of an arbitrary website URL supplied by the respondent.

2. Create the Zap and map the screenshot action

In Zapier, create a Zap and choose Tally as the trigger app.
Select New Submission as the trigger event, connect the Tally account, and choose the correct form.
Test the trigger and select a sample record that contains the website URL.
Add ScreenshotOne as the next action and choose Take Website Screenshot.
Connect the account, then map the Tally URL answer into the required Website URL input.
Choose only the capture options your use case needs. The listed action includes controls such as image format, response type, viewport dimensions, full-page capture, delay, and timeout.
Test the action. Inspect its actual output in the connected account before mapping it into a later step.

For a page that extends below the fold, consider full-page capture. For a page that renders slowly, a delay or a different timeout may help; these settings cannot guarantee that every destination site will render successfully. Choose a viewport that matches how the captured page should appear.

3. Store or send the resulting screenshot

A screenshot action and a durable destination are separate parts of the workflow. If you need to keep a copy or notify someone, add the relevant storage or messaging action after the screenshot step. Use the output shown by your live test—such as the field or file reference the action actually returns—to configure that next step.

Do not assume the action always returns the same kind of value or that an image link has a particular retention period. The directory listing establishes the action and its inputs, but not a universal output field or file-retention policy. Confirm the output and destination behavior in your account.

4. Test before publishing

Submit a new sample response through the published Tally form.
In Zapier’s run history, confirm the trigger fired and the expected URL reached the screenshot action.
Open or retrieve the action result using the output it actually returned. Check the page, viewport, full-page behavior, and timing.
If you added storage or notification, verify that the intended image or reference arrived at the destination.
Publish the Zap only after the trigger, screenshot, and any follow-up action have passed their tests.

Tally’s guide describes testing the trigger and actions before publishing. Tally says its direct Zapier integration is available free to Tally users; check the current editor and your account for any changes.

5. Alternative: send submission data to a webhook

Use a custom webhook/API route if the direct screenshot action is unavailable in your account or you need more control over request handling and asynchronous output. This route has more moving parts, so build it against the current documentation for each service rather than copying unverified authentication or parameter examples.

Configure a Tally webhook to POST submission data as JSON to an HTTPS endpoint you control or to a supported Zapier webhook URL.
Parse the submission’s fields collection and identify the field containing the target website URL.
Use a Zapier webhook/API request or your own endpoint to call the screenshot service’s documented API, passing the target URL and the required authentication.
Handle the screenshot response according to the configured response mode. If using an asynchronous callback, provide an endpoint that can receive the result and then store or forward it.
Test the whole route with a controlled sample submission, including error handling and the final file destination.

Tally requires a webhook endpoint to return a successful 2xx response within 10 seconds. If delivery fails, its documented retry schedule begins after 5 minutes, then 30 minutes, 1 hour, 6 hours, and 1 day. These are Tally webhook delivery rules; they do not describe the timing of Tally’s direct Zapier trigger.

Zapier’s Webhooks by Zapier help lists GET, POST, PUT, and Custom Request methods. Its documentation updated August 10, 2026 says sending webhooks in Zaps is unavailable on Free and available on Professional, Team, and Enterprise. Check current plan access in your account before choosing this route. This webhook plan constraint is separate from Tally’s direct Zapier integration.

ScreenshotOne documents screenshot API options and asynchronous delivery to a webhook. Confirm its current authentication, request parameters, response format, and output destination in its documentation before implementing a custom request.

Configuration choices and edge cases

Decision	What to check
Where the URL comes from	Use an explicit Tally URL answer, or a supported embed-origin value saved to a hidden field. Test that the field exists in the trigger sample.
Capture dimensions	Set a viewport appropriate to the intended screenshot. A different viewport can change responsive layouts and content.
Full-page capture	Enable it when content below the viewport matters. Pages with lazy-loaded content may need additional time or scrolling behavior supported by the selected action.
Delay and timeout	Adjust for the destination’s loading behavior, then test. A longer wait can increase workflow duration and does not fix blocked or failed pages.
Output handling	Inspect the live test result, then map the returned output into the storage or notification step. Do not infer a permanent public URL.
Webhook versus direct action	Use the direct action for the simplest documented path. Choose a webhook/API route when its added control justifies implementation and plan requirements.

Keep API credentials and private webhook URLs out of public form code and article examples. If respondents can supply arbitrary URLs, validate that the value is a well-formed HTTP(S) URL and decide which destinations your workflow is allowed to request.

Common problems and fixes

Symptom	Likely cause	What to do
The Zap trigger has no useful URL value	The sample submission omitted the URL, or the wrong form/field was selected.	Submit a fresh test response with the target field filled in, reload trigger samples, and map the correct answer.
The URL is blank for an embedded form	The embed does not forward the page address, or the hidden field is not configured for that embed.	Check Tally’s supported embed setup, pass the needed page value, and verify it appears in a real submission.
The screenshot is of the wrong page	The mapped field contains a form preview, a different answer, or an unexpected query-string value.	Inspect the exact URL in the screenshot action input and distinguish the submitted site URL from Tally’s response PDF/preview links.
The page looks incomplete	The page needs more render time, full-page mode, or a different viewport.	Try the relevant delay, timeout, full-page, or viewport setting and test again with a page you control.
The screenshot step succeeds but nothing is saved	No destination step was added, or the next step mapped the wrong output field.	Inspect the screenshot action’s test output, then configure a storage or messaging action using that actual output.
Webhook action is unavailable	The Zapier plan may not include Webhooks by Zapier, or the current editor/package differs.	Check the current plan and app availability. The direct Tally trigger plus screenshot action is a separate path.
A Tally webhook is retried	The endpoint did not return a successful 2xx response within the documented 10-second window.	Return success promptly, move lengthy screenshot work to background processing, and use the documented retry behavior to account for repeated deliveries.

Performance, reliability, and cost

The main factors affecting completion time are the destination page’s load behavior, the selected delay and timeout, screenshot rendering, and any storage or messaging steps. Full-page captures may involve more page content than a viewport capture. Test representative pages rather than assuming one setting works for every submitted URL.

For reliability, inspect Zap run history, confirm the URL passed between steps, and test the final destination. A webhook endpoint should acknowledge Tally promptly and perform slow capture work asynchronously when needed. Design custom webhook handling to account for retries so a repeated delivery does not accidentally create confusing duplicate records or notifications.

Costs can involve separate services and plans. Tally describes its direct Zapier integration as free to Tally users, while Zapier’s Webhooks by Zapier availability is plan-dependent per its current help documentation. Check the plan and pricing shown in the accounts you use; this workflow guide does not establish the current price of ScreenshotOne or guarantee a particular screenshot volume.

Or skip the browser setup

ScreenshotNeo can capture a submitted website URL with one GET request. Its cookie/consent handling removes supported banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, and cache hits are not billed, and responses say the page verdict and billing status in headers. It also has an MCP server so AI agents can take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

See the ScreenshotNeo API documentation for request options. cURL example:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

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)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Replace the example URL with the URL from the Tally submission and supply your API key securely in your integration. Sign up free for 1,000 screenshots a month, with no card required.

FAQ

Does a Tally submission PDF show the submitted website?

No. The PDF or preview is a representation of the form response. To capture a website, pass that website’s URL to a screenshot action.

Can I capture the page where an embedded Tally form appeared?

Potentially. Tally documents forwarding page URLs and query parameters to hidden fields for supported embed setups. Confirm your embed supports the configuration and test the resulting field value.

Do I need a custom webhook for the basic workflow?

No. The documented direct route is a Tally New Submission trigger followed by ScreenshotOne’s Take Website Screenshot action. A webhook/API path is an alternative when you need additional control.

Should I publish immediately after the action test passes?

First verify a real sample submission, the screenshot result, and any storage or notification step. Then publish the Zap.