Skip to content

Integration · Documents & E-signature

PandaDoc integration

PandaDoc SalesforceHubSpot

Short answer

A PandaDoc integration creates proposals, quotes and contracts from Salesforce or HubSpot records, collects e-signatures and payments, and writes status back to the deal.

How the PandaDoc integration works

PandaDoc generates documents from templates populated with CRM data, tracks views and signatures, and updates the opportunity or deal when a document is completed. In HubSpot it can work alongside HubSpot quotes; in Salesforce it can pull products and pricing. Vantage Point is a PandaDoc partner.

What syncs

  • Proposals, quotes and contracts from templates
  • Signature and payment status
  • Completed documents on the record

See the architecture diagram ↓

Integration options

  • PandaDoc apps for Salesforce and HubSpot
  • Template merge fields mapped to CRM fields
  • Workflow triggers on document completion

What to plan for

  • Which system owns pricing and products
  • Template maintenance
  • Retention of signed documents

Frequently asked questions

Can PandaDoc update the deal stage when a contract is signed?

Yes. Document completion can trigger a workflow or flow that updates the deal or opportunity.

Do active PandaDoc quotes survive a CRM migration?

They can be re-linked to the new records, but this needs planning during the migration.

Last reviewed October 2, 2026 by the Vantage Point team. Product names and capabilities belong to their respective vendors; access to some data requires the vendor's approval. Browse all integrations →

Architecture

How data flows: PandaDoc integration

CRM Middleware / connector layer Connected system
What syncs between systems
FromToWhatDirectionTimingHow
SalesforcePandaDoc Merge fields & pricing → one-way on-demandnative connector
PandaDocSalesforce Status & completed documents → one-way event-drivennative connector
HubSpotPandaDoc Merge fields & line items → one-way on-demandnative connector
PandaDocHubSpot Status & completed documents → one-way event-drivennative connector

A typical pattern, simplified. Your design depends on licenses, data ownership and volumes, which we settle in discovery.