PandaDoc + HubSpot: The Complete Integration Guide (2026)
Key Takeaways
The PandaDoc + HubSpot native integration is a two-way sync that pushes CRM data into documents and writes signature status back to deals. Here are the answers most teams are looking for:
What it does: Auto-fills PandaDoc templates with HubSpot deal, contact, and company data via merge tokens, and logs document status back to the deal timeline
Who can use it: HubSpot Starter or above, plus PandaDoc Business or Enterprise. Not available on free tiers of either platform
Setup time: 30 to 60 minutes for the base connection. Add 2 to 4 hours if templates need to be built from scratch with tokens mapped correctly
Biggest failure point: Tokens showing blank because the deal has no associated contact or company, or the admin used the display label instead of the internal HubSpot property name
When to automate: Configure workflow-triggered document creation once your template library is stable. Auto-creation still requires a human to send, by PandaDoc design
When to get help: Multi-pipeline structures, custom object associations, or CPQ / billing sitting alongside the stack. If you have any of those, Proposal Engine, our flagship PandaDoc implementation for HubSpot-first revenue teams, is built for that layer of complexity
What the PandaDoc + HubSpot Integration Actually Does
The PandaDoc + HubSpot integration is a native two-way sync between your CRM and your document platform. HubSpot deal, contact, and company properties auto-populate PandaDoc templates through merge tokens, and once a document is sent, viewed, or signed, that status writes back to the HubSpot deal timeline and any custom deal properties you have mapped.
Before touching any settings, it helps to understand what you’re connecting. The PandaDoc + HubSpot integration is a native two-way sync between your CRM and your document platform. In plain terms: deals in HubSpot can automatically populate PandaDoc proposals, and once a document is sent or signed, that status flows back into HubSpot as deal activity and property updates.
Here’s what the integration handles in practice:
Token population: HubSpot deal and contact properties (company name, deal value, owner name, etc.) auto-fill into PandaDoc templates using merge tags, so reps aren’t copying and pasting
Activity logging: When a document is viewed, signed, or declined, a note is created on the HubSpot deal timeline
Property sync: Document status can write back to custom HubSpot deal properties (useful for building workflows off document state)
Deal stage triggers: You can configure HubSpot workflows to create or send PandaDoc documents automatically when a deal moves to a specific stage
This is the integration most sales teams should have running. If your reps are still pulling deal data from HubSpot and typing it into a Word doc, you’re losing time and introducing errors on every single deal.
Prerequisites Before You Start
Before installing the integration, you need four things in place: a HubSpot Starter, Professional, or Enterprise plan; a PandaDoc Business or Enterprise plan; Super Admin access in HubSpot with Admin rights in PandaDoc; and clean deal and contact data with required properties populated. Missing any of these is the most common reason the integration breaks partway through.
A few things need to be in place before setup. Skipping these is the most common reason the integration breaks partway through:
HubSpot plan: You need HubSpot Starter, Professional, or Enterprise. The free plan does not support third-party app integrations from the marketplace
PandaDoc plan: The HubSpot integration is available on PandaDoc Business and Enterprise plans. It is not available on the free tier or Essentials
Admin access: You need to be a Super Admin in HubSpot and have Admin rights in PandaDoc to install the app and configure OAuth
Clean contact and deal data: The integration maps CRM properties to document tokens. If your HubSpot data is messy (blank required fields, duplicate properties, etc.), documents will generate with blanks or wrong values
Also worth noting: this is not a Zapier integration. It’s a native connection maintained by PandaDoc, which means it’s faster, more reliable, and doesn’t require a middleware account. But it also means any issues need to go through PandaDoc support, not a third-party platform.
Native integration vs Zapier: which should you use?
Teams sometimes ask whether to skip the native integration and pipe HubSpot to PandaDoc through Zapier or Make. For most cases, the native app wins on reliability and depth. Here is the side-by-side:
| Capability | Native PandaDoc + HubSpot | Zapier / Make |
|---|---|---|
| Two-way sync (status writeback) | Yes, on the deal timeline and to custom properties | Partial, one direction per Zap |
| Token / merge-tag population | Full field browser with Deal, Contact, Company, Owner objects | Limited to whatever fields the Zap step exposes |
| Auto-create from deal stage | Native HubSpot workflow action | Requires a Zap and a HubSpot trigger |
| Middleware cost | None (included with plans) | Zapier / Make subscription on top |
| Failure surface | PandaDoc support | Middleware plus both endpoints |
| Best fit | Any team on qualifying plans | Teams on unsupported plans, or edge sync needs the native app misses |
The native integration is the right default. Reach for Zapier only when you are on a plan that does not qualify, or when you need to fan document events out to a third system the native connector does not touch.
Step-by-Step Setup
How do you connect PandaDoc to HubSpot? Install the PandaDoc app from the HubSpot Marketplace, complete the OAuth handshake as a PandaDoc Admin, configure object mapping and status sync in PandaDoc’s HubSpot settings, add merge tokens to your templates, then create documents directly from the PandaDoc panel on any HubSpot deal record. The four steps below walk through each stage.
Step 1: Install PandaDoc from the HubSpot App Marketplace
In HubSpot, go to Settings > Integrations > Connected Apps and click “Visit App Marketplace.” Search for PandaDoc. You’ll find the official app published by PandaDoc, Inc. Click Install.
You’ll be redirected through an OAuth flow that asks you to log in to PandaDoc and grant HubSpot permission to access your workspace. Make sure you’re logging in with an account that has Admin rights in PandaDoc, not a standard user account. If you install with a standard account, certain sync settings won’t appear.
Step 2: Configure the Integration Settings in PandaDoc
Once the OAuth handshake is done, you’ll land in PandaDoc under Settings > Integrations > HubSpot. This page controls the core behavior of the sync:
Object mapping: Decide whether PandaDoc documents should link to HubSpot Deals, Contacts, or both. For B2B sales, Deals is almost always the right choice
Document status sync: Enable this so that sent, viewed, and completed statuses write back to the deal timeline as activity
Property writeback: This is optional but useful. You can create a custom HubSpot deal property (e.g., “PandaDoc Status” as a single-line text or dropdown) and have PandaDoc update it when document status changes
Step 3: How do you set up tokens in PandaDoc templates?
Tokens (also called merge tags) are the variables in your PandaDoc templates that pull data from HubSpot. To set them up: open a template in PandaDoc, click a text block, choose “Token” from the toolbar, and select the HubSpot property you want to pull. Save the template. When a document is created from a HubSpot deal, every mapped token auto-fills from the deal, contact, and company records.
They look like this in the template editor: [Deal.dealname] or [Contact.firstname].
To add a token, open a template in PandaDoc and click on a text block. In the toolbar you’ll see a “Token” option. This opens a field browser where you can select from available HubSpot properties. The token inserts into the document and auto-fills when the document is created from a HubSpot deal.
The most commonly used tokens for a sales proposal:
[Deal.dealname] - Deal name from HubSpot
[Deal.amount] - Deal value
[Deal.closedate] - Expected close date
[Contact.firstname] and [Contact.lastname] - Prospect’s name
[Contact.email] - Used to pre-fill the recipient field
[Company.name] - Company name
[HubSpot_Owner.name] - The deal owner’s name (great for signature blocks)
One thing reps often miss: the token namespace matters. [Deal.X] pulls from deal properties, [Contact.X] from the associated contact, and [Company.X] from the associated company. If you use [Contact.name] but the deal has no associated contact, that field will be blank in the generated document.
Teams selling configurable products or usage-tiered pricing outgrow flat token merges quickly. If your proposals need quantity-driven line items, conditional bundles, or approval routing on discount thresholds, that is a PandaDoc CPQ implementation, not a token-mapping exercise.
Step 4: Create a Document from a HubSpot Deal
Once the integration is live and your templates are set up, here’s how reps actually use it:
Open the HubSpot deal record
Scroll to the PandaDoc panel in the right sidebar (it appears automatically after installation)
Click “Create Document” and choose a template
PandaDoc opens with all mapped tokens pre-filled
Rep reviews, adjusts pricing, and sends
The document is linked to the deal. All activity (views, opens, comments, signatures) surfaces in the HubSpot timeline without any manual updates from the rep.
Field Mapping: The Part Most Teams Get Wrong
The single most common field-mapping mistake is using HubSpot’s display label instead of the internal property name. PandaDoc tokens reference the internal name only, so [Deal.deal_owner] returns blank while [HubSpot_Owner.name] returns the owner. Custom properties follow lowercase-with-underscores. Always verify the internal name in HubSpot’s property settings before mapping a token.
The integration uses HubSpot’s internal property names, not the display labels you see in the UI. This trips up a lot of admins during setup.
For example, the “Deal Owner” field you see in HubSpot has an internal name of hubspot_owner_id, and in PandaDoc it maps as [HubSpot_Owner.name] for the name or [HubSpot_Owner.email] for the email address. If you try to use [Deal.deal_owner], it won’t work.
To find the internal property name in HubSpot: go to Settings > Data Management > Properties, find the property, and look at the “Internal name” field on the detail view.
For custom properties you’ve created (things like “Customer Tier” or “Contract Length”), the internal name usually follows the pattern: lowercase, underscores instead of spaces. In PandaDoc tokens, custom deal properties reference as [Deal.your_custom_property_name].
Tips for clean field mapping:
Test every token before sending templates to your sales team. Create a test document from a known deal with complete data and verify each field populates correctly
For currency fields like deal amount, set the formatting in PandaDoc’s token settings (currency symbol, decimal places) rather than relying on HubSpot’s formatting
Date fields from HubSpot come through as Unix timestamps by default. Use PandaDoc’s date formatting option on the token to display them as MM/DD/YYYY or your preferred format
If a token might be blank (e.g., a deal doesn’t always have a billing address), add fallback text using PandaDoc’s token default value setting
Common Issues and How to Fix Them
Most PandaDoc + HubSpot problems trace to four causes: HubSpot plan doesn’t support integrations, deal missing associated contact or company, status sync toggle off, or workflow trigger built off the timeline event instead of a synced deal property. Each of the four sub-sections below shows the exact fix.
Why doesn’t the PandaDoc panel appear on deal records?
This is almost always a HubSpot plan issue or a caching problem. First, confirm your HubSpot account is on Starter or above. If the plan is correct, try logging out and back in to both platforms. If the panel still doesn’t appear, go to HubSpot > Settings > Connected Apps and disconnect PandaDoc, then reinstall it. The OAuth tokens occasionally go stale.
Why are tokens showing as blank in generated documents?
Usually one of three causes:
The deal doesn’t have the required property filled in (check the deal record in HubSpot)
The deal has no associated contact or company (required for [Contact.X] and [Company.X] tokens)
The token syntax is wrong (double-check internal property names as described above)
Why isn’t document status syncing back to HubSpot?
Check the Document Status Sync toggle in PandaDoc under Settings > Integrations > HubSpot. It must be enabled. Also confirm the HubSpot deal the document was created from still exists and hasn’t been deleted or merged.
Why don’t HubSpot workflow triggers fire on document status?
HubSpot workflows that trigger on PandaDoc document status require the property writeback to be configured. The workflow trigger must use a deal property (e.g., your custom “PandaDoc Status” field) rather than the timeline activity. Set up the property writeback in PandaDoc settings first, then build the workflow in HubSpot using that property as the trigger.
If you have already tried these fixes and the integration still won’t behave, that’s typically the point where a PandaDoc rescue engagement is cheaper than another week of support tickets: we log in, find the root cause, and hand back a working setup.
Best Practices for Teams Running This at Scale
Teams that get lasting value from the integration do five things: standardize the template library so token usage stays consistent, add a “Document Created” pipeline signal for visibility, wire a “Signed” workflow that advances the deal and notifies CS, review document engagement data in weekly sales meetings, and lock template editing to admins so reps can’t break token mappings.
After setting this up for multiple sales teams, a few practices separate the teams that get full value from the ones that end up with a half-configured integration:
Standardize your template library: The integration is only as good as your templates. Have one primary proposal template per product line, with all tokens mapped. Avoid letting reps create templates ad-hoc, as inconsistent token usage breaks automation
Use a “Document Created” deal stage: Add a deal stage (or pipeline property) that automatically gets set when a PandaDoc document is created from that deal. This gives you visibility in your pipeline on which deals have active proposals out
Build a “Signed” workflow: When PandaDoc document status writes back “completed,” trigger a HubSpot workflow to move the deal to Closed Won, create a task for onboarding, and notify the CS team. This is where the real ROI of the integration comes from
Audit document activity weekly: PandaDoc shows you when prospects open documents and how much time they spend on each section. Pull this data into your sales reviews. A prospect who spent 8 minutes on the pricing section is a different conversation than one who hasn’t opened the document
Lock down template editing: Give reps Send access to templates, not Edit access. Every time a rep edits a shared template, they break someone else’s token setup
Setting Up Automated Document Creation with HubSpot Workflows
Yes, you can auto-create PandaDoc documents from HubSpot workflows. Build a deal-based workflow with a “Deal Stage is X” trigger, then add the “Create Document from Template” PandaDoc action. HubSpot will generate the document automatically when a deal hits that stage. Auto-created documents still require a human to send, by PandaDoc design, and the workflow will fail if the deal has no primary contact with an email address.
This is an advanced step, but it’s worth mentioning because it removes the manual step of a rep clicking “Create Document” in the sidebar.
In HubSpot, go to Automation > Workflows and create a deal-based workflow. Set the trigger to “Deal Stage is X.” In the actions, you’ll see a PandaDoc action called “Create Document from Template.” Select the template, and HubSpot will automatically generate the PandaDoc document when any deal hits that stage.
A few caveats: auto-created documents don’t auto-send (PandaDoc requires a human to review and send). The document appears in the deal’s PandaDoc panel, ready for the rep. Also, if the deal lacks a primary contact with an email address, the workflow action will fail. Build an enrollment condition that checks for a valid contact email before running the PandaDoc action.
Frequently Asked Questions
Is the PandaDoc + HubSpot integration free?
The integration itself is included with qualifying PandaDoc and HubSpot plans, at no extra per-connection fee. You do need PandaDoc Business or Enterprise and HubSpot Starter or above. There is no add-on charge from either vendor for turning the native connector on.
How long does PandaDoc + HubSpot setup take?
The base connection takes 30 to 60 minutes, including the OAuth install, object mapping, and status-sync configuration. Building templates with tokens mapped correctly usually adds another 2 to 4 hours per template, more if you also want workflow-triggered auto-creation and a full “Signed” writeback workflow.
Can PandaDoc auto-send documents from a HubSpot workflow?
No. HubSpot workflows can auto-create PandaDoc documents from a template when a deal hits a stage, but sending still requires a person to click Send inside PandaDoc. This is a deliberate PandaDoc guardrail so contracts don’t leave the building without a human review.
Does the integration work with custom HubSpot properties?
Yes. Custom deal, contact, and company properties are available in the PandaDoc token browser as long as you reference them by their internal HubSpot name (typically lowercase with underscores). Display labels won’t work in the token syntax.
What breaks if we downgrade our HubSpot or PandaDoc plan?
Dropping HubSpot to the free tier disables all third-party marketplace integrations, so the PandaDoc panel disappears from deal records and status sync stops. Downgrading PandaDoc to Essentials or free removes the HubSpot integration entirely. Existing documents keep working, but new-document creation from HubSpot deals stops.
When to Call in Help
Most teams can self-serve through the initial setup. Where things get complicated: multi-pipeline deal structures, custom object associations, content libraries synced across multiple HubSpot portals, and integrations that involve a third system (like a CPQ or billing platform sitting alongside both tools).
If you’re dealing with any of those scenarios, or if you’ve run through this guide and something still isn’t working, it’s usually faster to have someone who configures this daily take a look rather than spending hours in support tickets.
We offer a dedicated HubSpot integration setup service for teams that want this done right the first time, including template builds with all tokens mapped, workflow configuration, and testing on real deal data.
Need help setting this up? We configure PandaDoc + HubSpot for teams every week. Book a free call and we’ll take a look at your setup.