Reference · built on requestConnectorCRM & sales

PandaDoc

Documents, templates, recipients, and signing status from PandaDoc through the public API and webhooks.

Request PandaDocAsk about this listing

About

PandaDoc is a document workflow product for proposals, quotes, and contracts. A workspace holds documents built from templates or uploaded PDFs, the recipients who sign them, and a status for each document from document.draft through document.sent, document.viewed, and document.completed. Webhooks post each change to your endpoint as events such as document_state_changed and recipient_completed.

Through Fibric, an operator reads document status alongside the deal or order it belongs to, then proposes the next step: send a draft, chase an unsigned quote, or mark a document declined with a note. You approve. The connector makes one call to PandaDoc and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from PandaDoc and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

What it reads

  • Documents through GET /public/v1/documents, filtered by status, template_id, contact_id, and created or completed date ranges
  • Document status values from document.uploaded and document.draft through document.sent, document.viewed, document.completed, document.voided, and document.declined
  • document_state_changed and recipient_completed webhook events, the latter carrying action_by and action_date for the recipient
  • document_creation_failed, document_deleted, and document_updated events for documents that fail, are removed, or return to draft
  • Templates and their status through the Templates API, with template_created, template_updated, and template_deleted events
  • quote_updated events when a user saves changes in Quote Builder
  • Contacts and workspace users through the Contacts and Users endpoints

Proposed actions

  • Target capability: propose creating a document from a template or an uploaded PDF through POST /public/v1/documents
  • Target capability: propose sending a draft through POST /public/v1/documents/{id}/send, with subject, message, and silent options
  • Target capability: propose a manual status change through PATCH /public/v1/documents/{id}/status, with a private note and recipient notification
  • Target capability: propose an embedded signing session through the Create Document Session endpoint for a sent document

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase an unsigned quote

    A document sits in document.sent or document.viewed past its follow-up window. The operator drafts a reminder tied to the deal and proposes a resend or a message for approval.

    With Quote Follow-up, Abandoned Quote

  • Turn a signed quote into an order

    recipient_completed and document.completed arrive for a quote. The operator matches it to the opportunity and proposes the order record in your commerce or ERP system.

    With Quote to Order

  • Expire stale documents

    Documents past their expiration date with no signature are proposed for a status change to expired, with a private note, so the pipeline reflects what is real.

    With Quote Expiry, Stale Pipeline

  • Renew before the contract lapses

    A completed contract carries an end date in its fields. The operator proposes a renewal document from the same template ahead of that date.

    With Renewal Reminder, Contract Lapse

What it needs

  • A PandaDoc plan that includes API access; production keys require approval from PandaDoc's sales team
  • A workspace member whose role covers the documents the connector reads; keys inherit that user's role and license
  • A webhook subscription created in the Developer Dashboard or through POST /public/v1/webhook-subscriptions
  • An HTTPS endpoint that answers within 20 seconds and returns a status below 400
Authentication
An API key sent as Authorization: API-Key {key}, or an OAuth 2.0 app with read+write scope sent as a Bearer token; both issued from the Developer Dashboard.

Limits

  • Rate limits are per endpoint on a sliding 60-second window; sandbox keys allow 10 requests per minute on any endpoint.
  • Failed webhook deliveries are retried 3 times; a 410 response deactivates the subscription.
  • A workspace holds at most 300 webhook subscriptions, and a list call returns at most 100 documents per page.
  • If the user who generated an API key leaves the workspace, that key is deactivated.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request PandaDoc

Questions and answers

Does PandaDoc push status changes, or does the connector poll?
Both are documented. Webhooks post document_state_changed, recipient_completed, and related events to your endpoint. GET /public/v1/documents/{id} returns status on demand. PandaDoc recommends webhooks for event-driven needs rather than polling the status endpoint.
Which statuses can be set through the API?
PATCH /public/v1/documents/{id}/status accepts completed (2), paid (10), expired (11), and declined (12). Allowed transitions depend on the current status; paid needs a connected payment app. Sending requires document.draft, and download requires document.completed.
What does a sandbox key allow?
Sandbox keys work against the same public API with a limit of 10 requests per minute on any endpoint. Senders and recipients must share the organization's email domain. Production keys need approval and carry per-endpoint limits.
Ask about PandaDoc

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with PandaDoc through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy