--- title: "PandaDoc Pipedrive Integration: The Complete Setup Guide" description: "How to set up the PandaDoc Pipedrive integration properly: connecting the apps, mapping deal fields to variables, flowing products into pricing tables, sync rules for status writeback, and the failure points to avoid." canonical: https://pureproposals.com/pandadoc-pipedrive-integration-setup-guide/ published: 2026-10-05 image: https://pureproposals.com/images/blog/pandadoc-pipedrive-integration-setup-guide/0.png site: Pure Proposals type: article --- # PandaDoc Pipedrive Integration: The Complete Setup Guide > How to set up the PandaDoc Pipedrive integration properly: connecting the apps, mapping deal fields to variables, flowing products into pricing tables, sync rules for status writeback, and the failure points to avoid. _Source of truth: https://pureproposals.com/pandadoc-pipedrive-integration-setup-guide/_ To set up the PandaDoc Pipedrive integration, connect the two apps from PandaDoc's Settings > API and Integrations page (or install PandaDoc from the Pipedrive Marketplace), check that the deal, person, and organization fields you need appear as PandaDoc variables, attach products to your deals so they flow into pricing tables, and configure sync rules so document status writes back to the deal. The connection itself takes minutes; making it a working system your reps actually use takes deliberate field choices, product catalog discipline, and a proper cutover. That second part is where most teams stall. Across the 129 sales calls we analysed, manual document creation was the top pain in 82 of them, and a large share of those teams already owned both the CRM and PandaDoc. The software was connected. The system was not. This guide covers both: the click-path to a clean connection, and the configuration decisions that separate "the apps are linked" from "reps generate accurate proposals from the deal in minutes." ## Key takeaways - The integration connects PandaDoc to Pipedrive's Deal, Person, and Organization records. Field values become document variables, deal products flow into pricing tables, and documents are created and tracked from inside the Pipedrive record. - It requires a PandaDoc Business or Enterprise plan, and each user connects their own account: this is a per-user install, not a one-time admin switch. - Variables follow the pattern `[Deal.FieldName]`, `[Person.FieldName]`, `[Organization.FieldName]`, and custom Pipedrive fields appear alongside the standard ones. Map the fields your team reliably fills in, not every field that exists. - Products attached to a deal transfer into PandaDoc pricing tables with name, SKU, description, price, quantity, discount, and percentage-based tax. A product with no name, price, or quantity will not transfer, so catalog hygiene matters. - Sync rules are the writeback layer: signed PDFs attach to the deal's files, document status can advance the deal stage or mark it won, and pricing table edits can update the deal's products. Skipping them leaves half the integration unbuilt. - Test on real deals, not test records, and close the old Word or PDF route on a named date. An integration that runs in parallel with the old way loses to the old way. ## What the PandaDoc Pipedrive integration actually does Once connected, the integration does four jobs: 1. **Data into documents.** Values from Pipedrive deals, people, and organizations populate PandaDoc variables, so a proposal opens pre-filled with the client name, deal value, and terms from the record. Deal variables are available whether you start from the deal, the person, or the organization. 2. **Products into pricing tables.** Products attached to the deal map into PandaDoc pricing tables with quantities, unit prices, discounts, and taxes intact, in the same order they sit on the deal. Quote builder blocks get the same data plus billing frequency. 3. **Documents from the record.** Reps create, send, and track documents from the PandaDoc panel on the Pipedrive record, without switching tools, and a refresh control pulls the latest record values into an open document. 4. **Status back to Pipedrive.** Sync rules write document events back to the deal: status display on the record, the signed PDF attached to the deal's files on completion, deal stage or won/lost changes driven by document status, and even line items synced back to the deal's products. Everything in the rest of this guide is configuration of those four jobs. If any one of them is missing after your setup, you have a partial integration, and partial integrations are exactly what produces the workaround culture where someone on the team manually re-types deal data every few days. We have seen that pattern often enough that we have a name for it: the human Zapier. One team we spoke to had a person manually adding products into documents every few days as a standing job. The integration below makes that job not exist. ## Before you connect: prerequisites and decisions Check the account requirements first: - **PandaDoc plan.** The Pipedrive integration is available on PandaDoc's Business and Enterprise plans. The eSignature-only plan does not include variables, which removes most of the integration's value, so check your plan before scheduling the rollout. - **Per-user connection.** Unlike some CRM integrations, each PandaDoc user connects to Pipedrive individually. Budget for that in rollout: every rep needs the two-minute connect step done before their first document, or generation will fail for them specifically while working for everyone else. - **Permissions.** You need a PandaDoc workspace admin to set up templates and sync rules, and reps need Pipedrive access to the deals they will generate from. Then make two decisions that are much cheaper to make now than after rollout: - **Where do reps create documents?** The integration allows creation from deals, people, and organizations. For a sales team the answer should be the deal, where the products and value live. Pick one and train it consistently; scattering the habit across record types confuses reps about where documents live. - **Which fields will feed the documents?** Walk through your most-sent proposal and list every value in it that exists in Pipedrive. That list, not the full schema, is your variable scope. This is the same scoping discipline that a full [PandaDoc implementation](/pandadoc-implementation/) starts with, and skipping it is the number one reason integrations stall. ## Step 1: Connect PandaDoc and Pipedrive In PandaDoc, go to Settings > API and Integrations, select Pipedrive, and click Connect, signing in to the Pipedrive account you want linked. Alternatively, find PandaDoc in the Pipedrive Marketplace and install from there; both routes end in the same place. Once connected, open any Pipedrive deal and check the PandaDoc options appear on the record. If they do not, the usual causes are a workspace mismatch (the user is in a PandaDoc workspace without an active Pipedrive connection) or a stale authorisation that needs reconnecting. Resolve that before going further: a half-connected account produces confusing behaviour later that looks like mapping problems but is not. Remember the per-user rule: repeat the connect step for every rep who will send documents, not just the admin who sets the system up. ## Step 2: Build templates around Pipedrive variables This is the step that decides whether the integration works. In PandaDoc templates, variables hold the dynamic values in a document, and the integration fills them from Pipedrive fields using the `[Object.FieldName]` pattern: `[Deal.Title]`, `[Person.FirstName]`, `[Organization.Name]`, plus any custom fields you have added in Pipedrive. Work from the field list you made in the prerequisites: - Place standard fields first: organization name, contact first and last name, deal title and value. - Add the custom fields your proposals actually use: contract term, service start date, project scope fields, whatever your documents display. Custom Pipedrive fields appear as variables automatically. - Money fields come through in several formats (formatted with currency, currency code alone, raw number), so pick the variant that reads correctly in the sentence you are writing. - For every variable, check the field is **reliably populated** on real deals before the stage where reps create documents. A variable mapped to a usually-empty field is worse than none, because it produces blanks that make reps distrust generation entirely. Where a field you need is often empty, fix the process rather than the template: make it required at an earlier pipeline stage, or drop the variable. A template with 10 dependable variables beats one with 30 theoretical ones. Template roles help here too: assign the deal's contact to a role like Client and the recipient's name and email prefill on creation. The templates themselves deserve the same rigour: locked branding, editable variables, one master template per deal type. That is its own discipline, covered by our [PandaDoc templates](/pandadoc-services/pandadoc-templates/) service page. ## Step 3: Flow deal products into pricing tables Pricing is where manual re-entry costs the most and where errors are most expensive. The integration transfers products attached to the deal into the PandaDoc pricing table, and the transfer rules reward a clean catalog: - Product name, SKU, price, quantity, and discount carry over, and line items keep the order they have on the deal. - Comments on a Pipedrive product populate the description column in the pricing table, so write them as client-facing copy, not internal notes. - Taxes transfer only as percentages, and a tax set on a product overrides the deal-level tax. Flat-amount tax arrangements need restructuring before they will carry. - A line item with an empty name, price, or quantity does not transfer at all. If reps report "missing" products, audit the deal's line items for blanks before blaming the integration. Carry discounts through from Pipedrive rather than letting reps apply them freehand in the document: discounts belong in governable fields. And test with your ugliest real deal: multi-line, discounted, mixed one-off and recurring items. If that renders correctly, the simple deals will too. If your pricing involves bundles, conditional options, or approval-gated discounts, the pricing table alone may not be enough, and you are in CPQ territory. See our [PandaDoc CPQ](/pandadoc-services/pandadoc-cpq/) service page for what that adds on top of the integration. ## Step 4: Create and track documents from the deal With templates and products wired, the rep flow is short: open the deal, create a new document from the PandaDoc panel, pick the template, and the variables, recipients, and pricing table fill from the record. If the deal changed since the document was drafted, the refresh control pulls the latest values in without recreating the document. Documents created outside Pipedrive can also be linked to a deal afterwards from the document's details panel, which keeps the record complete when a proposal started life elsewhere. The goal is that a rep never asks "where do I make the proposal": the answer is always "on the deal, where you already are." Teams we work with typically start at 45 to 50 minutes per proposal and get to minutes once generation runs from the CRM record. ## Step 5: Configure sync rules for status writeback Sync rules are the integration's writeback layer, and they are what turns it from a convenience into a system. Configure them deliberately rather than accepting defaults: - **Signed PDF to the deal.** The completed, signed PDF attaches to the deal's files automatically, so the record holds the final artefact. - **Status into the pipeline.** Set document status to advance the deal stage, or mark the deal won when the proposal is completed. Pipeline reality and document reality stop being two separate things a human reconciles. - **Field and variable sync.** Values a client fills in on the document, and document system values like completion date, can write back to deal fields, which makes them reportable and automatable in Pipedrive. - **Line items back to products.** Edits made in the pricing table or quote builder can update the deal's products, so the deal value stays honest after negotiation. For catalog products this matching runs on SKU, so PandaDoc product SKUs must match Pipedrive product codes exactly. Skip writeback and you keep the human Zapier, just for status instead of products: someone checking PandaDoc and updating Pipedrive by hand. ## Step 6: Test on real deals, then cut over Test with live data before rollout: - Generate documents from five to ten real deals, including at least one messy one: long product list, discounts, a custom field with unusual characters. - Check every variable filled, the pricing table matches the deal to the cent, and the sync rules fire within a minute of each status change. - Have one rep, not an admin, run the flow end to end and note every point of hesitation, including whether their individual Pipedrive connection is actually active. Then roll out deliberately: short role-based training, a first-week target of every rep sending at least one real document through the new flow, and a named date when the old route (Word, PowerPoint, duplicated PDFs) is closed. Teams that run old and new in parallel indefinitely drift back to the old way, because habit always wins a tie. The full playbook for this stage is in our [PandaDoc onboarding](/pandadoc-services/pandadoc-onboarding/) service. ## The four ways Pipedrive PandaDoc setups fail Having rescued a fair number of stalled setups, the failure points are consistent: 1. **Mapped-but-empty fields.** The variables exist, the data does not, documents generate with blanks, reps go back to typing. Fix the data discipline or drop the variable. 2. **Connected but not implemented.** The apps are linked, but there are no real templates, no products on deals, and no sync rules. Reps see no benefit, so nothing changes. Being "integrated" was never the goal; generating accurate documents in minutes was. 3. **Pricing outside the system.** Line items live in a spreadsheet, get pasted into documents, and Pipedrive never knows what was actually quoted. Everything downstream (forecasting, reporting, renewals) inherits the gap. The product transfer rules above only help if the products are on the deal in the first place. 4. **The per-user install assumed away.** The admin connects, tests, and declares victory; half the team never ran their own connect step and quietly concludes "it doesn't work for me." Make the two-minute connection part of onboarding every rep. If you recognise your own setup in that list, the repair is usually faster than the original build, because the workarounds show you exactly what is broken. ## PandaDoc Pipedrive integration FAQ ### How long does the PandaDoc Pipedrive integration take to set up? The connection takes minutes per user. A working setup with dependable variables, products flowing into pricing tables, tested templates, and sync rules typically takes 2 to 5 days for a standard pipeline. Complex pricing, multiple pipelines, or a messy product catalog extend that, with field and catalog decisions, not technical work, driving most of the timeline. ### What PandaDoc plan do I need for the Pipedrive integration? PandaDoc's Business or Enterprise plan. The eSignature-only plan does not include variables, which removes the pre-fill capability that makes the integration worth having. Check PandaDoc's current pricing page before committing, as plan packaging changes. ### Can PandaDoc update the Pipedrive deal when a proposal is signed? Yes. Sync rules can attach the signed PDF to the deal's files, advance the deal stage or mark the deal won based on document status, and write document values like completion date back to deal fields. This is one of the highest-value parts of the integration and the one most often left unconfigured. ### Why are products missing from my PandaDoc pricing table? The most common cause is a blank: a line item with no name, no price, or no quantity does not transfer from the deal. Next most common are tax formats (only percentage-based taxes carry over) and, for catalog syncing back to Pipedrive, SKUs in PandaDoc that do not match the Pipedrive product codes. ### Should I use the native integration or Zapier? Native, for this stack. The built-in integration covers data pre-fill, product transfer, status writeback, and signed-PDF attachment without per-task fees or an extra tool to maintain. Zapier earns its place only for edge cases the sync rules cannot express, and it should supplement the native connection, not replace it. ## Get the integration implemented properly The marketplace listing gets you connected. The [PandaDoc Pipedrive integration](/pandadoc-integrations/pipedrive/) page covers what we build on top of that connection: variables that fill reliably, pricing tables driven by the deal's products, sync rules that keep the pipeline honest, and a rollout your reps stick with. If your integration has been "set up" for months and proposals are still assembled by hand, that gap is precisely what we fix.