How to Use CloudConvert with Zapier to Save Webpage PDFs Automatically
Build a Zap that captures a webpage as a PDF and saves it to Google Drive, on a schedule or when another app provides a URL.
To save webpage PDFs automatically, create a Zap with a trigger that provides a URL, add CloudConvert’s Capture a Website action with Output Format set to pdf, then add a storage action such as Google Drive’s Upload File. Map the PDF file output from CloudConvert into the destination’s required File field, test each step, and turn on the Zap. Zapier lists URL and Output Format as required inputs for Capture a Website; CloudConvert documents the corresponding website-capture operation. Zapier’s CloudConvert integration · CloudConvert Capture Website documentation.
Choose how the Zap should start
The trigger determines when a PDF is captured and where its URL comes from. Choose the trigger that matches the source of your URLs:
- Recurring snapshots: Use Schedule by Zapier, then select a cadence such as Every Day. Zapier publishes an example that pairs its daily schedule trigger with CloudConvert’s Capture a Website action. Check the schedule options and availability in your account before relying on a particular cadence. Zapier’s daily capture example.
- Event-driven captures: Start with an event from another app that supplies the URL, such as a new record or submission. Map that event’s URL into CloudConvert in the next step. Use this when a new event, rather than a clock, should cause a capture.
A schedule is suitable for taking regular snapshots of a known page. An event trigger is suitable when another app provides a changing URL or tells you when a capture is needed. Confirm the timezone, cadence, and account-specific scheduling settings in Zapier before activating a recurring workflow.
Build the Zap step by step
- Create the trigger. In Zapier, start a new Zap. Select Schedule by Zapier and an interval for recurring captures, or choose the event app that supplies your URL. Configure and test the trigger. For an event trigger, make sure the test record contains a complete webpage URL.
- Add CloudConvert. Add CloudConvert as an action and choose Capture a Website. Connect your CloudConvert account if Zapier asks.
- Set the capture URL. Enter a fixed URL for a scheduled snapshot, or use the field picker to map the URL from the trigger record. Use a complete URL including its scheme, such as
https://example.com/page. - Set Output Format to PDF. This is a required field. The action can also create JPG or PNG website screenshots, but choose PDF for this workflow. The current Zapier action listing also shows optional Filename, Wait, and Tag fields; their availability and labels may vary, so follow the fields shown in your connected account. CloudConvert actions in Zapier.
- Add a destination action. For Google Drive, choose Upload File, select the Drive and destination folder, and map CloudConvert’s resulting PDF file into the required File field. You can set a filename if the action offers that field. Google Drive is one documented destination, but another connected storage service can work if its upload action accepts CloudConvert’s output. Google Drive actions in Zapier.
- Test the capture. Run the CloudConvert action with the test URL. Confirm that it completes and returns a file that is a PDF. If the action offers a Filename field, give it a useful name, such as
example-com-weekly.pdf. - Test the upload and workflow. Test the destination action, then run the Zap from trigger through upload. Open the saved file from the target folder and check that it contains the intended page. Turn the Zap on only after this end-to-end check succeeds.
Map a real file, not a preview page
The destination needs the PDF’s file data or a direct download link that the upload action can fetch. A webpage that merely displays or previews the PDF is not the same thing as the file itself. If the upload step rejects CloudConvert’s mapped output, inspect the fields returned by the capture step and select the actual file output or direct download data accepted by that destination. Zapier explains this distinction in its file handling guidance.
Field names and output shapes can change. Use the output shown by your own tested CloudConvert step rather than assuming a field name from another Zap. If several file-like outputs appear, test the one that represents the PDF download.
Useful capture and file settings
| Setting | How to use it |
|---|---|
| URL | Required. Use a fixed page address or map the URL supplied by the trigger. Check that the test value is complete and points to the intended page. |
| Output Format | Required. Select PDF for a document capture. CloudConvert’s documented operation also supports JPG and PNG screenshot output. |
| Filename | Optional in the Zapier action listing. Use a descriptive, predictable name if you want files to be easy to identify. If saving recurring captures, include a date or other unique value when the available mapping fields allow it. |
| Wait | Optional in the Zapier action listing. Use the field as presented in the connected action. If the capture or upload step fails while waiting for a job, inspect the job result and Zap task history before changing timing. |
| Tag | Optional in the Zapier action listing. Use it only if you have a reason to label or organize CloudConvert jobs; it is not needed for a basic capture-and-save workflow. |
| Google Drive destination | Select the correct Drive and folder, then map the actual PDF file to the required File field. Set a name if the action exposes a filename input. |
CloudConvert’s API operation offers additional controls, including choosing an engine or engine version, a filename, and a task timeout. The Zapier action may not expose every API option. Its documented default task timeout is five hours; that is a task ceiling, not a promise that a capture will finish within that time. Consult the operation documentation before building a direct API workflow that depends on an option not present in Zapier. CloudConvert operation parameters.
Test checklist before turning on the Zap
- The trigger test contains the intended URL, and the mapped value is not blank.
- The CloudConvert action has the right page URL and Output Format set to PDF.
- The capture step completes and returns a downloadable PDF.
- The destination File field receives file data or an accepted direct download link, not a preview webpage.
- The uploaded file appears in the intended Drive and folder and opens as a PDF.
- For recurring captures, the schedule and timezone shown in your Zap match the intended run time.
- For event-driven captures, a second test with a different URL confirms the URL is dynamically mapped rather than hard-coded.
Common errors and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| CloudConvert reports a missing URL | The URL field is empty, or the trigger field was not mapped. | Retest the trigger, choose the field that contains the URL, and verify the mapped test value is a complete address. |
| The capture does not produce a PDF | Output Format was omitted or set to an image format. | Open the CloudConvert action and set Output Format to PDF, then retest it. |
| The destination rejects the File value | The mapped value is a preview page or another non-download URL, rather than the file data or a direct download link. | Inspect CloudConvert’s tested output and map its actual PDF file output. Follow the destination’s file-input requirements. |
| The upload succeeds, but the file is in the wrong place | The selected Drive or folder is not the intended destination. | Reopen the destination step, choose the correct Drive and folder, and verify the location in the end-to-end test. |
| A capture works in a manual test but misses on a schedule | The scheduled trigger may be configured differently than expected, or the account’s current schedule settings may constrain the cadence. | Check the Zap’s trigger configuration, timezone, task history, and current account settings. Zapier’s scheduling documentation describes the available intervals and setup. Schedule Zaps help. |
| The saved PDF is blank or does not show the expected page state | The page may depend on content or access conditions that differ during capture, or the selected URL may lead somewhere unexpected. | Open the exact URL independently, check whether it requires access or interaction, and inspect the CloudConvert job result. Retest with a stable public page to separate URL issues from workflow mapping issues. |
| A Zap step fails after an app or field change | A connected account, action field, or output shape may have changed. | Reconnect the affected app if needed, refresh or remap the fields, and test the complete workflow again. Check Zapier task history for the failed step. |
Performance, reliability, and cost considerations
Each scheduled run needs time for the trigger, website capture, and file upload to complete. A capture depends on the target page being reachable and on the job finishing successfully; an upload also depends on the destination connection and its acceptance of the file output. Use Zapier’s task history and the CloudConvert step result to find which part failed. Run an end-to-end test before relying on the PDF as a record or report.
For recurring archives, consider how filenames behave over time. A fixed filename may make files harder to distinguish or may interact with destination behavior differently from a dated filename. Confirm the result in your destination with multiple runs. The exact naming and replacement behavior depends on the fields and options exposed by the connected storage action.
Costs and usage limits depend on the current CloudConvert and Zapier plans, the frequency and number of captures, and the workflow’s task usage. The reviewed documentation does not establish a universal price or plan limit for this workflow. Check the pricing and plan information in your accounts before selecting a capture cadence, especially if the Zap processes many URLs.
Or skip the browser setup
If your goal is to capture a webpage as an image or PDF through an API, ScreenshotNeo offers a one-call screenshot API and an MCP server for AI agents. Use this request for a PNG capture:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpFor code examples and the available API options, see the ScreenshotNeo documentation. Cookie banners are accepted like a visitor and removed before the shot, along with known newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks, blank pages, timeouts, and failed loads are never billed, and cache hits cost nothing. Responses identify the page verdict and billing status in headers. Its MCP server lets AI agents use screenshot, page-info, and PDF-capture tools.
The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 captures, and every feature is available on every plan. Sign up free for ScreenshotNeo.
FAQ
Can the Zap save a PDF to somewhere other than Google Drive?
Yes. Use a connected destination with an upload action that accepts the CloudConvert file output or a direct download link. Map the PDF file into the destination’s required file input and test the upload.
Can I capture more than one webpage?
You can run the workflow for multiple URL records if your trigger and Zap design provide each URL to the capture action. Test how your chosen trigger processes multiple records and how the destination names each resulting file.
Can CloudConvert capture a screenshot instead of a PDF?
Yes. The Capture a Website action supports JPG and PNG as well as PDF. Select the desired output format in the action. CloudConvert’s operation documentation.
Does a scheduled capture run at an exact guaranteed time?
Use the schedule and timezone settings displayed in your Zapier account as the source for your configuration. Check the current scheduling documentation and account settings before depending on a particular cadence.
