Skip to main content
Telara

Integrations / PandaDoc

PandaDoc logo

PandaDoc

PandaDoc e-signature and document workflow platform for creating documents from templates, sending them for signature, and tracking signing status.

API key
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

A PandaDoc workspace you can administer.
Admin who can create API keys or approve OAuth.

Vendor setup

Get the credential

1
Prefer Connect in Telara
Settings → Integrations → PandaDoc. If Telara offers OAuth, click Connect and approve. You do not create a PandaDoc OAuth app.
2
Or create an API key
In PandaDoc, go to Settings → Integrations → API → API keys. Click Create API key. Copy it once.
3
Paste in Telara
Paste the key if you are not using OAuth. Sandbox keys live under the sandbox workspace — do not mix them with production.

Permissions Telara requests

  • read+write
    OAuth 2.0

In Telara

Connect in Telara

API key

PandaDoc API key from Settings > API & Integrations > API Keys. Sent as "Authorization API-Key <key>".

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
OAuth 2.0

PandaDoc OAuth2 app. Scope "read+write" is required to create, send, and delete documents; "read" only allows viewing templates and document details.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Knowledge

What gets indexed

ResourceCoverage
DocumentPartial — not every record the vendor holds is synced
TemplatePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
DocumentUp to 1 dayRemoved records disappear on the next full sync
TemplateUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Document, Template.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Documents the authorizing user cannot open stay out of Telara.
Sandbox vs production are different workspaces and different keys.