How to Use PDFShift with Zapier to Save Webpages as PDFs

To save webpages as PDFs with PDFShift and Zapier, have a Zap trigger provide a page URL, send that URL to PDFShift’s PDF conversion endpoint with your API key, then pass the resulting PDF or its delivery reference to a storage or email step. PDFShift documents URL-to-PDF conversion and lists Zapier among its automation connections. The available Zapier action, authentication fields, and exact response mapping depend on the current Zapier setup; verify those in your account before building around a specific field name.

This guide explains the documented workflow and a direct API request you can run independently. It does not assume that a particular native PDFShift action or arbitrary API request route is currently available in every Zapier account.

1. Understand the workflow

The automation has three parts:

Trigger: an event in a supported app supplies the webpage URL, such as a form submission or a new record.
Convert: an HTTP/API step sends the URL as the source to PDFShift, authenticating with an API key.
Deliver: a later step stores, emails, or otherwise routes the resulting PDF using the fields the conversion step actually returns.

PDFShift describes automation connections using this general pattern: connect a tool through its REST API and API key, configure the source and options, then receive a PDF through a download, URL, cloud storage, or webhook. The exact response and Zapier field mapping should be checked against the live integration. PDFShift’s automation overview

2. Check which Zapier path is available

Before assembling the Zap, search Zapier’s current app and action picker for PDFShift. If a PDFShift action is offered, inspect its inputs and output fields, and use the documented fields shown in your account. The available research confirms that PDFShift lists Zapier as an automation connection, but does not establish the current names or layout of a native Zapier action.

If there is no suitable PDFShift action, check whether Zapier’s API Request action supports the required request in your account. Zapier describes API Request as a beta feature for HTTP requests to supported public apps and says it requires HTTP/API knowledge. Its help page does not establish that PDFShift is supported for this action, so confirm that before relying on it. Zapier API Request documentation

Zapier also lists a separate app called PDF Export, with a “Convert HTML to PDF” action that accepts a URL or HTML. The listing does not identify that service as PDFShift. Choose it only if you want that listed app; do not treat it as a PDFShift integration.

3. Prepare the PDFShift request

PDFShift documents a POST request to its v3 conversion endpoint. The source can be a URL, and the request uses an X-API-Key header. The product page includes an example and supports URL or HTML sources. PDFShift API and product page

Get an API key from your PDFShift account.
Keep the key in Zapier’s secret or connection handling fields when the chosen path provides them. Do not put it in a public webpage, shared document, or a URL that may be logged.
Use the page URL as the request source. Confirm the exact request body encoding expected by the Zapier action you select.
Plan the next Zap step only after checking what the conversion action returns: a PDF file, a download reference, or another delivery mechanism.

PDFShift says unauthenticated calls can produce watermarked output and identifies X-API-Key as the current authentication header. PDFShift authentication and watermark help

4. Build and verify the Zap

Choose a trigger. Select the app event that contains the webpage URL. Test the trigger and confirm the URL is present and complete.
Add the PDFShift conversion step. Use the native action if it is currently available and suitable. Otherwise, use an API request route only if Zapier confirms that PDFShift is supported and the request can be configured with the documented method, endpoint, key, and source.
Map the URL. Pass the trigger’s URL into PDFShift as the source. Check for whitespace, missing scheme such as https://, or accidental mapping to a title or record ID.
Set authentication privately. Configure X-API-Key using the secret or connection controls available for that action. Never expose the secret in a public client-side script.
Test with a public page. Confirm the conversion succeeds and inspect the resulting PDF for page size, content, and completeness.
Add delivery. Map the actual output from the conversion step into the storage, email, or other destination action. If the step returns a temporary URL or file object, verify its availability and expected field type with the destination app.
Turn on the Zap and monitor runs. Check early runs for failed conversions, missing files, or incorrect URL mappings.

Zapier’s connection settings can vary by app and authentication method; follow the fields presented by the live action rather than assuming every integration accepts credentials the same way. Zapier app connection help

5. Run a direct API request

When configuring an HTTP-capable step, use PDFShift’s current API documentation for the precise payload and response format. This minimal cURL example demonstrates the documented method, endpoint, source, and authentication header. The output file path is local to your machine; it is not a Zapier file-mapping recipe.

