PandaDoc
PandaDoc is a document workflow platform. This Willow connector lists workspace members (email, role, license, and active status) and removes a member from a workspace.
Removing a member does not cancel the billed org license. The Account Owner must cut licenses in Settings → Billing → Manage licenses.
Authentication Types
PandaDoc supports 1 authentication method on this connector:
- API Key —
Authorization: API-Key {key}from the Developer Dashboard.- Pros: Simple server-to-server setup
- Cons: Tied to the user who generated the key; that user's removal deactivates the key. Member tools require an Org Admin (or workspace admin for remove) key.
OAuth is available in the PandaDoc API but is not configured on this connector. API access needs at least a Business plan (sandbox keys work on trial).
Setting up an API Key
- Sign in as a PandaDoc Org Admin.
- Open the Developer Dashboard Configuration page.
- Generate a Sandbox or Production API key. Production keys require PandaDoc approval.
- Paste the key into Willow.
PandaDoc documents that List Members is only exposed upon request. If the tool returns 404, ask your PandaDoc Account Manager to enable GET /public/v1/members. Keys that are not Org Admin return 403.
Available Tools
- List Members —
GET /public/v1/members. Returns members of the workspace implied by the key. Each row'sworkspaceis that member's currently active workspace, which can differ from the key's workspace. Fields includeemail,is_active,role,user_license,membership_id, andworkspace. - Remove Member —
DELETE /public/v1/workspaces/{workspace_id}/members/{member_id}. Passworkspaceasworkspace_idandmembership_idfrom List Members. To remove someone from every workspace, call once per membership. Workspace owners cannot be removed (400). This does not release the org license.
Troubleshooting
403 on List Members or Remove Member
Cause: The API key was generated by a non–Org Admin, or the user lacks the required license.
Solution: Recreate the key while signed in as an Org Admin.
404 on List Members
Cause: The members endpoint is not enabled for the account.
Solution: Ask your PandaDoc Account Manager to expose GET /public/v1/members.
400 Owner can not be removed
Cause: The target is the workspace owner.
Solution: Transfer ownership in the PandaDoc UI first, then remove the member.
Key stopped working after a user left
Cause: API keys are deactivated when the generating user is removed from the workspace.
Solution: Generate a new key as a long-lived Org Admin account.