home / skills / composiohq / awesome-claude-skills / pandadoc-automation

pandadoc-automation skill

/pandadoc-automation

This skill automates PandaDoc workflows from the terminal, creating documents, managing contacts, folders, webhooks, templates, and status tracking.

npx playbooks add skill composiohq/awesome-claude-skills --skill pandadoc-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

6.9 KB

---
name: PandaDoc Automation
description: "Automate document workflows with PandaDoc -- create documents from files, manage contacts, organize folders, set up webhooks, create templates, and track document status through the Composio PandaDoc integration."
requires:
  mcp:
    - rube
---

# PandaDoc Automation

Manage **PandaDoc** document workflows directly from Claude Code. Create documents from uploaded files, manage recipients and contacts, organize with folders, set up event webhooks, create templates, and track document status without leaving your terminal.

**Toolkit docs:** [composio.dev/toolkits/pandadoc](https://composio.dev/toolkits/pandadoc)

---

## Setup

1. Add the Composio MCP server to your configuration:
   ```
   https://rube.app/mcp
   ```
2. Connect your PandaDoc account when prompted. The agent will provide an OAuth link to authenticate.
3. Ensure your PandaDoc workspace has the appropriate plan for the features you need (e.g., e-signatures, templates, webhooks).

---

## Core Workflows

### 1. Create a Document from File

Upload a PDF, DOCX, or RTF file to create a new PandaDoc document with designated recipients for signing and tracking.

**Tool:** `PANDADOC_CREATE_DOCUMENT_FROM_FILE`

Key parameters:
- `name` (required) -- document name
- `recipients` (required) -- array of recipient objects, each with:
  - `email` (required) -- recipient email
  - `first_name`, `last_name` -- recipient name
  - `role` -- `signer` (default), `approver`, or `cc` (must be unique per recipient)
  - `signing_order` -- numeric order (if set for one, must be set for all)
- `file` -- uploaded file object with `name`, `mimetype`, and `s3key`
- `url` -- alternatively, a public HTTPS URL to the file
- `parse_form_fields` (default false) -- parse PDF form fields
- `tags` -- array of strings for categorization
- `owner` -- document owner (email or membership_id)

Example prompt: *"Create a PandaDoc document from contract.pdf with [email protected] as signer and [email protected] as approver"*

---

### 2. Get Document Details

Fetch comprehensive metadata for a document including recipients, fields, tokens, pricing, tags, and content-block references.

**Tool:** `PANDADOC_GET_DOCUMENT_DETAILS`

Key parameters:
- `id` (required) -- the unique document identifier (e.g., `BhVzRcxH9Z2LgfPPGXFUqa`)

Use this to check document status, inspect recipient completion, review field values, or gather metadata for reporting.

Example prompt: *"Get the full details and status for PandaDoc document BhVzRcxH9Z2LgfPPGXFUqa"*

---

### 3. Manage Contacts

Create new contacts or update existing ones in PandaDoc. Contacts are matched by email -- if a contact with the given email exists, it gets updated; otherwise, a new one is created.

**Tool:** `PANDADOC_CREATE_OR_UPDATE_CONTACT`

Key parameters:
- `email` (required) -- contact email address
- `first_name`, `last_name` -- contact name
- `company` -- company name
- `job_title` -- role/title
- `phone` -- phone number
- `street_address`, `city`, `state`, `postal_code`, `country` -- address fields

Example prompt: *"Create a PandaDoc contact for [email protected] at Acme Corp as Software Engineer"*

---

### 4. Organize with Folders

Create folders and move documents to organize your PandaDoc workspace.

**Tools:** `PANDADOC_CREATE_FOLDER`, `PANDADOC_LIST_DOCUMENT_FOLDERS`, `PANDADOC_MOVE_DOCUMENT_TO_FOLDER`

For creating folders:
- `name` (required) -- folder name
- `parent_uuid` -- parent folder UUID for nested structures

Example prompt: *"Create a 'Q1 2026 Contracts' folder in PandaDoc and move document BhVzRcxH9Z to it"*

---

### 5. Set Up Webhooks

Create webhook subscriptions to receive real-time notifications when document events occur.

**Tool:** `PANDADOC_CREATE_WEBHOOK`

Key parameters:
- `name` (required) -- descriptive name for the webhook
- `url` (required) -- endpoint URL for notifications
- `triggers` (required) -- event types: `document_state_changed`, `recipient_completed`, `document_updated`, etc.
- `active` (default true) -- enable/disable the webhook
- `payload` -- additional data to include: `fields`, `products`, `metadata`, `tokens`, `pricing`

Example prompt: *"Set up a PandaDoc webhook to notify https://api.example.com/hooks when documents change state or recipients complete"*

---

### 6. Create Templates

Create reusable templates from PDF files or from scratch with structured content blocks.

**Tool:** `PANDADOC_CREATE_TEMPLATE`

Key parameters:
- `name` (required) -- template name
- `file_path` -- path to PDF file for template creation
- `content` -- structured content object with `title` and `blocks` array for building from scratch
- `description` -- template description
- `tags` -- categorization tags

Example prompt: *"Create a PandaDoc template called 'Standard NDA' from the nda-template.pdf file"*

---

## Known Pitfalls

- **Unique recipient roles:** PandaDoc API does not allow duplicate roles within a single document. Each recipient must have a unique `role` value (e.g., `signer`, `signer_2`, `approver`, `cc`).
- **Signing order consistency:** If you specify `signing_order` for any recipient, you must specify it for ALL recipients in the document. Partial ordering will cause errors.
- **File upload requirements:** Either `file` (with `s3key`) or `url` must be provided for document creation, not both. The URL must be publicly accessible HTTPS.
- **Contact upsert behavior:** `PANDADOC_CREATE_OR_UPDATE_CONTACT` matches by email. If you need to update a contact's email itself, you must create a new contact and handle the old one separately.
- **Document ID format:** Document IDs are alphanumeric strings (e.g., `BhVzRcxH9Z2LgfPPGXFUqa`). They are returned when documents are created and can be found via the PandaDoc dashboard.
- **Webhook event naming:** Trigger event names must match exactly (e.g., `document_state_changed`, not `stateChanged` or `state_changed`). Check PandaDoc API docs for the complete list.
- **Folder operations require UUIDs:** Moving documents requires both the document ID and the destination folder UUID. List folders first to get the correct UUID.
- **Template content blocks:** When creating templates from scratch, the `blocks` array must contain valid content block objects per PandaDoc's schema. Check their API documentation for supported block types.

---

## Quick Reference

| Tool Slug | Description |
|---|---|
| `PANDADOC_CREATE_DOCUMENT_FROM_FILE` | Create a document from PDF/DOCX/RTF with recipients |
| `PANDADOC_GET_DOCUMENT_DETAILS` | Get full document metadata, status, and fields |
| `PANDADOC_CREATE_OR_UPDATE_CONTACT` | Create or update a contact by email |
| `PANDADOC_CREATE_FOLDER` | Create a folder for document organization |
| `PANDADOC_LIST_DOCUMENT_FOLDERS` | List all document folders |
| `PANDADOC_MOVE_DOCUMENT_TO_FOLDER` | Move a document to a specific folder |
| `PANDADOC_CREATE_WEBHOOK` | Set up event notification webhooks |
| `PANDADOC_CREATE_TEMPLATE` | Create a reusable document template |

---

*Powered by [Composio](https://composio.dev)*

Overview

This skill automates PandaDoc document workflows directly from an agent environment. It creates documents from files or URLs, manages contacts and folders, sets up webhooks, builds templates, and retrieves detailed document status for tracking and reporting. Use it to reduce manual steps and keep document lifecycle actions reproducible and auditable.

How this skill works

The skill exposes toolkit actions that call PandaDoc endpoints via an authenticated Composio integration. Actions include creating documents from uploaded files or public URLs, upserting contacts by email, creating and organizing folders, registering webhook subscriptions, and building templates from files or structured content. After creation, the skill can fetch full document metadata and status so you can programmatically monitor progress and trigger downstream automation.

When to use it

Automate contract creation and delivery from uploaded PDFs or DOCX files
Maintain an up-to-date contact list by creating or updating contacts programmatically
Organize documents into folders as part of billing, legal, or quarterly workflows
Receive real-time updates via webhooks for document state changes and recipient completion
Create reusable templates for frequently used agreements to standardize document generation
Extract document metadata and field values for reporting or CRM syncs

Best practices

Ensure recipients have unique role identifiers and provide signing_order for all recipients if used
Provide either an uploaded file (s3key) or a publicly accessible HTTPS URL — not both
List folders first to retrieve folder UUIDs before moving documents to avoid errors
When creating webhooks, use exact trigger names (e.g., document_state_changed) to ensure events fire
Test template blocks and parsed form fields in a staging workspace before production use
When updating contact emails, create a new contact rather than relying on email upsert to rename entries

Example use cases

Create a signed sales contract from [email protected]’s uploaded PDF, assign signer and approver, and move the document into a Q1 folder
Upsert new hires into PandaDoc as contacts and generate onboarding documents from a template
Set a webhook to notify your backend when a document reaches the signed state and then trigger an invoice creation workflow
Build a reusable NDA template from a PDF and then generate one-off NDAs populated with recipient info
Fetch a document’s metadata and field values to populate CRM fields and track signature completion

FAQ

How do I upload a file vs. provide a URL when creating a document?

Provide either a file object with name, mimetype, and s3key for uploaded files, or supply a publicly accessible HTTPS URL to the file. Do not provide both.

What happens when I create or update a contact with an existing email?

The action matches by email and updates the existing contact. To change an email address, create a new contact and handle the old record separately.