Skip to main content

​
About PandaDoc

PandaDoc is a document automation and e-signature platform for contracts, proposals, and other business documents. Serval connects to a PandaDoc workspace with a single API key: an admin pastes it in once, Serval stores it encrypted for your team, and workflows call PandaDoc on demand with that key attached. Serval only ever sends the key to one host for this integration: api.pandadoc.com. Authentication: API key (a PandaDoc workspace API key). There is no OAuth sign-in flow, and the key never expires on a schedule - it works until you revoke or rotate it in PandaDoc. Data sync: None. Nothing is imported into Serval in the background - PandaDoc is called only when a workflow runs.

​
What the PandaDoc integration enables

Anything defined in the PandaDoc API can be accessed through Serval.

​
Get your credentials

Serval needs a PandaDoc API key for the workspace you want it to operate in, created by a user with admin access to that workspace’s API settings. PandaDoc’s official guide is here: API key authentication process.
1

Open PandaDoc settings

In PandaDoc, click the gear icon (Settings) in the bottom left corner.
2

Go to API and Integrations

Under your current workspace, click API and Integrations.
3

Find the API section

Scroll to the API and Webhooks section.
4

Open the API tile

Click the API tile, then click Open.
5

Copy the API Key

Copy the API Key and store it securely - you will paste it into Serval.
Use a production key for live use. PandaDoc also issues sandbox keys, and a sandbox key only works against sandbox data - workflows pointed at your real documents will fail with one.
API keys are scoped to a single PandaDoc workspace. If Serval should work across more than one workspace, create a key in each and connect each one separately.

​
Connect in Serval

1

Open the connect form

Find the app in your Serval Apps catalog and click Connect. It’s listed as Pandadoc - that exact spelling, with a lowercase “d”.
2

Enter an Instance Name

The Instance Name field is a plain text field. It isn’t marked required on the form, but it becomes the connection’s display name and internal identifier, so always fill it in - and if you plan to connect more than one workspace, give each a distinct name.
3

Paste your API Key

The API Key field is a password field. Paste the full key exactly as PandaDoc shows it.
4

Submit

Click Submit. If installation fails, the form shows “Failed to install integration” along with the underlying error.
Serval does not test the key against PandaDoc when you connect, and this integration has no automated health checks - a mistyped or revoked key is accepted and only fails later, the first time a workflow calls PandaDoc. Verify the connection right after saving (see below).
When you edit an existing connection, the stored key appears masked - bullets plus its last 4 characters. On the connection’s settings page, a pencil icon swaps in a replacement box (its placeholder reads “Enter new value”); in the reconnect dialog, the masked value sits next to a Replace button. Leaving the masked value untouched - or saving with the replacement box empty - keeps your existing key, so you can safely change just the Instance Name. To rotate the key, paste the complete new key and save.

​
Verifying the connection

The PandaDoc integration has no automated health checks in Serval, so nothing runs after you connect and there is no pass/fail status to look for. To verify the connection:
  1. Create or run a simple workflow step that reads PandaDoc data - for example, one that lists your documents or templates.
  2. If the step returns PandaDoc data, the key works.
  3. If it fails with an authentication error, copy the API key from PandaDoc again and replace it in the connection settings.
If a basic read works but a workflow can’t find a specific document or template, the item most likely lives in a different PandaDoc workspace (keys are workspace-scoped), or you connected a sandbox key while the data lives in production.

​
Gotchas and troubleshooting

No call is made to PandaDoc when you save the connect form, so a bad key is stored without complaint, and there is no health check to catch it afterward. The failure only appears the first time a workflow calls PandaDoc. Make a quick test workflow part of your connect routine.
On the connection’s settings page the key is shown masked (bullets plus its last 4 characters) with a pencil icon to replace it; the reconnect dialog shows the same masked value with a Replace button. Leaving the masked value untouched keeps the existing stored key - renaming the connection never requires re-entering the key - and so does saving with the replacement box left empty. To rotate, enter the entire new key and save. If an update fails, Serval shows a message starting with “Failed to update integration:” or the message “Failed to update configuration”, depending on which form you used.
The Instance Name doubles as the connection’s display name and internal identifier. Saving an update with the name emptied out is rejected and surfaces as a generic update failure. Renaming does work, but it also changes the internal identifier, so workflows pinned to this specific PandaDoc connection may need to be re-pointed afterward. Pick a clear, distinct name when you connect - especially if you connect multiple PandaDoc workspaces.
PandaDoc issues both production and sandbox API keys. A sandbox key connects without error but can only reach sandbox documents and templates, so workflows against your real workspace data will fail. Use a production key for live use.
PandaDoc returns list results (documents, templates, contacts, and so on) one page at a time. Workflows have to ask for the next page until an empty page comes back - if a workflow seems to be missing items, it’s usually only reading the first page. Serval AI handles this when it authors the workflow, but it’s worth checking if results look incomplete.
Serval authenticates to PandaDoc using PandaDoc’s “API-Key” authorization scheme, not the more common “Bearer” scheme. If you sanity-check the same key with another tool and use Bearer, PandaDoc rejects it even though the key is fine in Serval. Serval also only ever attaches the key to requests bound for api.pandadoc.com.
This connector does not import PandaDoc users, documents, or anything else into Serval, and it has no access-management features. If you’ve seen older Serval documentation listing an “Access Management” capability for PandaDoc, that does not apply to the current integration - user and permission changes in PandaDoc are only possible as ordinary workflow API calls.
Need help? Contact support@serval.com for assistance with your PandaDoc integration.