To capture a screenshot after a Webflow form succeeds, route the submission to a webhook or connected automation, then capture the confirmation page. If the confirmation appears only inside the submitting browser’s session, keep the form submission and screenshot in the same browser automation session and wait for the success state first. A URL screenshot request captures a page; it does not submit the form.
Choose the capture method that matches the success state
| What the visitor sees after submitting | Best-fitting method | Key requirement |
|---|---|---|
| A separate, publicly accessible thank-you page | Webflow submission event plus a URL screenshot API | Capture only after the redirect page has finished loading. |
| An inline success message or personalized/session-specific page | Playwright or another persistent browser automation session | Submit or observe the submission, wait for success in that same session, then capture. |
| A low-code workflow | Webflow connected app, Zapier, or Make plus an HTTP-capable action or custom endpoint | Confirm the workflow includes a way to call the screenshot service; a built-in screenshot action is not established for every connector. |
Configure Webflow to emit a submission event
In Webflow’s form settings, configure the form’s success and error states, and choose where submissions go: Webflow, a webhook, connected apps, or a custom action. Give the form a descriptive name so you can identify it in settings and integrations. Webflow says, “You can use webhooks to send form submissions automatically to external services.” See Webflow’s form submission documentation for current setup details.
As an Amazon Associate I earn from qualifying purchases.
For a webhook workflow, configure the endpoint that will receive the event and securely store the webhook secret. Webflow shows that secret only once during setup; use it to authenticate or validate incoming messages as Webflow documents. Your receiving service should trigger the screenshot step only when it has received the relevant successful submission event.
Recommended Free Tools
Be deliberate about custom actions: Webflow says a custom action bypasses Webflow’s form processing and cannot be combined with Webflow or email destinations under the documented settings. Submissions sent this way will not be stored or processed by Webflow’s built-in handling.
#1 Best Overall
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Method 1: Capture a separate thank-you page from its URL
Use this route when a successful submission redirects to a stable receipt page that the screenshot service can access. Set the redirect in Webflow, then have the webhook receiver or connected automation request a screenshot of that page after the submission event. The screenshot endpoint receives a URL and returns an image; it does not perform the form submission.
- In Webflow, set the form’s success behavior to redirect to the thank-you page.
- Configure a Webflow webhook or connected-app trigger for that form’s submission.
- In the receiving workflow, wait until the thank-you page is reachable and ready, then call a URL screenshot API with that page URL.
- Store or deliver the resulting image where your workflow requires, with appropriate access controls.
Browserless documents a POST screenshot endpoint that accepts a URL and options and returns an image, including full-page or viewport capture and wait conditions. It is suited to a reachable receipt page that does not depend on the submitter’s session. Choose the exact URL and wait condition for your site; documentation: Browserless screenshot API.
Avoid triggering capture merely because the webhook arrived if the destination page still needs time to render. Prefer a page-ready condition or a specific visible element over an arbitrary short delay when the page is dynamic.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Method 2: Capture an inline or session-specific success state with Playwright
If the success message appears inline, requires authentication, or depends on state held in the submitting browser, use an interactive browser flow. Keep navigation, form submission, success detection, and screenshot capture in one browser context. The following Playwright example is a template: replace the URL, selectors, and input values with those for your form. It captures the page after the success message becomes visible.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
import { chromium } from 'playwright';
const browser = await chromium.launch();
const page = await browser.newPage();
try {
await page.goto('https://example.com/contact', { waitUntil: 'domcontentloaded' });
await page.locator('input[name="name"]').fill('Test User');
await page.locator('input[name="email"]').fill('[email protected]');
await page.locator('textarea[name="message"]').fill('Screenshot workflow test');
await page.locator('form button[type="submit"]').click();
// Replace this selector with the success message or receipt element on your page.
await page.locator('.w-form-done').waitFor({ state: 'visible', timeout: 15000 });
await page.screenshot({ path: 'after-submit.png', fullPage: true });
} finally {
await browser.close();
}Install Playwright and its browser before running the script; the selectors in the sample are illustrative and must match the published form’s actual markup. If another system performs the submission, automate or attach to the browser context that owns the resulting session instead of making a separate URL-only request. Playwright’s documentation covers page interaction and screenshots: screenshots and installation and setup.
Browserless also documents persistent browser interaction options. Its REST API overview states that its one-request APIs do not click a button, fill a form, and scrape the result in one request, and that session state is discarded after each response. Use a browser automation route when the task depends on multiple actions or session continuity; see Browserless API overview.
Method 3: Route submissions with Zapier or Make
Webflow documents connected apps and integrations as submission destinations. A no-code workflow can receive the event and then call an HTTP-capable action or your own endpoint to perform the capture. Do not assume a connector includes a screenshot step: verify that the particular workflow can make the required API request.
Zapier setup
- Create at least one real or test submission for the form; Zapier’s documented trigger setup needs a submission to test successfully.
- In Zapier, choose Webflow as the trigger app and “Form submission” as the event.
- Select the site and form, test the trigger, configure an action that can call your screenshot workflow, and publish the Zap.
See Webflow’s form submission documentation and Zapier’s Webflow setup guide.
Rank #3
- WINDOWS 11 | STABLE PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 system, this laptop delivers stable performance for everyday computing tasks. It supports web browsing, online learning, document editing, email communication, and basic office work with optimized power efficiency, providing a practical and reliable experience for essential daily use for daily use.
- 15.6” FHD IPS DISPLAY: Features a 15.6-inch Full HD IPS display with narrow bezels, offering wider viewing angles and clearer image details compared to standard panels. The improved screen-to-body ratio enhances visual experience for study, reading, document work, and video playback, making it suitable for both productivity and entertainment use.
- 4GB DDR4 + 128GB eMMC STORAGE: Equipped with 4GB DDR4 memory and 128GB eMMC storage for everyday basics such as browsing, documents, email, and online learning platforms. The built-in TF card slot supports storage expansion up to 1TB, giving you more flexibility for files, photos, videos, and daily documents. TF card not included.
- CONNECTIVITY & PORTS: Includes 1× TF card slot, 2× USB 3.2 Gen1 ports, and 2× full-featured Type-C ports (USB 3.2 Gen1). The Type-C ports support data transfer, charging, and video output, enabling flexible connection with external devices such as monitors, storage, and peripherals for daily work and study use.
- LIGHTWEIGHT DESIGN | ONLINE COMMUNICATION: Designed with a slim, portable profile, this laptop is easy to carry for school, commuting, and travel. A built-in 1MP front camera supports online classes, video meetings, remote communication, and everyday conferencing. The 3300mAh battery works with the low-power system design to support practical daily use, while thermal optimization helps maintain quieter operation during extended tasks.
Make setup
Use Webflow’s documented Make connection to route submission data to an appropriate scenario, then add an HTTP/API-capable step or endpoint for screenshot capture. The precise modules and availability depend on the workflow you configure; the Webflow connection alone should not be treated as proof that a screenshot action is included. See Webflow’s form submission documentation and Webflow’s Make integration article.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For a public or otherwise accessible thank-you URL, ScreenshotNeo can capture the page with one GET request. This URL-based request does not submit the form or preserve a visitor’s session, so use browser automation for inline or session-specific states.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/thank-you -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo is a website screenshot API and MCP server: it removes cookie/consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed; and its MCP server lets AI agents take screenshots. It includes 1,000 shots per month free with no card, while paid plans start at $5 for 3,000 shots. Learn more at ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Privacy, hosting, and workflow safeguards
- Keep personal data out of URLs. A URL may be recorded in logs or exposed to systems beyond the form. Do not place submitted names, emails, or other personal details in query strings.
- Review third-party data handling. A screenshot can create another copy of a personalized confirmation page. Limit access and check how the automation and screenshot provider handle page content. Webflow advises users routing form data through third parties to review their data-controller responsibilities and seek consent where required; this is operational guidance, not legal advice. See Webflow’s privacy information.
- Know the hosting boundary. Webflow says it will not process form submissions if the site is exported for external hosting. Use a third-party collection service or embedded third-party form in that case. See Webflow’s form submission documentation.
- Validate the event and capture result. Authenticate webhook messages with the configured secret, and inspect the screenshot response or workflow result before treating the capture as complete.
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| The automation never receives a submission | The webhook or connected-app trigger is not configured for the selected form, or the site is externally hosted. | Confirm the form destination and endpoint; if exported, Webflow will not process submissions. |
| Zapier’s trigger test finds no record | No submission exists for Zapier to test against yet. | Submit the form once, then retest and select the right site and form. |
| The custom-action form is absent from Webflow’s submission handling | Custom actions bypass Webflow’s built-in processing. | Receive and store the submission in the custom destination; do not expect Webflow or email destinations to process it alongside the custom action. |
| The screenshot shows the form instead of success | The capture ran before redirect or rendering finished, or the desired state exists only in the original session. | For a public receipt URL, wait for a page-ready condition. For inline/session-specific success, use one interactive browser session and wait for the success selector. |
| The image is missing personalized or authenticated content | A separate URL request does not have the visitor’s browser session or authentication context. | Use browser automation with the appropriate session, and apply access and data-handling controls. |
| Webhook validation fails | The secret may not match, may not have been saved, or message validation is incorrect. | Use the secret captured during setup and follow Webflow’s documented validation instructions; the secret is shown only once during setup. |
Frequently asked questions
Can a screenshot API submit a Webflow form for me?
No. A URL screenshot endpoint renders an accessible page and returns an image; form submission requires a separate event or browser interaction workflow.
Can I capture the visitor’s exact browser state after submission?
Yes, if the browser session that performed or observed the submission remains available to your automation. A separate URL-only capture cannot be assumed to inherit that session.
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.
