Using Doppio with Zapier

Zapier is one of the simplest ways to automate PDF generation without building a backend workflow engine yourself. By combining Zapier with the Doppio API, you can generate PDFs when a form is submitted, a new order is created, a deal changes stage in your CRM, or a document needs to be emailed automatically. This guide explains how the integration works, how to configure the Zap, what payload to send, and where Zapier fits best compared with a code-based integration.

What can you automate with Zapier and Doppio?

The combination works well for operational workflows handled by business teams, operations, or no-code builders. Typical examples include:

• Invoices: generate a PDF invoice when a Stripe payment succeeds or a new order is created.
• Quotes and proposals: export a PDF from Airtable, HubSpot, Notion, or Pipedrive data.
• Customer documents: send confirmations, contracts, or certificates automatically after a user action.
• Scheduled reports: generate weekly or monthly PDFs and send them by email or Slack.
• Screenshots and attachments: use the same pattern for screenshots or post-generation storage workflows.

How the Zap works

The overall logic is straightforward:

1. A trigger starts the Zap: webhook, form submission, CRM update, spreadsheet row, or scheduled event.
2. Zapier sends a webhook request to the Doppio API.
3. Doppio generates the PDF or screenshot.
4. Optional follow-up actions can email the result, store it in Drive or Dropbox, or update the original system.

If you are just getting started, a webhook trigger is the easiest setup because it gives you a direct, flexible entry point into the Zap.

Create a Zapier account

First, register on Zapier if you do not already have an account.

Create a Zap

Then create a new Zap in your dashboard.

Configure the trigger

Create a webhook trigger

We'll use a webhook as the trigger. This gives you a URL that any application can call to start the automation.

Configure the webhook

In the "Event" dropdown, choose the "Catch Hook" option. Leave the field empty in the next "Trigger" step and click "Continue".

Zapier will generate a webhook URL you can call to trigger the Zap. To test it quickly, you can use an API testing tool such as ReqBin, Postman, or a simple curl request.

Configure the Doppio action

Create a webhook action

To make Zapier call the Doppio API, add a new step using Webhooks by Zapier as the action.

Configure the Doppio API call

Choose "Custom Request" in the "Event" dropdown, then configure:

• Method: POST
• URL: https://api.doppio.sh/v1/render/pdf/sync

Example request body for PDF generation

Use a payload that reflects a real business workflow. For example, if you want to generate an invoice or customer document from a hosted HTML page, you can send:

{
  "page": {
    "goto": {
      "url": "https://example.com/invoices/INV-2026-001",
      "options": {
        "waitUntil": ["networkidle0"]
      }
    },
    "pdf": {
      "format": "A4",
      "printBackground": true
    }
  }
}

This tells Doppio to open the page, wait for the network to go idle, and export the page as an A4 PDF with background styles enabled.

Add these headers:

Authorization: Bearer [YOUR_API_KEY]
Content-Type: application/json

Useful variations

Once the basic Zap works, you can extend it in several directions:

• Email the PDF: add Gmail, Outlook, or another mail action after generation.
• Store the file: send the generated document to Google Drive, Dropbox, or another storage app.
• Update the source record: write the generated document URL back to Airtable, HubSpot, or Notion.
• Switch to screenshots: use the screenshot endpoint instead of the PDF endpoint for monitoring or no-code visual workflows.
• Schedule recurring jobs: combine Doppio with Schedule by Zapier for recurring reports or recurring captures.

Check the result

Publish the Zap, then test the full chain by calling the webhook URL or by triggering the upstream event. Check the Doppio dashboard and the Zap run history to confirm that the document was generated successfully.

Common mistakes with Zapier PDF workflows

• The source page is private: if the target URL requires login, the render may fail unless you provide the right access strategy.
• The PDF is generated too early: some pages fetch data after load, so networkidle0 may still need to be combined with better page readiness logic.
• The wrong endpoint is used: Doppio exposes separate endpoints for PDF and screenshot generation.
• The workflow stops too early: generation is often only the middle of the automation; many teams also need a storage, email, CRM, or Slack step after it.
• The payload is too generic: a production workflow usually needs real document options, not just a raw URL and default settings.

When Zapier is enough and when code is better

Zapier is a strong fit for no-code and low-code business workflows: invoices, report delivery, CRM-triggered exports, and internal automations handled by operations teams. If you need high volume, complex authentication, custom retry logic, or deeper control over rendering and error handling, a code-based integration is usually more flexible.

That makes Zapier a great starting point, especially when the goal is speed and simplicity rather than custom infrastructure. If your workflow grows more complex later, you can move the same rendering logic into your application code.

What's next

Zapier can connect Doppio to thousands of services, so the PDF step can sit in the middle of a much larger business workflow. For a screenshot-focused version of the same pattern, see our guide to scheduled website screenshots. For more advanced API options, check the Doppio documentation.