PandaDoc
Put PandaDoc to work on your own records, inside your rules, with a person approving what it changes.
21 ways to read, 10 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with PandaDoc, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create contact
contacts.createApproval by rule - Create document folder
document_folders.createApproval by rule - List contacts
contacts.listRead
Example flow
- Salesforce · Read opportunities
opportunities.listDone - PandaDoc · Create document from template
documents.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches PandaDoc.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to PandaDoc
- PandaDoc's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a PandaDoc test account before you go live.
For developers
Technical detail
PandaDoc documents, drafts from templates or file URLs, folders, linked CRM objects, templates, content library, contacts, members, forms and webhooks.
PandaDoc API docs- Source actions
- 21
- Destination actions
- 10
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
contacts4
- Create contactDestinationNot retried automaticallyApproval before production
Creates a workspace contact.
- Get contactSource
A contact by ID.
- List contactsSource
Workspace contacts, optionally matched by exact email.
- Update contactDestinationProvider duplicate protectionApproval before production
Updates supplied fields on a contact.
content library items2
- Get content library itemSource
A content library item's roles, variables, fields and metadata.
- List content library itemsSource
Reusable content blocks (pricing tables, clauses) in the content library.
current member1
- Get current member and workspaceSource
The member the API key acts as, with the workspace ID and name.
document attachments1
- List document attachmentsSource
Attachment metadata on a document.
document folders2
- Create document folderDestinationNot retried automaticallyApproval before production
Creates a document folder, optionally inside a parent folder.
- List document foldersSource
Document folders, optionally inside a parent folder.
document moves1
- Move document to folderDestinationProvider duplicate protectionApproval before production
Moves a document into a document folder.
document status1
- Get document statusSource
Lightweight status check, for polling after create or send.
documents5
- Create document from templateDestinationNot retried automaticallyApproval before production
Creates a draft document from a template with recipients, variables and field values.
- Get document detailsSource
Full document details: recipients, tokens, fields, pricing, metadata and tags.
- List documentsSourceIncremental
Documents filtered by status, template, folder, tag, search text or modified date.
- Send documentDestinationNot retried automaticallyApproval before production
High risk: sends a draft document to its recipients for viewing, approval, signature or payment.
- Update draft documentDestinationProvider duplicate protectionApproval before production
Changes the name, recipients, variables, fields or metadata of a draft document.
forms1
- List formsSource
PandaDoc forms (self-serve documents) with status.
linked objects2
- Link CRM objectDestinationNot retried automaticallyApproval before production
Links a document to a CRM record of a connected PandaDoc integration.
- List linked CRM objectsSource
CRM records (for example a HubSpot deal) linked to a document.
members2
- Get workspace memberSource
One workspace member by membership ID.
- List workspace membersSource
Members of the API key's workspace with role and licence.
template folders2
- Create template folderDestinationNot retried automaticallyApproval before production
Creates a template folder, optionally inside a parent folder.
- List template foldersSource
Template folders, optionally inside a parent folder.
templates2
- Get template detailsSource
Template roles, variables (tokens), fields and metadata for mapping document creation.
- List templatesSource
Templates in the workspace.
url documents1
- Create document from file URLDestinationNot retried automaticallyApproval before production
Creates a draft document from a publicly reachable PDF, DOCX or RTF file URL, with recipients and optional form-field parsing.
webhook events2
- Get webhook deliverySource
One webhook delivery attempt (signature and bodies are not returned).
- List webhook deliveriesSourceIncremental
Webhook delivery attempts with their result, optionally since a time.
webhook subscriptions2
- Get webhook subscriptionSource
One webhook subscription (the shared key is never returned).
- List webhook subscriptionsSource
Webhook subscriptions with triggers and status (shared keys are never returned).
Access and limits
- Authentication
- PandaDoc API key
- Plans and access
- API access requires an Enterprise plan or a developer sandbox key. Sandbox keys work only with sandbox documents and have low rate limits.
- Test environment
- Generate a sandbox API key in the Developer Dashboard.
- Rate limits
- Per-endpoint limits per minute in production (for example document creation and sending are lower than reads); sandbox keys are limited to 10 requests per minute. HTTP 429.
- Pagination
- page and count (up to 100).
- Provider events
- PandaDoc webhooks for document state, recipient and content events (HMAC signed). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- OAuth 2.0 connections are not implemented; use an API key.
- Document creation is asynchronous: new documents start in document.uploaded; poll Get document status until document.draft before sending.
- Documents can be created from templates or from a public file URL; binary PDF uploads, downloads, deletes, voids, status overrides, ownership transfers and recipient edits are intentionally not implemented.
- PandaDoc has no workspace list endpoint for API keys; the current workspace is read through Get current member. Workspace and user creation are not implemented.
- Webhook subscriptions and deliveries are read-only; shared keys, signatures and delivery bodies are never returned.
- Document creation and sending have no idempotency key; uncertain writes are not repeated automatically.
Developer reference
- Create the PandaDoc credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose PandaDoc, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/pandadoc and the Connections API.