curl -X POST "https://api.pdfshift.io/v3/convert/pdf" \
  -H "X-API-Key: YOUR_PDFSHIFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source":"https://example.com"}' \
  --output webpage.pdf

Use an accessible URL in place of https://example.com. Consult the PDFShift API page for supported options and current request details. Do not assume this cURL command’s binary response handling maps directly to a Zapier action; inspect that action’s output and configure the destination accordingly.

6. Options, limits, and edge cases

Pages the converter can reach

A URL conversion requires the conversion service to reach and render the page. A public URL is the simplest starting point. The reviewed sources do not establish how private, authenticated, paywalled, robots-restricted, or JavaScript-heavy pages behave in this Zapier workflow. Test the actual pages you need and avoid promising that every site will convert successfully.

Large PDFs and credit use

PDFShift’s FAQ says its free tier includes 50 monthly credits and one credit covers up to 5 MB of generated PDF output; larger output consumes additional credits. These prices and allowances can change, so confirm the current terms before estimating a production workflow. PDFShift FAQ and credit accounting

File delivery and retention

Do not assume a returned file URL is permanent, that a destination accepts it as a file, or that a binary response is automatically carried between Zapier steps. Verify the response fields and destination’s accepted input. If a download link is involved, test whether the receiving step can fetch it when the Zap runs.

Secrets and access

An API key is a credential. Restrict access to the Zap and its run history according to your team’s practices, and rotate the key if it is exposed. Authentication also matters for avoiding watermarked output, according to PDFShift’s help article.

7. Troubleshooting

Symptom	Likely cause	What to check
PDF has a watermark	The request was unauthenticated or the key was not sent in the expected header.	Verify the `X-API-Key` header is present, correctly mapped, and stored as a secret. See PDFShift’s watermark guidance.
Conversion step is rejected	Wrong endpoint, method, request encoding, missing source, or invalid key.	Compare the request with PDFShift’s current API documentation; inspect the step’s status and error details without exposing the key.
Zapier does not offer a PDFShift action	The native integration may not be available in the current account or action picker.	Check the current app directory and available actions. Confirm support before using Zapier API Request, which is limited to supported public apps.
Conversion works in a test but not for a particular page	The service may not be able to access or render that page, or the page may depend on authentication or client-side behavior.	Try a public URL and compare. The reviewed sources do not document every protected-page or JavaScript rendering case.
Downstream step has no usable file	The conversion output was mapped as text or a reference where the destination expects a file, or the link is not fetchable later.	Inspect the actual output fields and destination input requirements; test the complete Zap with a real run.
Credits run out sooner than expected	Some generated PDFs exceed 5 MB and use multiple credits.	Check output sizes and current PDFShift credit rules in the FAQ.

8. Reliability, performance, and cost planning

PDF conversion runs add work to each Zap execution, so keep the trigger payload small and pass only the URL and required settings. Test representative pages, including the largest expected output, before estimating throughput. The source material does not establish conversion latency, Zapier retry behavior for this specific integration, or a guaranteed response format; consult the current action details and monitor run history.

For budget estimates, count expected successful conversions and account for PDFShift’s documented output-size credit rule. Its FAQ currently describes 50 free monthly credits, with each credit covering up to 5 MB, but that figure is changeable. Also account for any Zapier plan or task limits that apply to your own account; no current Zapier pricing or task allowance is asserted here.

9. FAQ

Is PDFShift’s Zapier integration the same as Zapier PDF Export?

No such equivalence is established by the available sources. Zapier lists PDF Export separately, and its listing does not identify it as PDFShift.

Can I convert any webpage URL?

No universal reach or rendering guarantee is established. The converter must be able to access and render the page; test pages with authentication, paywalls, restrictions, or heavy client-side rendering.

Why does authentication matter if the request still returns a PDF?

PDFShift says unauthenticated requests may produce a watermarked PDF. Its help article identifies X-API-Key as the current authentication header.

Or skip the browser setup

If your goal is a screenshot of a webpage rather than a PDF archive, ScreenshotNeo can return an image or PDF from one GET request. See the ScreenshotNeo API documentation for its parameters.

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

ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. ScreenshotNeo is a website screenshot API and MCP server by Yorker Media.