--- title: "PandaDoc Zapier Integration: Triggers, Actions, Limits, and 3 Proven Zaps" description: "What the PandaDoc Zapier integration actually supports: the 4 triggers and 6 actions, plan and usage-credit rules, when Zapier beats a native integration or the API, three proven zap patterns, and the honest limits." canonical: https://pureproposals.com/pandadoc-zapier-integration-guide/ published: 2026-10-13 image: https://pureproposals.com/images/blog/pandadoc-zapier-integration-guide/0.png site: Pure Proposals type: article --- # PandaDoc Zapier Integration: Triggers, Actions, Limits, and 3 Proven Zaps > What the PandaDoc Zapier integration actually supports: the 4 triggers and 6 actions, plan and usage-credit rules, when Zapier beats a native integration or the API, three proven zap patterns, and the honest limits. _Source of truth: https://pureproposals.com/pandadoc-zapier-integration-guide/_ The PandaDoc Zapier integration connects PandaDoc to 7,000+ apps with four triggers (Document Sent, Document Completed, Document Paid, Document Status Changed) and six actions, the most useful of which is Create Document: it generates a document from a PandaDoc template with recipients, tokens, fields, and pricing tables pre-filled from the triggering app's data, and can send it in the same step. It requires a PandaDoc Business or Enterprise plan, and every document generated through Zapier consumes one usage credit. That is the capability in two sentences. Whether Zapier is the right way to wire your proposal system is a different question, and it is the one this guide actually answers: what the integration supports as of October 2026, where it genuinely beats the native CRM integrations and the API, three zap patterns we see work in production, and the limits that catch teams out, starting with the one everyone asks about. ## Key takeaways - Triggers: Document Sent, Document Completed, Document Paid, and Document Status Changed. The first three can be filtered by template or form, so one zap can serve one document type without firing on everything else. - Actions: Create Document (from a template or form, optionally sent immediately), Create Attachment, Create or Update Contact, plus three search steps: Find Document, Get Document Attachments, and Get Document by ID. - Create Document fills recipient roles, CC recipients, tokens, fields, and pricing tables (matched by table name) from upstream zap data, and can file the document into a folder. This is the full pre-filled-proposal flow, not just a bare document shell. - It is gated to PandaDoc's Business and Enterprise plans, and each generated document uses one usage credit. Extra volume comes in 50-document packs, so high-volume automation has a real per-document cost that native CRM integrations do not carry. - The honest limits: taxes do not transfer through Zapier, ID Check cannot be enabled on created documents, zaps do not fire on duplicated documents, and a completed PDF downloaded too quickly can be missing signatures, so build in a delay step. - Zapier is the right glue when your system of record has no native PandaDoc integration. If you run HubSpot, Salesforce, Pipedrive, or another natively supported CRM, the native integration is deeper and meter-free, and the API is the graduation path when logic outgrows zaps. ## Why this integration matters more than it looks Across the 129 sales calls we analysed, manual document creation was the top pain in 82 of them. The teams feeling it worst were rarely teams with no tools. They owned a CRM, they owned PandaDoc, and somewhere between the two sat a person re-typing record data into proposals. We see the pattern often enough that we have a name for it: the human Zapier. One team we spoke to had someone manually adding products into documents every few days as a standing job. At 45 to 50 minutes per manually built proposal, that job is expensive, and it exists because the two systems were never actually wired together. PandaDoc ships native integrations for the major CRMs, but plenty of businesses run on something else: a vertical CRM, a project management tool, a form builder, an internal database. For those teams, Zapier is how the wiring gets done without custom development. The integration is not a toy; configured properly, it is the difference between "we own PandaDoc" and "proposals generate themselves when a record is ready." ## What the PandaDoc Zapier integration supports Connect it from PandaDoc under Settings > Integrations > Zapier, or search for PandaDoc inside the Zapier editor. Two details matter at this step: pick the app named PandaDoc, not PandaDoc (legacy), which is deprecated, and connect the correct PandaDoc workspace, because documents in workspaces you have not connected are invisible to your zaps. ### The four triggers A trigger starts a zap when something happens in PandaDoc: - **Document Sent** fires when a document goes out. - **Document Completed** fires when every recipient has finished, which usually means signed. - **Document Paid** fires on payment, whether collected through Stripe or set manually. - **Document Status Changed** is the catch-all: it fires on status transitions and you filter for the one you want. Document Sent, Completed, and Paid can each be filtered to a specific template or form. Use that filter on every zap you build. An unfiltered trigger fires on all documents in the workspace, which is how teams end up with an invoice zap running on their NDAs. ### The six actions - **Create Document** is the headline action, covered in detail below. - **Create Attachment** adds a file to an existing document, useful for pulling supporting files in from the triggering app. - **Create or Update Contact** upserts a PandaDoc contact by email (an older Create Contact action still appears in some zaps; it is deprecated, use the upsert). - **Find Document**, **Get Document Attachments**, and **Get Document by ID** are search steps: they read data mid-zap so later steps can use it, for example fetching the completed PDF to file it in cloud storage. ### What Create Document can actually fill This is where the integration earns its place. Create Document generates a document from an existing PandaDoc template (or form) and can populate: - **Recipient roles and CC recipients**, mapped from upstream data such as a form submission's email field. - **Tokens**, the square-bracket variables in your template, filled from any field the trigger step provides. If your templates are not built on variables yet, fix that first: our [PandaDoc variables guide](/pandadoc-variables-merge-fields-guide/) covers the setup. - **Fields**, the fillable elements like text fields and dates. Rename them in the template before building the zap: a template full of fields named "textfield" is nearly impossible to map correctly in the Zapier editor, and fields only appear as mappable targets when the template is selected and the field has a merge field value set. - **Pricing tables**, matched by table name, so line items from the triggering app can land as real rows. Note what does not come with them: taxes are not supported through Zapier, so tax either lives as a pre-set rule in the template's [pricing table](/pandadoc-pricing-tables-complete-guide/) or gets handled after generation. - **A folder destination and an optional immediate send** with a message, which turns a one-step zap into record-to-inbox automation. One constraint to plan around: you cannot push a brand-new PDF through Zapier as the document source. The document must come from a template or form that already exists in PandaDoc, which in practice is the right discipline anyway. ## Plan gating and the usage-credit meter Two commercial facts shape whether Zapier is your long-term answer or a stepping stone. First, the integration requires a PandaDoc **Business or Enterprise** plan. Essentials does not include it. Second, **every document generated through Zapier consumes one usage credit**. When the included allowance runs out, additional volume is purchased in 50-document packs that expire at the end of your subscription period, with overages billed monthly. For a team sending 10 automated proposals a month this is a rounding error. For a team generating hundreds of documents from form submissions, it is a real line item, and it is a meter the native CRM integrations do not have: a rep creating a document from a HubSpot deal record through the [native HubSpot integration](/pandadoc-integrations/hubspot/) burns no credit. Price the meter into the decision, not after it. ## When Zapier is the right call (and when it is not) The decision has three tiers, and the deciding question is what your system of record is. **Use the native integration when one exists.** PandaDoc's native integrations for HubSpot, Salesforce, Pipedrive, monday.com, and others run deeper than Zapier reaches: two-way status writeback onto the record, products flowing into pricing tables with the CRM's own structure, documents created and tracked from inside the record, no per-document credit. If your CRM is on that list and your zap idea is "create a document when a deal hits a stage", you are rebuilding a worse version of something that already exists. **Use Zapier when there is no native path, or the event lives outside your CRM.** A vertical CRM with no PandaDoc integration, a Typeform or website form that should produce a proposal, a project management tool that marks work ready to quote, an accounting system that needs to know when a document is paid: this is Zapier territory, and it is exactly the gap the human-Zapier workaround grows in when nobody closes it properly. **Use the API when the logic outgrows zaps.** Multi-step document assembly, conditional pricing logic, custom objects, volume that makes the credit meter painful, or error handling that matters: at that point you want the PandaDoc API, the same decision framing we walk through for [HubSpot custom objects](/pandadoc-hubspot-custom-object-merge-fields/), where Zapier is the middle rung between native capability and custom code. The pattern we recommend in a [PandaDoc implementation](/pandadoc-implementation/) is boring and reliable: native integration for the CRM, Zapier for the edges, API when a workflow earns it. ## Three proven zap patterns These three cover most of what teams actually ship. Each follows the same rule: let PandaDoc's template do the document work and let Zapier move only data. ### 1. Record-ready to pre-filled proposal **Trigger:** the system of record signals readiness (a stage change, a status field, a tagged record, a form submission). **Action:** PandaDoc Create Document, mapping record fields to tokens, contact details to the recipient role, and line items to the pricing table by name. This is the human-Zapier replacement. The build quality lives entirely in the template: locked branding, variables everywhere a hand would otherwise type, a pricing table wired to a catalog. Done right, the proposal a rep opens (or the client receives, if you enable send) is 90 percent finished, which is how teams move from 45 to 50 minutes per proposal to minutes. The template discipline that makes this work is the same as for any serious build; our [branded templates service](/pandadoc-services/pandadoc-templates/) exists because this step, not the zap, is where the quality is decided. ### 2. Completed document to downstream operations **Trigger:** Document Completed, filtered to the template that matters. **Steps:** a Delay step, then Get Document by ID or Get Document Attachments to fetch the signed PDF, then whatever operations need it: file the PDF in cloud storage, raise the invoice in your accounting app, post the win to a team channel, open the onboarding project. The Delay step is not optional decoration. A completed PDF downloaded immediately can be missing signatures because the final render is still processing; a few minutes of delay removes the support ticket. ### 3. Paid or status change back to the system of record **Trigger:** Document Paid, or Document Status Changed filtered to the transition you care about. **Action:** update the originating record: mark the deal won, flip a project status, start the fulfilment workflow. This is the writeback half that teams forget, and skipping it recreates the old problem in reverse: now someone manually checks PandaDoc to update the CRM. Close the loop in both directions or the workaround culture survives. ## The honest limits, in one place Verified against PandaDoc's live documentation in October 2026: - **Taxes do not transfer through Zapier.** Handle tax inside the template's pricing rules or accept manual adjustment. Complex tax logic (the by-province kind we see in [CPQ builds](/pandadoc-services/pandadoc-cpq/)) belongs in the native integrations or the API. - **ID Check cannot be enabled** on documents created through Zapier; PandaDoc points you to the API for that. - **Zaps do not fire on duplicated documents**, so a rep cloning last week's proposal silently bypasses your automation. - **Field mapping depends on template hygiene**: fields need real names, not "textfield", and they only surface in Zapier when the template is selected and the field carries a merge field value. - **Forms do not support approval workflows**, so approval-related statuses never fire for form-sourced documents. - **Workspace scoping**: zaps only see documents in the connected workspace. - **The credit meter**: one usage credit per generated document, topped up in 50-document packs. None of these is disqualifying. All of them are the kind of thing that surfaces three weeks after go-live if nobody checked first. ## When to graduate off Zapier Zapier is the right answer until one of three things happens: the credit meter plus Zapier task costs cross what a proper build would cost, the logic needs branches and error handling that zaps express badly, or you adopt a CRM with a native PandaDoc integration. Graduation is not failure; a zap that ran for a year while the business proved the workflow was a good investment. If you are at that point, or you want the zap layer designed so you never hit it messily, that is implementation work, and it is what we do. A [PandaDoc implementation](/pandadoc-implementation/) scopes the data flow first (what creates documents, what fills them, what happens after signature), then picks native, Zapier, or API per flow on the merits. The proposal for that work goes out within 24 hours of a scoping call. ## FAQ ### Does the PandaDoc Zapier integration work on every PandaDoc plan? No. It requires a Business or Enterprise plan. Zapier's own side works on any Zapier plan, but multi-step zaps (like the delay-then-fetch pattern above) need a paid Zapier tier. ### Can Zapier fill a PandaDoc pricing table? Yes. The Create Document action populates pricing tables matched by table name, including line items from the triggering app. Taxes are the exception: they do not transfer through Zapier, so set tax rules up inside the template instead. ### Why did my zap not fire when a document was duplicated? That is by design: PandaDoc's Zapier triggers do not fire on duplicated documents. If reps routinely clone old documents instead of generating from templates, your automation coverage has a hole that training, not Zapier, fixes. ### Should I use Zapier or the native HubSpot integration? Native, almost always. The native HubSpot integration creates and tracks documents from the deal record, flows products into pricing tables, writes status back, and burns no usage credits. Zapier earns its place for apps with no native integration, or for events the native integration does not cover. ### Is the Zapier integration good enough to skip a proper implementation? Zapier moves the data; it cannot design the system. The template architecture, variable naming, catalog hygiene, and cutover plan decide whether automated documents are accurate and on-brand, and those are implementation decisions whether the transport is Zapier, a native integration, or the API.