How to capture a website screenshot from a new HubSpot deal with Zapier

To capture a website screenshot when a new HubSpot deal is created, make HubSpot → New Deal the Zap trigger, map a public website URL from the deal or a related record into a screenshot action, then send the returned image to a later Zap step. The exact property that contains the URL depends on your HubSpot setup, so inspect a sample trigger record in Zapier before mapping it.

This guide uses Zapier’s listed GetScreenshot → Take Website Screenshot action as the do-it-yourself example. Its required input is Website URL. You can also use another screenshot action if its controls and output fit your workflow.

1. Check that a new deal contains a usable website URL

A screenshot action needs an address it can open. Before building the Zap, identify where that address is stored:

It may be a property on the deal itself.
It may belong to an associated company or contact.
It may be in a custom property populated by your sales process.

The available integration information does not establish one universal HubSpot property name or association layout. In the Zap editor, load a representative New Deal sample and inspect the available fields. Confirm that the chosen value is a complete public URL, such as https://example.com, rather than a company name, domain fragment, internal record link, or blank value.

2. Create the HubSpot trigger

In Zapier, create a new Zap and select HubSpot as the trigger app.
Choose New Deal as the trigger event and connect the HubSpot account you want to monitor.
Use the editor’s test or sample-record option to load a representative deal.
Inspect the sample fields and locate the website URL. If it is on an associated record, check whether the trigger data exposes that value; otherwise, add an appropriate HubSpot lookup or association step before the screenshot action.

Zapier’s integration listing labels New Deal as an instant trigger. Treat that as the listing’s trigger classification, not a guarantee of a particular end-to-end delivery time.

3. Add and configure the screenshot action

Add an action and choose GetScreenshot → Take Website Screenshot.
Map the confirmed URL value into the action’s required Website URL field.
Choose capture options exposed by the action. The listing describes Full Page Capture, Width, PDF output, and an additional wait setting. These are available controls, not universal recommendations: use the settings that match the page and what the next step accepts.
Test the action with a representative URL. Check that the resulting output is the expected image or PDF and is available to map into a later action.

A full-page capture can suit a page where content below the fold matters. A width setting can help when a consistent viewport is needed. A wait setting may help pages that render content after the initial response. The listing does not establish exact behavior or best values for every website, so validate the output with your own target pages.

4. Send the screenshot to the next Zap step

Add the action that should consume the captured file, such as the storage, notification, or record-update step your workflow requires. Select the screenshot output from the previous action’s data when mapping the file or attachment input.

Check the receiving action’s expected input. Some actions accept a file or file URL, while others expect a link or a different representation. The integration listing says the screenshot output is made available to following Zap steps, but the exact field name and downstream mapping depend on the action you choose.

5. Test the complete flow and turn it on

Use a test deal with a known public URL and representative page content.
Run the Zap through the trigger, screenshot, and destination actions.
Open the output from the destination and check that it shows the intended site, at the expected size and format.
Confirm how the Zap behaves when the URL is missing, malformed, or points to a page that cannot be reached. Add a filter or error-handling path if those cases need separate treatment.
Review the step mappings once more, then turn on the Zap.

This sequence is setup guidance; the integration listings document available triggers, actions, and fields, not a tested end-to-end workflow or the schema of each HubSpot account.

Choosing a screenshot action

Choose based on the output and capture controls your workflow needs. Zapier’s listings also include PagePixels Screenshots, ScreenshotOne, and HTML to Image alongside HubSpot. The listed controls vary:

Action listing	Controls or behavior described in the listing	Check before choosing
ScreenshotNeo	One GET request can return PNG, JPEG, WebP, or PDF; the API supports full-page capture, element capture, waits, and other controls.	Use the API call below or the ScreenshotNeo documentation to map the URL and output for your Zap workflow.
GetScreenshot	Website URL, full-page capture, width, PDF output, and an additional wait setting.	Verify its current availability in Zapier, output mapping, and any plan requirements.
PagePixels Screenshots	Page width and height, full-page capture, selector, wait, format, and quality.	Check whether its selector and output options match the target page and receiving step.
ScreenshotOne	A website screenshot action and an animated or scrolling screenshot action.	Confirm which action and output type you need.
HTML to Image	URL-to-image capture with full-page and wait settings.	Check whether the output and available controls meet the workflow requirements.

These listings establish the described actions and fields, not which service produces the best result for a particular site. Compare full-page versus selected-element capture, wait and selector controls, output format, scrolling or animated capture, and whether the next Zap step can accept the returned output.

Or skip the browser setup

Instead of configuring a browser capture service, call ScreenshotNeo from a Zapier step that can make an HTTP request, then map its response into a later step. One GET request takes the target URL and returns an image or PDF. For endpoint parameters and response details, see the ScreenshotNeo API documentation.

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

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

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

Cookie and consent banners, newsletter popups, and chat widgets are removed before the capture; each cleanup step can be turned off.
Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Response headers say which page verdict occurred and whether the request was billed.
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.

Troubleshooting

Symptom	Likely cause	What to do
The screenshot step has no URL or receives an empty value.	The URL is not stored on the deal, the sample record lacks it, or it belongs to an associated record not included in the trigger data.	Inspect another representative trigger sample. Map the correct deal property or add a lookup step for the associated record. Add a filter for missing URLs if needed.
The screenshot shows an error page or the wrong website.	The mapped field may be a company name, partial domain, internal CRM link, or incorrect property.	Check the exact mapped value and use a complete public URL with the correct scheme and hostname.
The capture is blank or missing content.	The page may not have finished rendering, the URL may be inaccessible to the capture service, or a required page state may not be available.	Test the URL directly, adjust the available wait option, and confirm the page does not require a login or interactive state the action cannot provide.
The screenshot is clipped or too small.	The selected capture mode or width does not match the page.	Try full-page capture where appropriate and adjust width. Recheck the result rather than assuming one setting fits all pages.
The destination step cannot attach or open the output.	The destination may expect a different file field or a link rather than the screenshot action’s returned value.	Inspect the screenshot action’s output fields and the destination’s required input, then remap or add a step that accepts the available representation.
The Zap cannot be created with the chosen number of steps.	The GetScreenshot listing says a Starter plan is needed for Zaps with three or more steps; plan details can change.	Check Zapier’s current plan requirements and integration listing before publishing or changing the workflow.

Reliability, performance, and cost notes

URL quality: Validate that the value is present and public before capture. This prevents avoidable failures caused by missing or malformed CRM data.
Page variability: Dynamic pages may need a wait setting, while very long pages can produce larger outputs. Choose full-page capture only when the extra page content is useful to the next step.
Workflow checks: Test a normal page and the failure cases important to your process. Decide what should happen when capture fails or returns an unusable file.
Zapier plan: The reviewed GetScreenshot listing says a Starter plan is required for Zaps with three or more steps. This is a changeable plan detail; verify it before relying on it.
ScreenshotNeo pricing: Free includes 1,000 shots per month with no card; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free. Only clean shots are billed, and cache hits are not billed.

FAQ

Can the Zap screenshot a page on a new deal’s associated company?

Yes, if the URL is available to the workflow. Check the New Deal sample and, if needed, add a step to retrieve the associated company’s URL before the screenshot action.

Does the screenshot action capture a private HubSpot deal page?

The action needs a website URL to capture. A CRM record link is not automatically the public website URL you intend to screenshot; map the target page address instead.

Can the screenshot be saved or shared automatically?

Yes. Add a downstream Zap action and map the screenshot output in the form that action accepts.

Can I return a PDF instead of an image?

The GetScreenshot listing describes PDF output, and ScreenshotNeo supports PDF responses. Confirm the selected action’s current output fields and the next step’s accepted file type.