> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to PandaDoc

The PandaDoc connector lets your AI agent act in each user's PandaDoc account. Each user signs in to PandaDoc once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 91 tools.

**Authentication:** OAuth 2.0
**Categories:** Files & Documents, CRM & Sales
**Tools:** 91: 44 read, 38 write, 9 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own PandaDoc app
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=PANDADOC)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the PandaDoc connection

   In **AgentKit > Connections**, create a PandaDoc connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   PandaDoc connections use your own OAuth app. Register one with PandaDoc and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the PandaDoc connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'pandadoc'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize PandaDoc:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'pandadoc_catalog_items_search',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "pandadoc"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize PandaDoc:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="pandadoc_catalog_items_search",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'pandadoc_catalog_item_get',
  toolInput: {
    item_uuid: '<item_uuid>',
  },
  connector: 'pandadoc',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="pandadoc_catalog_item_get",
    tool_input={
        "item_uuid": "<item_uuid>",
    },
    connection_name="pandadoc",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `pandadoc_catalog_item_get`

Catalog Item Details · Read-only

Get the details of a single product catalog item by its UUID, including title, pricing configuration, variants, category, and bundle items (if any).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `item_uuid` (`string`, required): The UUID of the catalog item to retrieve.

Example input: `{"item_uuid":"<item_uuid>"}`

### `pandadoc_catalog_items_search`

List Catalog Items Search · Read-only

Search for items in your product catalog. The query parameter searches title, SKU, description, category name, and custom field names/values. Supports filtering by item type, billing type, category, excluded UUIDs, and sorting by SKU, name, price, or modification date. Returns a paginated list of catalog items with pricing, images, and tier information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `billing_types` (`string`, optional): Comma-separated list of billing types to filter by. Valid values: one_time, recurring.
- `category_id` (`string`, optional): Filter items belonging to this category id.
- `exclude_uuids` (`string`, optional): Comma-separated list of item UUIDs to exclude from the search results.
- `no_category` (`boolean`, optional): If true, return only items that do not belong to any category.
- `order_by` (`string`, optional): Sort order for results. One of: `sku`, `-sku`, `title`, `-title`, `price`, `-price`, `date_modified`, `-date_modified`.
- `page` (`integer`, optional): Page number of results to fetch. Default: `1`.
- `per_page` (`integer`, optional): Number of items to return per page. Default: `10`.
- `query` (`string`, optional): Search query matched against title, SKU, description, category name, and custom field names/values.
- `types` (`string`, optional): Comma-separated list of catalog item types to filter by. Valid values: regular, bundle.

Example input: `{}`

### `pandadoc_contact_get`

Contact Details · Read-only

Retrieve the details of a single PandaDoc contact by its id. Returns the contact object including email, name, company, job title, phone, and address fields.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of the contact to retrieve.

Example input: `{"id":"<id>"}`

### `pandadoc_contacts_list`

List Contacts · Read-only

List contacts associated with your PandaDoc workspace. Optionally filter by an exact email address match. Returns an array of contact objects (id, email, first_name, last_name, company, job_title, phone, country, state, street_address, city, postal_code).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): Filter contacts by an exact email address match. Leave blank to list all contacts.

Example input: `{}`

### `pandadoc_content_library_item_get_details`

Content Library Item Details · Read-only

Retrieve detailed information about a specific PandaDoc Content Library Item (CLI) by its ID, including roles, fields with values, tokens with values, pricing information (pricing tables, products), metadata, tags, and modification timestamps.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the Content Library Item to retrieve details for.

Example input: `{"id":"<id>"}`

### `pandadoc_content_library_item_get_status`

Content Library Item Status · Read-only

Retrieve the current processing status of a PandaDoc Content Library Item (CLI) by ID. Statuses: cli.UPLOADED (upload in progress, will transition to PROCESSED), cli.PROCESSED (successfully created and fully editable), cli.ERROR (upload failed). Use this to confirm a CLI is ready before invoking other CLI methods.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the Content Library Item to check the status of.

Example input: `{"id":"<id>"}`

### `pandadoc_content_library_items_list`

List Content Library Item · Read-only

List and search PandaDoc content library items. Supports filtering by ID, folder, tag, deletion status, and a free-text name search, plus pagination. Returns a paginated array of content library item summaries (id, name, dates, version).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of content library items to return per page. Default 50, maximum 100. Default: `50`.
- `deleted` (`boolean`, optional): If true, return only deleted (soft-deleted) content library items instead of active ones.
- `folder_uuid` (`string`, optional): The UUID of the folder where the content library items are stored.
- `item_id` (`string`, optional): Search for a specific content library item by its id.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `q` (`string`, optional): Search query. Filter by content library item name.
- `tag` (`string`, optional): Search tag. Filter by content library item tag.

Example input: `{}`

### `pandadoc_document_attachment_download`

Download Document Attachment · Read-only

Download the binary content of a PandaDoc document attachment by its attachment ID. The response is the raw file bytes (not JSON) — for text-like attachments this will be readable, for other formats (PDF, images, etc.) it will be binary data. Use the attachment ID from the document's attachment list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `attachment_id` (`string`, required): The attachment UUID to download.
- `id` (`string`, required): The document UUID that owns the attachment.

Example input: `{"attachment_id":"<attachment_id>","id":"<id>"}`

### `pandadoc_document_attachment_get_details`

Document Attachment Details · Read-only

Retrieve details of a specific attachment on a PandaDoc document, including its UUID, creation date, creator details, and file name.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `attachment_id` (`string`, required): The UUID of the attachment to retrieve.
- `id` (`string`, required): The UUID of the document that owns the attachment.

Example input: `{"attachment_id":"<attachment_id>","id":"<id>"}`

### `pandadoc_document_attachments_list`

List Document Attachments · Read-only

List all attachments on a PandaDoc document. Returns each attachment's UUID, creation date, creator details, and file name.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID of the document whose attachments should be listed.

Example input: `{"id":"<id>"}`

### `pandadoc_document_audit_trail_list`

List Document Audit Trail · Read-only

Retrieve the full audit trail for a PandaDoc document, including detailed user actions such as sending, viewing, signing, and editing, along with metadata like timestamps, IP addresses, and user identity. Accessible to authorized workspace administrators only. Supports pagination via limit/offset.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): Unique identifier of the document to retrieve the audit trail for.
- `limit` (`integer`, optional): Maximum number of items to return. Default 20, maximum 100. Default: `20`.
- `offset` (`integer`, optional): Number of items to skip before starting to collect the result set. Default 0. Default: `0`.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_download`

Document Download · Read-only

Download a PDF copy of the document identified by id. The response is a binary PDF file, not JSON — save it to disk rather than parsing it as JSON. Optionally apply a text watermark (color, font size, opacity, text) and request the document bundle as a zip of separate per-section PDFs. May return 202 if the PDF is still being generated (retry shortly) or 409 if the document is not in a downloadable state.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique id of the document to download.
- `separate_files` (`boolean`, optional): Download the document bundle as a zip archive of separate PDFs, one per section, instead of a single combined PDF. Default: `false`.
- `watermark_color` (`string`, optional): HEX color code for the watermark text, e.g. #FF5733.
- `watermark_font_size` (`integer`, optional): Font size of the watermark text.
- `watermark_opacity` (`number`, optional): Opacity of the watermark, in the range 0.0-1.0.
- `watermark_text` (`string`, optional): Text to render as a watermark across the downloaded PDF.

Example input: `{"id":"<id>"}`

### `pandadoc_document_download_protected`

Download Completed Document · Read-only

Download the final, audit-trail-protected PDF of a completed document identified by id. The response is a binary PDF file, not JSON — save it to disk rather than parsing it as JSON. Optionally request the bundle as a zip of separate per-section PDFs. May return 202 if the PDF is still being generated (retry shortly) or 409 if the document has not yet reached a completed state.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique id of the completed document to download.
- `separate_files` (`boolean`, optional): Download the document bundle as a zip archive of separate PDFs, one per section, instead of a single combined PDF. Default: `false`.

Example input: `{"id":"<id>"}`

### `pandadoc_document_esign_disclosure`

Document eSign Disclosure · Read-only

Retrieve the current version of the eSign disclosure text configured for a specified PandaDoc document. Returns whether the eSign disclosure feature is enabled, the company name, and the disclosure text (HTML) shown to signers.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The UUID of the document to retrieve the eSign disclosure text for.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_fields_list`

List Document Fields · Read-only

Return the list of fields for a particular PandaDoc document, including each field's UUID, type, current value, layout position, settings, and the recipient it is assigned to (if any).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The document UUID to list fields for.

Example input: `{"id":"<id>"}`

### `pandadoc_document_folders_list`

List Documents Folders · Read-only

Get the list of folders that contain PandaDoc documents in your account. The root folder itself is not listed in the response. Supports pagination and optional filtering by parent folder.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of folders to return per page. Default is 50, maximum is 100. Default: `50`.
- `page` (`integer`, optional): Page number of results to fetch. Default: `1`.
- `parent_uuid` (`string`, optional): The UUID of the parent folder whose subfolders you want to list. Omit to list folders located in the root folder.

Example input: `{}`

### `pandadoc_document_get_details`

Document Details · Read-only

Retrieve full details of a PandaDoc document by its id, including recipients, fields, pricing tables, tokens, metadata, tags, and grand totals. The document must not be in an uploaded/processing state (a 409 is returned if details are not yet available). Use the Document Status tool first to confirm the document has reached document.draft or later.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique id of the document to fetch details for.

Example input: `{"id":"<id>"}`

### `pandadoc_document_get_status`

Document Status · Read-only

Retrieve the current status of a PandaDoc document by its id, e.g. document.draft, document.sent, document.completed. Also returns basic metadata (name, dates, version, uuid, links). Use this to poll a newly created document until it transitions out of document.uploaded into document.draft before further operations.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique id of the document to look up.

Example input: `{"id":"<id>"}`

### `pandadoc_document_linked_objects_list`

List Linked Objects · Read-only

List all CRM objects (e.g. deals, contacts) linked to a specific PandaDoc document. Returns each linked object's link id, CRM provider, entity type, and entity id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID of the document whose linked objects should be listed.

Example input: `{"id":"<id>"}`

### `pandadoc_document_reminder_get_settings`

Document Auto Reminder Settings · Read-only

Retrieve the current auto-reminder configuration for a specified PandaDoc document, including whether reminders are enabled, delivery method (email/sms), initial delay in days, and recurrence settings. Returns a 400 error if the document is in a final state (e.g., completed, paid, declined, or expired).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The UUID of the document to retrieve auto-reminder settings for.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_reminder_get_status`

Document Auto Reminder Status · Read-only

Retrieve the auto-reminder status for a PandaDoc document. Returns, for each recipient with an active auto-reminder, their recipient_id and reminder status (sent, error, or scheduled).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The UUID of the document to check auto-reminder status for.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_section_get`

Document Section Details · Read-only

Retrieve details (UUID, name, and parent document UUID) for a single document section.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The ID of the document the section belongs to.
- `section_id` (`string`, required): The ID of the section to retrieve.

Example input: `{"document_id":"<document_id>","section_id":"<section_id>"}`

### `pandadoc_document_section_upload_status`

Document Section Upload Status · Read-only

Poll the status of an asynchronous document section upload (created via Create Document Section). Returns the upload's status, which becomes 'document_sections_upload.PROCESSED' once processing completes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The ID of the document the section upload belongs to.
- `upload_id` (`string`, required): The ID of the upload, returned by the Create Document Section (or from file upload) call.

Example input: `{"document_id":"<document_id>","upload_id":"<upload_id>"}`

### `pandadoc_document_sections_list`

List Document Sections · Read-only

Retrieve information about the sections (bundled sub-documents) within a PandaDoc document. Returns each section's UUID and name.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The ID of the document to list sections for.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_settings_get`

Get Document Settings · Read-only

Retrieve the settings for a specified PandaDoc document, including language, whether a Qualified Electronic Signature (QES) is required, expiration in days, and whether Suggest Edits (redlining) is enabled.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): Unique identifier of the document to retrieve settings for.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_documents_list`

List Documents · Read-only

List and search PandaDoc documents. Supports filtering by template, form, folder, contact, status, tag, metadata-derived free text search, and created/modified/completed date ranges, plus pagination and sorting. Returns a paginated array of document summaries (id, name, status, dates, version).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `completed_from` (`string`, optional): Only return documents with date_completed on or after this ISO 8601 datetime.
- `completed_to` (`string`, optional): Only return documents with date_completed before this ISO 8601 datetime.
- `contact_id` (`string`, optional): Filter by recipient or approver contact_id.
- `count` (`integer`, optional): Number of documents to return per page. Default 50, maximum 100. Default: `50`.
- `created_from` (`string`, optional): Only return documents with date_created on or after this ISO 8601 datetime.
- `created_to` (`string`, optional): Only return documents with date_created before this ISO 8601 datetime.
- `deleted` (`boolean`, optional): If true, return only deleted (soft-deleted) documents instead of active ones.
- `document_id` (`string`, optional): Search for a specific document by its id.
- `folder_uuid` (`string`, optional): Filter by the folder where the documents are stored.
- `form_id` (`string`, optional): Filter by parent form. Cannot be used together with template_id.
- `membership_id` (`string`, optional): Filter documents by the owner's membership_id.
- `modified_from` (`string`, optional): Only return documents with date_modified on or after this ISO 8601 datetime.
- `modified_to` (`string`, optional): Only return documents with date_modified before this ISO 8601 datetime.
- `order_by` (`string`, optional): Sort field for the results. Prefix with '-' for descending order (e.g. '-date_created'). Defaults to 'date_status_changed'. One of: `name`, `date_created`, `date_status_changed`, `date_of_last_action`, `date_modified`, `date_sent`, `date_completed`, `date_expiration`, `date_declined`, `status`, `-name`, `-date_created`, `-date_status_changed`, `-date_of_last_action`, `-date_modified`, `-date_sent`, `-date_completed`, `-date_expiration`, `-date_declined`, `-status`. Default: `date_status_changed`.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `q` (`string`, optional): Filter documents by name or reference number (stored on the template level).
- `status` (`integer`, optional): Filter documents by status code: 0=draft, 1=sent, 2=completed, 3=uploaded, 4=error, 5=viewed, 6=waiting_approval, 7=approved, 8=rejected, 9=waiting_pay, 10=paid, 11=voided, 12=declined, 13=external_review, 14=scheduled. One of: `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`, `12`, `13`, `14`.
- `status_ne` (`integer`, optional): Exclude documents with this status code. Same code mapping as Status: 0=draft, 1=sent, 2=completed, 3=uploaded, 4=error, 5=viewed, 6=waiting_approval, 7=approved, 8=rejected, 9=waiting_pay, 10=paid, 11=voided, 12=declined, 13=external_review, 14=scheduled. One of: `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`, `12`, `13`, `14`.
- `tag` (`string`, optional): Filter documents by tag.
- `template_id` (`string`, optional): Filter by parent template. Cannot be used together with form_id.

Example input: `{}`

### `pandadoc_documents_list_by_linked_object`

List Documents by Linked Object · Read-only

List PandaDoc documents that are linked to a specific CRM entity (e.g. a HubSpot deal or a Pipedrive deal). Requires the entity's id, entity type, and CRM provider name; supports optional sorting and filtering by owner.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `entity_id` (`string`, required): The unique identifier of the linked CRM entity, e.g. from a HubSpot deal URL.
- `entity_type` (`string`, required): The type of the linked entity (e.g. 'deal'). See https://developers.pandadoc.com/reference/link-service#examples-of-the-most-popular-crms for available entity types.
- `provider` (`string`, required): The CRM provider name (lowercase), e.g. 'hubspot' or 'pipedrive'. See https://developers.pandadoc.com/reference/link-service#examples-of-the-most-popular-crms for available providers.
- `order_by` (`string`, optional): Sort field for results. Defaults to '-date_created' (most recently created first). Default: `-date_created`.
- `owner_ids` (`array`, optional): Filter results to documents owned by one or more of these membership (owner) IDs.

Example input: `{"entity_id":"<entity_id>","entity_type":"deal","provider":"hubspot"}`

### `pandadoc_forms_list`

List Forms · Read-only

Retrieve a paginated list of PandaDoc forms with optional filtering by status and name, and sorting options. Returns form id, name, dates, and status.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `asc` (`boolean`, optional): Sort results in ascending order when true, descending when false.
- `count` (`integer`, optional): Number of forms to return per page. Default is 50, maximum is 100. Default: `50`.
- `name` (`string`, optional): Filter forms by name (exact or partial match on the form's name).
- `order_by` (`string`, optional): Field to sort the forms dataset by. One of: `name`, `responses`, `status`, `created_date`, `modified_date`.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `status` (`array`, optional): Filter forms by one or more statuses: draft, active, or disabled.

Example input: `{}`

### `pandadoc_member_get`

Member Details · Read-only

Retrieve a member's details by membership id, including user_id, email, name, active status, workspace, role, user license, and creation/modification dates.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The membership id of the member to retrieve.

Example input: `{"id":"<id>"}`

### `pandadoc_member_get_current`

Current Member Details · Read-only

Return the member details of the current user (the owner of the API key), including user_id, membership_id, email, name, active workspace, role, user license, and creation/modification dates.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pandadoc_members_list`

List Members · Read-only

Retrieve all member details for the workspace implied by the OAuth token. For each member, the workspace field shows their currently active workspace, which can differ from the workspace implied by the authenticated token. Returns an array of member objects (user_id, membership_id, email, first_name, last_name, is_active, workspace, workspace_name, email_verified, role, user_license, date_created, date_modified). This endpoint takes no parameters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pandadoc_notaries_list`

List Notaries · Read-only

Retrieve a list of notaries associated with your organization. Requires the Notary add-on to be enabled. Notaries can currently only be added to an organization manually through the PandaDoc Notary UI. Supports filtering by status and commission state, sorting, and pagination.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `commission_state` (`string`, optional): Comma-separated list of commission states to filter by, e.g. 'California,Arizona'.
- `limit` (`integer`, optional): Maximum number of results to return. Defaults to 50, maximum 100. Default: `50`.
- `offset` (`integer`, optional): Number of results to skip. Defaults to 0. Default: `0`.
- `order_by` (`string`, optional): Sort field. Prefix with '-' for descending order. Defaults to 'email'. One of: `email`, `-email`, `status`, `-status`, `name`, `-name`. Default: `email`.
- `status` (`string`, optional): Comma-separated list of statuses to filter by. Valid values: INVITED, UNDER_REVIEW, ACTIVE, REJECTED, INACTIVE.

Example input: `{}`

### `pandadoc_notarization_request_get`

Notarization Request Details · Read-only

Get details about a notarization request by its id, including status, creator, invitees, signed documents (with download links, available only once COMPLETED), session recording info, timestamps, and termination reason/details if the session did not complete successfully. Signed document and recording links expire in 1 hour.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session_request_id` (`string`, required): The unique identifier (UUID) of the notarization request.

Example input: `{"session_request_id":"<session_request_id>"}`

### `pandadoc_notarization_requests_list`

List Notarization Requests · Read-only

Retrieve a paginated list of notarization requests for your organization. Requires the Notary On-Demand or Notary add-on. By default only returns requests created by the API key owner, unless they have the 'Can view any notarization request' permission. Supports filtering by status, creator, or document, and sorting.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created_by_user_id` (`string`, optional): Comma-separated list of creator user IDs to filter by.
- `document_id` (`string`, optional): Comma-separated list of document IDs to filter by.
- `limit` (`integer`, optional): Maximum number of results to return. Defaults to 50, maximum 100. Default: `50`.
- `offset` (`integer`, optional): Number of results to skip. Defaults to 0. Default: `0`.
- `order_by` (`string`, optional): Sort field. Prefix with '-' for descending order. Defaults to 'date_created' ascending. One of: `status`, `-status`, `date_created`, `-date_created`, `date_completed`, `-date_completed`. Default: `date_created`.
- `status` (`string`, optional): Comma-separated list of statuses to filter by. Valid values: DRAFT, SENT, WAITING_FOR_NOTARY, ACCEPTED, LIVE, COMPLETED, INCOMPLETE, CANCELLED.

Example input: `{}`

### `pandadoc_sms_opt_outs_list`

Recent SMS Opt-out · Read-only

List recent SMS communication preference changes (opt-in/opt-out) for phone numbers associated with PandaDoc documents, optionally filtered by a date/time range. Returns an array of phone_number, status ('opt-in' or 'opt-out'), and the timestamp the status changed.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `timestamp_from` (`string`, optional): Only return opt-out/opt-in changes on or after this ISO 8601 datetime.
- `timestamp_to` (`string`, optional): Only return opt-out/opt-in changes before this ISO 8601 datetime.

Example input: `{}`

### `pandadoc_template_folders_list`

List Templates Folders · Read-only

List the folders that contain Templates in your PandaDoc account. Optionally filter by parent folder UUID and paginate results. The root folder itself is not included in the response.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of template folders to return per page. Default 50, maximum 100. Default: `50`.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `parent_uuid` (`string`, optional): The UUID of the parent folder whose child folders should be listed. Omit to list folders in the root folder.

Example input: `{}`

### `pandadoc_template_get_details`

Template Details · Read-only

Get detailed information about a PandaDoc template by ID, including basic template information (name, author), roles, fields with values, tokens with values, pricing information (pricing tables, products, quotes), metadata, tags, content placeholders, and modification timestamps.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the template to retrieve details for.

Example input: `{"id":"<id>"}`

### `pandadoc_template_get_status`

Template Status · Read-only

Retrieve the current processing status of a PandaDoc template by ID. Statuses: template.UPLOADED (upload in progress, will transition to PROCESSED), template.PROCESSED (successfully created and fully editable), template.ERROR (upload failed). Use this to confirm a template is ready before invoking other template methods, such as Template Update.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the template to check the status of.

Example input: `{"id":"<id>"}`

### `pandadoc_template_settings_get`

Get Template Settings · Read-only

Retrieve the settings for a PandaDoc template. Currently only the document language setting is supported and returned (e.g. 'en-US', 'fr-FR').

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Unique identifier of the template to retrieve settings for.

Example input: `{"template_id":"<template_id>"}`

### `pandadoc_template_shares_get`

Get Template Sharing Settings · Read-only

Retrieve the sharing settings for a PandaDoc template, i.e. the list of workspace ids the template is currently shared with.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Unique identifier of the template to retrieve sharing settings for.

Example input: `{"template_id":"<template_id>"}`

### `pandadoc_templates_list`

List Templates · Read-only

List and search PandaDoc templates. Supports filtering by name search query, template ID, folder, tag(s), shared/deleted status, plus pagination. Returns a paginated array of template summaries (id, name, dates, version).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of templates to return per page. Default 50, maximum 100. Default: `50`.
- `deleted` (`boolean`, optional): If true, return only deleted (soft-deleted) templates instead of active ones.
- `fields` (`string`, optional): Additional field to include in each result. Currently only 'content_date_modified' is supported. One of: `content_date_modified`.
- `folder_uuid` (`string`, optional): Filter by the folder where the templates are stored.
- `id` (`string`, optional): Search for a specific template by its id.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `q` (`string`, optional): Filter templates by name.
- `shared` (`boolean`, optional): If true, return only templates shared with the account.
- `tag` (`array`, optional): Filter templates by one or more tags. Example: ["onboarding"].

Example input: `{}`

### `pandadoc_user_get`

Get User Details by ID · Read-only

Get details of a single user in the PandaDoc organization by their user ID. Returns email, first/last name, phone number, license, organization-owner flag, and workspace memberships (role, workspace_id, membership_id).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): The unique identifier of the user to fetch.

Example input: `{"user_id":"<user_id>"}`

### `pandadoc_users_list`

List Users · Read-only

List users in the PandaDoc organization. Supports pagination and optionally including removed users. Returns the total count and an array of users (user_id, email, first_name, last_name, phone_number, license, ownership flag, and workspace memberships).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of users to return per page. Default and maximum 50. Default: `50`.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `show_removed` (`boolean`, optional): Whether to include removed (deactivated) users in the results. Default: `true`.

Example input: `{}`

### `pandadoc_workspaces_list`

List Workspaces · Read-only

List workspaces in the PandaDoc organization. Supports free-text search on workspace name and pagination. Returns the total count and an array of workspaces (id, name, date_created, owner email).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `count` (`integer`, optional): Number of workspaces to return per page. Default 50, maximum 100. Default: `50`.
- `page` (`integer`, optional): Page number of results to fetch. Increase to page through additional results. Default: `1`.
- `q` (`string`, optional): Filter workspaces by name using a free-text search.

Example input: `{}`

### `pandadoc_catalog_item_create`

Create Catalog Item · Write

Create a new product catalog item with a title and a default price configuration (currency, price, cost, pricing method, billing type/cycle, and optional volume tiers). Optionally set a category, SKU, description, item type, custom fields, images, and bundle items (for bundle-type items). Returns the created item with its generated UUID and default price configuration.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `currency` (`string`, required): ISO 4217 currency code for the item's default price configuration.
- `pricing_method` (`integer`, required): Pricing method for the item: 0 = flat price, 1 = volume/tiered pricing. One of: `0`, `1`.
- `title` (`string`, required): The name/title of the catalog item.
- `billing_cycle` (`string`, optional): Billing cycle identifier, required when billing_type is 'recurring'.
- `billing_type` (`string`, optional): Billing type for the item's price configuration. One of: `one_time`, `recurring`. Default: `one_time`.
- `bundle_items` (`array`, optional): Items included in a bundle, used only when type is 'bundle'. Each entry is an object with 'quantity' and 'item_or_uuid' (an existing catalog item's UUID).
- `category_id` (`string`, optional): ID of the category to assign this item to.
- `cost` (`number`, optional): Cost of the item (for margin calculations).
- `custom_fields` (`array`, optional): Custom field name/value pairs for the item.
- `description` (`string`, optional): Description of the catalog item.
- `images` (`array`, optional): Images for the item. Each entry is an object with 'src' (image URL), 'order' (display order), and 'is_main' (whether it's the primary image).
- `price` (`number`, optional): Flat price of the item. Used when pricing_method is 0. Set to null if using tiered pricing.
- `sku` (`string`, optional): SKU for the item. If omitted, PandaDoc generates one automatically.
- `tiers` (`array`, optional): Volume pricing tiers, used only when pricing_method is 1. Each entry is an object with 'value' (price at that tier) and 'min_qty' (minimum quantity for the tier).
- `type` (`string`, optional): Catalog item type. Defaults to 'regular'. One of: `regular`, `bundle`. Default: `regular`.

Example input: `{"currency":"<currency>","pricing_method":0,"title":"<title>"}`

### `pandadoc_catalog_item_update`

Update Catalog Item · Write

Update an existing product catalog item (product or bundle) in PandaDoc by its item UUID. Supports updating the title, category, bundle composition, and the default product variant (SKU, description, images, custom fields, and price configuration). Returns the updated catalog item.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `item_uuid` (`string`, required): The UUID of the catalog item to update.
- `bundle_items` (`array`, optional): List of items included in the bundle. Each entry has a 'quantity' and an 'item_or_uuid' (either an existing catalog item UUID as a string, or an inline custom bundle item object). Only applicable when type is 'bundle'. Passed through as-is to the PandaDoc API.
- `category_id` (`string`, optional): UUID of the category to assign this item to, or null to remove it from its current category.
- `product_variant` (`object`, optional): The default product variant to update: sku, description, images (array of {is_main, order, src}), custom_fields (array of {name, value}), and price_configuration ({currency, price, cost, billing_type, billing_cycle, tiers, pricing_method}). Passed through as-is to the PandaDoc API.
- `title` (`string`, optional): New title for the catalog item.
- `type` (`string`, optional): Whether the item is a regular product or a bundle of other items. One of: `regular`, `bundle`.

Example input: `{"item_uuid":"<item_uuid>"}`

### `pandadoc_contact_create`

Create Contact · Write

Add a new contact into your PandaDoc contacts list. All fields are optional, but at minimum an email or name is recommended for the contact to be useful in documents. Returns the created contact object including its generated id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `city` (`string`, optional): The contact's city name.
- `company` (`string`, optional): The contact's company name.
- `country` (`string`, optional): The contact's country name.
- `email` (`string`, optional): The contact's email address.
- `first_name` (`string`, optional): The contact's first name.
- `job_title` (`string`, optional): The contact's job title.
- `last_name` (`string`, optional): The contact's last name.
- `phone` (`string`, optional): The contact's phone number.
- `postal_code` (`string`, optional): The contact's postal or ZIP code.
- `state` (`string`, optional): The contact's state or region name.
- `street_address` (`string`, optional): The contact's street address.

Example input: `{}`

### `pandadoc_contact_update`

Update Contact · Write

Update the details of an existing PandaDoc contact by its id. Note: the email address and country cannot be changed via this endpoint. Returns the updated contact object.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of the contact to update.
- `city` (`string`, optional): The contact's new city name.
- `company` (`string`, optional): The contact's new company name.
- `first_name` (`string`, optional): The contact's new first name.
- `job_title` (`string`, optional): The contact's new job title.
- `last_name` (`string`, optional): The contact's new last name.
- `phone` (`string`, optional): The contact's new phone number.
- `postal_code` (`string`, optional): The contact's new postal or ZIP code.
- `state` (`string`, optional): The contact's new state or region name.
- `street_address` (`string`, optional): The contact's new street address.

Example input: `{"id":"<id>"}`

### `pandadoc_content_library_item_create`

Create Content Library Item · Write

Create a new Content Library Item (CLI) in PandaDoc, either as an empty item or by importing a PDF from a publicly accessible HTTPS URL. If a url is provided, PandaDoc processes the PDF asynchronously; poll pandadoc_content_library_item_get_status to check when the item reaches the 'cli.PROCESSED' state.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, optional): The name of the Content Library Item.
- `url` (`string`, optional): Secure (HTTPS) and publicly accessible URL to a PDF document to import as the content library item's content. If omitted, an empty content library item is created.

Example input: `{}`

### `pandadoc_document_append_content_library_item`

Append Content Library Item to a Document · Write

Append a Content Library Item (CLI) to a PandaDoc document. Returns the list of appended CLI pages and a block name mapping (tables, pricing tables, images, texts) showing how the CLI's content block names were renamed to avoid collisions in the resulting document.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `cli_id` (`string`, required): The ID of the Content Library Item (CLI) to append to the document's first section.
- `id` (`string`, required): The ID of the document to append the Content Library Item to.
- `pages` (`array`, optional): Optional list of CLI page overrides. Each entry is an object with 'index' (0-based page index within the CLI) and 'name' (the name to apply to that page in the resulting document). Example: [{"index": 0, "name": "Introduction"}].

Example input: `{"cli_id":"<cli_id>","id":"<id>"}`

### `pandadoc_document_attachment_create`

Create Document Attachment · Write

Attach a file to a PandaDoc document by URL. PandaDoc fetches the file from the given source URL and stores it as an attachment. Optionally set a custom display name for the uploaded file.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID of the document to attach the file to.
- `source` (`string`, required): URL of the file to be attached to the document. PandaDoc will download the file from this URL.
- `name` (`string`, optional): Optional display name to set for the uploaded file. If omitted, PandaDoc derives a name from the source URL.

Example input: `{"id":"<id>","source":"<source>"}`

### `pandadoc_document_change_status`

Document Status Change · Write

Manually change the status of a PandaDoc document identified by id to one of four allowed target statuses: Completed (code 2), Paid (code 10, requires a connected payment app), Expired (code 11), or Declined (code 12). Not every transition is valid for every current status (e.g. a document already Paid cannot be changed to Expired) — an invalid transition returns 409. Optionally attach a private note explaining the change and notify recipients by email. Returns no content on success.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The unique id of the document whose status is being changed.
- `status` (`integer`, required): Numeric code for the target document status: 2=Completed (document.completed), 10=Paid (document.paid, requires a connected payment app), 11=Expired (document.voided), 12=Declined (document.declined). One of: `2`, `10`, `11`, `12`.
- `note` (`string`, optional): A private note explaining the reason for the manual status change. Not visible to recipients.
- `notify_recipients` (`boolean`, optional): If true, sends a notification email about the status change to all document recipients.

Example input: `{"id":"<id>","status":2}`

### `pandadoc_document_create`

Create Document · Write

Create a new PandaDoc document either from an existing template (provide template_uuid) or from a publicly accessible PDF URL (provide url). Exactly one of template_uuid or url must be supplied. Supports pre-filling recipients, merge fields, tokens, pricing tables, tables, images, texts, metadata, and tags. The response returns the new document in an initial 'uploaded' status; poll the Document Status tool until it becomes 'draft' before further operations.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the document to create.
- `content_placeholders` (`array`, optional): Only used when creating from a template. Array used to inject Content Library items into placeholder blocks.
- `detect_title_variables` (`boolean`, optional): Only used when creating from a template. If true, detects and replaces variables present in the document title.
- `fields` (`object`, optional): Object mapping merge field names to {"value": ...} objects to pre-fill field values (text, checkbox, date, etc).
- `folder_uuid` (`string`, optional): UUID of the folder where the new document should be stored.
- `images` (`array`, optional): Only used when creating from a template. Array of {name, urls} objects to replace image blocks by name.
- `metadata` (`object`, optional): Arbitrary key-value data to associate with the document, returned in later document detail requests.
- `owner` (`object`, optional): Object with a membership_id field identifying which workspace member owns the document, e.g. {"membership_id": "QMDSzwabfFzTgjW6KijHyu"}.
- `parse_form_fields` (`boolean`, optional): Only used when creating from a PDF url. Set true if the source PDF has AcroForm fields, false if it uses PandaDoc field tags.
- `pricing_tables` (`array`, optional): Only used when creating from a template. Array of pricing table objects to populate pricing table blocks.
- `recipients` (`array`, optional): Array of recipient objects (email, first_name, last_name, role, etc). Required when creating from template_uuid; optional when creating from a PDF url.
- `tables` (`array`, optional): Only used when creating from a template. Array of table objects to populate table blocks.
- `tags` (`array`, optional): Array of string tags to mark the document with.
- `template_uuid` (`string`, optional): The UUID of the PandaDoc template to create this document from. Required if url is not provided; cannot be combined with url.
- `texts` (`array`, optional): Only used when creating from a template. Array of {name, data} objects to replace text blocks by name.
- `tokens` (`array`, optional): Array of {name, value} objects used to initialize document variables.
- `url` (`string`, optional): A secure (HTTPS) and publicly accessible URL to a PDF document to create this document from. Required if template_uuid is not provided; cannot be combined with template_uuid.
- `use_form_field_properties` (`string`, optional): Set to 'yes', '1', or 'true' to respect PDF form field properties (like required) when uploading a PDF with form fields.

Example input: `{"name":"Copy of Sample Template"}`

### `pandadoc_document_create_editing_session`

Create Document Editing Session · Write

Create a new editing session for the PandaDoc Embedded Editor for a document that has draft status. The response includes an E-Token (token) required to open the document in the Embedded Editor. Only one editing session can be active at a time for a specific user-document pair; creating a new one invalidates the previous session. A maximum of 250 editing sessions can be created for a single document per week.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): Email address of the user to create the editing session for.
- `id` (`string`, required): The ID of the document (must be in draft status) to create the editing session for.
- `lifetime` (`integer`, optional): Lifetime of the E-Token in seconds. Minimum 60, maximum 86400. Defaults to 3600 (1 hour). Default: `3600`.

Example input: `{"email":"<email>","id":"<id>"}`

### `pandadoc_document_create_signing_session`

Create Document Session for Embedded Sign · Write

Create a document session (Embedded Sign session) for a recipient to view and sign a document. Returns a session id and expiration time that can be used to build an embedded signing link.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The ID of the document to create the signing session for.
- `recipient` (`string`, required): Email address of the recipient who will receive access to the document session.
- `lifetime` (`number`, optional): The duration in seconds for which the document session link remains valid. Defaults to 3600 (1 hour) if not specified. For security, PandaDoc recommends setting this to less than one year (e.g. 31535999). Default: `3600`.

Example input: `{"id":"<id>","recipient":"<recipient>"}`

### `pandadoc_document_fields_create`

Create Document Fields · Write

Create one or more fields (text, checkbox, date, dropdown, radio buttons, signature, etc.) on a PandaDoc document at specific page positions. Accepts an array of field definitions, each specifying the field type and layout (page, position, size). For 21 CFR Part 11 (CFR11) compliant workspaces, signature fields must be at least 108x33 in size. Returns the created fields with their assigned UUIDs.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `fields` (`array`, required): Array of field objects to place on the document. Each item requires 'type' (e.g. text, checkbox, date, dropdown, radio_buttons, signature, initials) and 'layout' (page, position {offset_x, offset_y, anchor_point}, style {width, height}). Optional per-field keys: 'field_id', 'merge_field', 'assigned_to' (recipient UUID), and 'settings' (type-specific options like required, placeholder, options list). Example: [{"type": "text", "layout": {"page": 1, "position": {"offset_x": 1, "offset_y": 1, "anchor_point": "topleft"}, "style": {"width": 1, "height": 1}}}]
- `id` (`string`, required): The document UUID to create fields on.

Example input: `{"fields":[{"type":"text","layout":{"page":1,"position":{"offset_x":1,"offset_y":1,"anchor_point":"topleft"},"style":{"width":1,"height":1}}}],"id":"<id>"}`

### `pandadoc_document_fields_update_assignment`

Update Document Fields Assignment · Write

Assign, reassign, or unassign fields on a PandaDoc document to recipients. Supports bulk operations by accepting multiple field assignment items in a single request. The document must be in 'Draft' status and you must have the 'Can Edit Document' permission. Returns no content on success.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fields` (`array`, required): Array of field assignment operations. Each item must include 'field_id' (UUID of the field) and 'assigned_to' (UUID of the recipient to assign to, or null to unassign the field). Example: [{"field_id": "d6948f39-612a-4626-a439-ca9e0cbbda7c", "assigned_to": "tf5dGS3Tmu3cj228ao6fnc"}]
- `id` (`string`, required): The document UUID whose field assignments should be updated.

Example input: `{"fields":[{"field_id":"d6948f39-612a-4626-a439-ca9e0cbbda7c","assigned_to":"tf5dGS3Tmu3cj228ao6fnc"}],"id":"<id>"}`

### `pandadoc_document_folder_create`

Create Documents Folder · Write

Create a new folder to store PandaDoc documents. Optionally nest it inside an existing folder by specifying the parent folder's UUID; omit to create a top-level folder in the root.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name for the new documents folder.
- `parent_uuid` (`string`, optional): UUID of the parent folder to create this new folder inside. Omit to create the folder at the root level.

Example input: `{"name":"Copy of Sample Template"}`

### `pandadoc_document_folder_rename`

Rename Documents Folder · Write

Rename a documents folder in PandaDoc by its UUID. Returns the updated folder object with uuid, name, and date_created.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID of the documents folder to rename.
- `name` (`string`, required): The new name to assign to the documents folder.

Example input: `{"id":"<id>","name":"Copy of Sample Template"}`

### `pandadoc_document_linked_object_create`

Create Linked Object · Write

Link a PandaDoc document to a CRM entity (e.g. a deal or contact) by specifying the CRM provider, entity type, and entity id. PandaDoc validates that the entity exists. Returns the created link's id and any child links.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `entity_id` (`string`, required): Unique identifier of the CRM entity to link. PandaDoc validates that the entity exists.
- `entity_type` (`string`, required): Entity type to link, e.g. 'deal'. See https://developers.pandadoc.com/reference/link-service#examples-of-the-most-popular-crms for available entity types.
- `id` (`string`, required): The UUID of the document to link the CRM entity to.
- `provider` (`string`, required): CRM provider name (lowercase), e.g. 'pipedrive'. See https://developers.pandadoc.com/reference/link-service#examples-of-the-most-popular-crms for available providers.

Example input: `{"entity_id":"<entity_id>","entity_type":"deal","id":"<id>","provider":"pipedrive"}`

### `pandadoc_document_move_to_folder`

Document Move to Folder · Write

Move a PandaDoc document to a folder by specifying the document ID and the destination folder ID. Returns no content on success.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `folder_id` (`string`, required): The ID of the destination folder to move the document into.
- `id` (`string`, required): The ID of the document to move.

Example input: `{"folder_id":"<folder_id>","id":"<id>"}`

### `pandadoc_document_recipient_add`

Add Document Recipient · Write

Add a CC recipient (an existing contact or contact group) to a PandaDoc document. Requires the 'Can Manage Recipients' permission, and the contact must already exist (create it first via the Create Contact tool if needed). CC recipients can be added in any document status except 'Expired' (voided) and 'Declined'. If the document has already been sent/viewed/completed/is waiting for payment/paid, the new CC recipient receives an instant email notification granting document access. Returns the new recipient's ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `contact_id` (`string`, required): The UUID of the existing contact or contact group to add as a CC recipient. Retrieve via the List Contacts tool.
- `id` (`string`, required): The document UUID to add the CC recipient to.
- `kind` (`string`, optional): Whether Contact ID refers to a single contact or a contact group. Defaults to 'contact'. One of: `contact`, `contact_group`. Default: `contact`.

Example input: `{"contact_id":"<contact_id>","id":"<id>"}`

### `pandadoc_document_recipient_reassign`

Change Signer (Reassign Document Recipient) · Write

Reassign a document recipient's fields to a different contact (change signer). Requires the 'Can Manage Recipients' permission, and the replacement contact must already exist (create it first with the Create Contact tool). You can reassign fields to another signer only before the original signer has signed; once reassigned, the original signer is entirely removed from the document (re-add them as a CC recipient if needed). If the document has already been sent, the new signer's pre-filled fields are reset; in Draft status they are preserved.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `contact_id` (`string`, required): The contact UUID of the replacement signer. Retrieve it with the List Contacts tool by searching for the contact's name or email.
- `document_id` (`string`, required): The UUID of the document containing the recipient.
- `recipient_id` (`string`, required): The UUID of the original signer's recipient record to reassign.
- `kind` (`string`, optional): The kind of entity referenced by contact_id. One of: `contact`, `contact_group`. Default: `contact`.

Example input: `{"contact_id":"<contact_id>","document_id":"<document_id>","recipient_id":"<recipient_id>"}`

### `pandadoc_document_recipient_update`

Update Document Recipient · Write

Modify a recipient's personal details (name, email, phone, company, address, etc.) on a PandaDoc document, or rename a recipient group and/or replace its members. For an individual recipient, provide any of the personal-detail fields you want to change; only provided fields are updated. For a recipient group, provide 'group_name' and/or 'group_members' (the full replacement membership list, matched by email) instead — at least one of those two must be set, and 'group_members' must contain at least one member if provided. Editable document statuses vary by recipient type; see PandaDoc docs. Returns no content on success.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The document UUID that owns the recipient.
- `recipient_id` (`string`, required): The recipient (or recipient group) UUID to update.
- `city` (`string`, optional): New city for an individual recipient.
- `company` (`string`, optional): New company name for an individual recipient.
- `country` (`string`, optional): New country for an individual recipient.
- `email` (`string`, optional): New email address for an individual recipient. Cannot be an email already used by another contact, and cannot be used to change a PandaDoc user's email.
- `first_name` (`string`, optional): New first name for an individual recipient.
- `group_members` (`array`, optional): Full replacement list of the recipient group's members. Use only when Recipient ID refers to a group. Each item is an object with 'email' (required, used to match existing members) and optionally 'first_name'/'last_name'. Members omitted from this list are removed from the group; new entries are added. Must contain at least one member if provided. Example: [{"email": "kept.member@pandadoc.com"}, {"email": "new.member@pandadoc.com", "first_name": "New", "last_name": "Member"}]
- `group_name` (`string`, optional): New name for a recipient group. Use only when Recipient ID refers to a group. Max length 120.
- `last_name` (`string`, optional): New last name for an individual recipient.
- `phone` (`string`, optional): New phone number for an individual recipient.
- `postal_code` (`string`, optional): New postal code for an individual recipient.
- `state` (`string`, optional): New state/region for an individual recipient.
- `street_address` (`string`, optional): New street address for an individual recipient.
- `title` (`string`, optional): New job title for an individual recipient.

Example input: `{"id":"<id>","recipient_id":"<recipient_id>"}`

### `pandadoc_document_reminder_update_settings`

Update Document Auto Reminder Settings · Write

Configure automatic reminders sent to recipients of a PandaDoc document after its initial dispatch. Set whether reminders are enabled, the delivery method (email/sms), the initial delay before the first reminder, and whether reminders recur (and at what frequency). Returns a 400 error if the document is in a final state (e.g., completed, paid, declined, or expired). To disable reminders, set enabled to false (other fields are then optional).

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The UUID of the document to update auto-reminder settings for.
- `enabled` (`boolean`, required): Toggles auto-reminders for the document. If true, reminders are scheduled based on the other configuration fields provided. If false, all other fields are optional.
- `delivery_method` (`string`, optional): The method used to deliver reminders. One of: email, sms. Required when enabling reminders. One of: `email`, `sms`.
- `initial_delay_days` (`integer`, optional): Number of days to wait after sending the document before the first reminder is sent. Must be between 1 and 180. Required when enabling reminders.
- `is_recurring` (`boolean`, optional): If true, reminders are sent repeatedly at the interval configured in recurrence_frequency_days after the initial reminder.
- `recurrence_frequency_days` (`integer`, optional): Number of days between recurring reminders. Applicable only when is_recurring is true. Must be between 1 and 180.

Example input: `{"document_id":"<document_id>","enabled":true}`

### `pandadoc_document_revert_to_draft`

Move Document to Draft · Write

Revert a PandaDoc document back to draft status so it can continue to be edited. Works for any document status except Removed. Signature and Initials fields are cleared (all other fields stay filled in). Recipients are NOT notified, so the document must be resent for recipients to sign the updated version.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the document to revert to draft status.

Example input: `{"id":"<id>"}`

### `pandadoc_document_section_upload`

Create Document Section · Write

Add a new section (bundle) to an existing PandaDoc document, either from a PandaDoc template (set template_uuid) or from a file reachable by a public HTTPS URL (set url). Exactly one of template_uuid or url must be provided. This is an asynchronous operation: a successful call returns an upload record with status 'document_sections_upload.UPLOADED'; poll the Document Section Upload Status tool until it becomes 'document_sections_upload.PROCESSED'. Pricing tables and content placeholders are not supported by this tool.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `document_id` (`string`, required): The ID of the document to add the section to.
- `recipients` (`array`, required): The list of recipients for the section. Each object must include email; role, first_name and last_name are optional. If role is passed, that person is assigned all fields matching their role; otherwise they receive a read-only link.
- `fields` (`object`, optional): Field name/value pairs to pre-fill fields used in a template. Signature fields cannot be pre-filled.
- `merge_field_scope` (`string`, optional): Determines how the fields/tokens are mapped when creating a section: 'document' updates fields across the entire document (default); 'upload' only updates fields from the created section, appending the merge field with the upload ID. One of: `document`, `upload`. Default: `document`.
- `name` (`string`, optional): Name for the new section.
- `parse_form_fields` (`boolean`, optional): Set true when creating a section from a PDF with form fields, or false when uploading a PDF with field tags. Only relevant when using url.
- `tags` (`array`, optional): One or more tags to mark the section's document with.
- `template_uuid` (`string`, optional): The ID of the PandaDoc template to create the section from. Provide either this or url, not both.
- `tokens` (`array`, optional): List of token (variable) name/value pairs to pre-fill tokens used in a template.
- `url` (`string`, optional): Secure (HTTPS) and publicly accessible URL to a PDF, DocX, or RTF file to create the section from. Provide either this or template_uuid, not both.

Example input: `{"document_id":"<document_id>","recipients":[]}`

### `pandadoc_document_send`

Send Document · Write

Send a PandaDoc document (which must be in draft status) to its recipients for viewing/signing. Optionally customize the email subject and message, set a sender, control forwarding permissions, set a reply-to address, suppress notifications with silent mode, and select approvers. Returns 409 if the document is not in a sendable state and 423 if it is locked by another operation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The unique id of the document to send.
- `forwarding_settings` (`object`, optional): Controls document/signature forwarding: {"forwarding_allowed": bool, "forwarding_with_reassigning_allowed": bool}.
- `message` (`string`, optional): A message that will be sent by email with a link to the document to sign.
- `reply_to` (`string`, optional): Email address used as the reply-to address. Requires the feature to be enabled for the account by PandaDoc support.
- `selected_approvers` (`object`, optional): Configuration for selected approvers, with an array of approval steps ({id, group}).
- `sender` (`object`, optional): Sets the sender of the document as {"membership_id": "..."} or {"email": "..."}.
- `silent` (`boolean`, optional): If true, disables email notifications for recipients and the sender, and disables scheduled reminders (manual reminders still possible). Does not affect the Approve document notification.
- `subject` (`string`, optional): Value used as the email subject when the document is sent.

Example input: `{"id":"<id>"}`

### `pandadoc_document_send_manual_reminder`

Send Manual Reminder · Write

Send a manual reminder to one or more recipients of a PandaDoc document. Each recipient can be reminded via email and/or SMS (per delivery_methods), and email reminders can be customized with a subject and message. The document sender's details are used automatically in the From field of email reminders.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `document_id` (`string`, required): The UUID of the document whose recipients should receive a reminder.
- `reminders` (`array`, required): A list of reminders to send to specific recipients. Each entry specifies the recipient_id, which delivery_methods to use (email and/or sms), and an optional email_customization object (subject/message, only used when delivery_methods.email is true). Example: [{"recipient_id":"2eWSKSvVqmuVCnuUK3iWwD","delivery_methods":{"email":true,"sms":false}}]

Example input: `{"document_id":"<document_id>","reminders":[{"recipient_id":"2eWSKSvVqmuVCnuUK3iWwD","delivery_methods":{"email":true,"sms":false}}]}`

### `pandadoc_document_settings_update`

Update Document Settings · Write

Update the settings for a specified PandaDoc document: language, whether a Qualified Electronic Signature (QES) is required, document expiration in days, and whether Suggest Edits (redlining) is enabled. Suggest Edits can only be changed while the document is in 'draft' status. Only the fields you provide are updated; omitted fields are left unchanged. Returns the full updated settings object.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): Unique identifier of the document to update settings for.
- `expires_in` (`integer`, optional): Document expiration in days. Minimum is 1 day.
- `language` (`string`, optional): Document language code. One of: `en-US`, `fr-FR`, `it-IT`, `es-ES`, `nl-NL`, `de-DE`, `pt-BR`, `pt-PT`, `pl-PL`, `sv-SE`, `cs-CZ`, `da-DK`, `el-GR`, `hu-HU`, `nb-NO`, `ro-RO`, `bg-BG`.
- `qualified_electronic_signature` (`boolean`, optional): Whether the document requires a Qualified Electronic Signature (QES) during signing. If true, signers must complete the document using a third-party qualified electronic signature provider.
- `suggest_edits` (`boolean`, optional): Enables or disables Suggest Edits (redlining) for the document. Can only be changed while the document is in 'draft' status.

Example input: `{"document_id":"<document_id>"}`

### `pandadoc_document_transfer_ownership`

Update Document Ownership · Write

Transfer ownership of a PandaDoc document to another workspace member by specifying the document ID and the target member's membership_id. Returns no content on success. Use the List Members endpoint to find a valid membership_id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the document whose ownership should be transferred.
- `membership_id` (`string`, required): The unique identifier of the workspace member who will become the new owner of the document.

Example input: `{"id":"<id>","membership_id":"<membership_id>"}`

### `pandadoc_document_update`

Update Document · Write

Update fields on an existing PandaDoc document that is still in draft status: name, recipients (add or update by id/email), merge fields, tokens, tags, metadata, pricing tables, tables, images, and texts. The document must not be sent, completed, or otherwise locked (a 423 is returned if the document is locked). Returns no content on success.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique id of the document to update.
- `fields` (`object`, optional): Object mapping merge field names to {"value": ...} objects to update field values.
- `images` (`array`, optional): Array of {name, urls} objects to replace image blocks by name.
- `metadata` (`object`, optional): Arbitrary key-value data to associate with the document. Existing keys are updated, new keys are added.
- `name` (`string`, optional): New name for the document.
- `pricing_tables` (`array`, optional): Array of pricing table objects to update pricing table blocks by name.
- `recipients` (`array`, optional): Array of recipient objects. If id is passed, an existing recipient is updated; if only email is passed, a new recipient is added to CC.
- `tables` (`array`, optional): Array of table objects to update table blocks by name.
- `tags` (`array`, optional): Array of string tags to mark the document with.
- `texts` (`array`, optional): Array of {name, data} objects to replace text blocks by name.
- `tokens` (`array`, optional): Array of {name, value} objects used to create or update document variables.

Example input: `{"id":"<id>"}`

### `pandadoc_notarization_request_create`

Create Notarization Request · Write

Create a notarization request to connect with a notary and complete online notarizations for signers. Only supports documents in draft status. Requires the Notary On-Demand or Notary add-on. At least one invitee (with email) is required. Optionally assign an in-house notary (must be ACTIVE) with a scheduled time. After the call, invitees receive an email invitation unless notifications are disabled; the notarization_link is also returned in the response for direct sharing.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `document_id` (`string`, required): ID of the document (must be in draft status) to send for notarization.
- `invitees` (`array`, required): List of invitees for the notarization session. Each object requires 'email' and may include 'first_name' and 'last_name'. At least one invitee is required.
- `disable_invitees_notifications` (`boolean`, optional): If true, disables all notifications for invitees, including the invitation email. Useful when using alternative delivery methods for the notarization_link. Default: `false`.
- `invitation_message` (`string`, optional): Optional message included in the invitation email sent to invitees.
- `notary_id` (`string`, optional): ID of an ACTIVE notary to assign for an in-house (bring-your-own-notary) notarization request. If omitted, signers connect with an available on-demand commissioned notary instead. When provided, notary_scheduled_at is also required.
- `notary_message` (`string`, optional): Optional custom message for the notary, included in their invitation email. Only used when notary_id is provided.
- `notary_scheduled_at` (`string`, optional): ISO 8601 timestamp for the scheduled in-house notarization session. Required if notary_id is provided.

Example input: `{"document_id":"<document_id>","invitees":[]}`

### `pandadoc_quote_update`

Quote Update · Write

Update a PandaDoc integration quote attached to a document. Sections and their items are order-authoritative: passing 'sections' replaces the full list of sections in the order given (omitted existing sections are removed), and each section's 'items' array replaces that section's full item list (omitted existing items are removed). Include the 'id' of an existing section/item to update it in place; omit or use an unknown id to create a new one. Returns the updated quote with computed totals.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The ID of the document the quote belongs to.
- `quote_id` (`string`, required): The ID of the quote to update.
- `currency` (`string`, optional): ISO 4217 currency code for the quote (e.g. USD).
- `sections` (`array`, optional): Full ordered list of quote sections. This REPLACES all existing sections - any existing section not included here will be removed. Each section object may include: id (UUID of an existing section to update, or omit/use unknown to create new), name, summary (same shape as the top-level Summary field), items (full ordered list of section line items - same replace semantics as sections, see PandaDoc integration quote item schema for item fields like sku, name, qty, price, discounts, taxes), and settings ({optional, selected, selection_type}). Passed through as-is to the PandaDoc API.
- `settings` (`object`, optional): Quote-level settings, e.g. selection_type ('single', 'multiple', or 'custom') describing how sections can be selected. Passed through as-is to the PandaDoc API.
- `summary` (`object`, optional): Quote-level summary settings: custom_columns (map of string->string), discounts/fees/taxes (maps keyed by an arbitrary label, each value an object with 'type' (percent|flat|value) and numeric 'value'). Passed through as-is to the PandaDoc API.

Example input: `{"document_id":"<document_id>","quote_id":"<quote_id>"}`

### `pandadoc_template_create`

Create Template · Write

Create a new PandaDoc template, either as an empty (blank) template or by importing a PDF from a publicly accessible HTTPS URL. Optionally set a name, destination folder, owner, custom metadata, and initial token (variable) values. If a source url is provided, PandaDoc processes the PDF asynchronously; poll pandadoc_template_get_status with the returned id to check when the template reaches the 'template.PROCESSED' state.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `fields` (`string`, optional): Additional field to include in the response. Currently only 'content_date_modified' is supported. One of: `content_date_modified`.
- `folder_uuid` (`string`, optional): The ID of the folder where the created template should be stored.
- `metadata` (`object`, optional): Arbitrary key-value data to associate with the template. Returned in subsequent template details requests. Example: {"my_favorite_pet": "Panda"}.
- `name` (`string`, optional): The name of the template.
- `owner_email` (`string`, optional): Email address of the user to set as the template's owner. Do not combine with owner_membership_id.
- `owner_membership_id` (`string`, optional): Membership ID of the user to set as the template's owner. Do not combine with owner_email.
- `tokens` (`array`, optional): Create and initialize CUSTOM template variables (tokens) with initial values. Each item is {"name": string, "value": string}. Predefined template variables are read-only. Example: [{"name":"Favorite.Pet","value":"Panda"}].
- `url` (`string`, optional): Secure (HTTPS) and publicly accessible URL to a PDF document to import as the template's content. If omitted, an empty (blank) template is created.

Example input: `{}`

### `pandadoc_template_create_editing_session`

Create Template Editing Session · Write

Create a new editing session for the PandaDoc Embedded Editor on a template. Returns an E-Token (token field) that is required to open the template in the embedded editor. Only one active session is allowed per user-template pair; creating a new session invalidates the previous one. A maximum of 250 sessions can be created for a single template per week.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): Email address of the user to create the editing session for.
- `id` (`string`, required): The id of the template to create an editing session for.
- `lifetime` (`integer`, optional): Lifetime of the E-Token in seconds. Must be between 60 and 86400. Defaults to 3600 (1 hour). Default: `3600`.

Example input: `{"email":"<email>","id":"<id>"}`

### `pandadoc_template_duplicate`

Duplicate Template · Write

Create a copy of a PandaDoc template within the same workspace. Optionally provide a custom name for the duplicate; if omitted, a name is auto-generated from the source template. Returns the id, name, and creation date of the new template.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The id of the template to duplicate.
- `name` (`string`, optional): Custom name for the duplicated template. When omitted or empty, a name is auto-generated from the source template (e.g. 'Copy of Sample Template'). Maximum 255 characters.

Example input: `{"id":"<id>"}`

### `pandadoc_template_folder_create`

Create Templates Folder · Write

Create a new folder to store PandaDoc templates. Optionally nest it inside a parent folder by UUID. Returns the created folder's uuid, name, and date_created.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name for the new templates folder.
- `parent_uuid` (`string`, optional): UUID of the parent folder to create this folder inside of. Omit to create the folder in the root folder.

Example input: `{"name":"Copy of Sample Template"}`

### `pandadoc_template_folder_rename`

Rename Templates Folder · Write

Rename a templates folder in PandaDoc by its UUID. Returns the updated folder object with uuid, name, and date_created.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID of the templates folder to rename.
- `name` (`string`, required): The new name to assign to the templates folder.

Example input: `{"id":"<id>","name":"Copy of Sample Template"}`

### `pandadoc_template_settings_update`

Update Template Settings · Write

Update the settings for a PandaDoc template. Currently only the document language setting is supported. Returns the updated template settings.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `language` (`string`, required): Document language code to set for the template, e.g. 'en-US', 'fr-FR', 'de-DE'. One of: `en-US`, `fr-FR`, `it-IT`, `es-ES`, `nl-NL`, `de-DE`, `pt-BR`, `pt-PT`, `pl-PL`, `sv-SE`, `cs-CZ`, `da-DK`, `el-GR`, `hu-HU`, `nb-NO`, `ro-RO`, `bg-BG`.
- `template_id` (`string`, required): Unique identifier of the template to update settings for.

Example input: `{"language":"en-US","template_id":"<template_id>"}`

### `pandadoc_template_shares_update`

Update Template Sharing Settings · Write

Replace the full list of workspaces a PandaDoc template is shared with. This is a complete replacement, not a delta: pass the full desired end-state list of workspace ids. Pass an empty array to unshare the template from all workspaces. The caller must be a member of every workspace being newly shared; unsharing only requires permission to edit the template.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Unique identifier of the template whose shares are being replaced.
- `workspace_ids` (`array`, required): Complete desired list of workspace ids the template should be shared with. This replaces the prior shares entirely; duplicate ids are deduplicated. Pass an empty array to unshare from all workspaces.

Example input: `{"template_id":"<template_id>","workspace_ids":[]}`

### `pandadoc_template_update`

Template Update · Write

Update a PandaDoc template. Currently supports updating template variables (tokens) and managing template roles. The template must be in the 'template.PROCESSED' status (check with pandadoc_template_get_status first). Passing 'roles' replaces the full set of template roles in a single request: items with an existing role id update that role (name, signing_order), items without an id create a new role, and existing roles whose id is not included are deleted. Preassigned contacts/contact groups on roles are preserved on update and removed together with their role on deletion.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the template to update.
- `roles` (`array`, optional): Replace the full set of template roles. Items with an existing 'id' are updated (name, signing_order); items without an 'id' are created as new roles; existing roles whose id is not present in this list are deleted. Role names must be unique within the template. Example: [{"id":"BqL3PVsB2tPLfaSqUiQQRf","name":"Client","signing_order":1},{"name":"Manager","signing_order":2}].
- `tokens` (`array`, optional): Create or set values for CUSTOM template variables (tokens). Each item is {"name": string, "value": string}. Predefined template variables are read-only and any attempt to change them is ignored. Example: [{"name":"Favorite.Pet","value":"Panda"}].

Example input: `{"id":"<id>"}`

### `pandadoc_catalog_item_delete`

Delete Catalog Item · Destructive

Permanently delete a product catalog item from PandaDoc by its item UUID. This action cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `item_uuid` (`string`, required): The UUID of the catalog item to delete.

Example input: `{"item_uuid":"<item_uuid>"}`

### `pandadoc_contact_delete`

Delete Contact · Destructive

Permanently delete a PandaDoc contact by its id. This action cannot be undone. Returns no content on success.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The unique identifier of the contact to delete.

Example input: `{"id":"<id>"}`

### `pandadoc_document_attachment_delete`

Delete Document Attachment · Destructive

Permanently delete an attachment from a PandaDoc document by its attachment ID. This does not delete the document itself, only the attachment. Returns no content on success.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `attachment_id` (`string`, required): The attachment UUID to delete.
- `id` (`string`, required): The document UUID that owns the attachment.

Example input: `{"attachment_id":"<attachment_id>","id":"<id>"}`

### `pandadoc_document_delete`

Delete Document · Destructive

Permanently delete a PandaDoc document by ID. This is a destructive operation and cannot be undone. Returns no content on success.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the document to delete.

Example input: `{"id":"<id>"}`

### `pandadoc_document_linked_object_delete`

Delete Linked Object · Destructive

Remove a link between a PandaDoc document and a CRM entity. This does not delete the CRM entity itself, only the link record.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID of the document that owns the linked object.
- `linked_object_id` (`string`, required): The id of the linked object (link id) to delete.

Example input: `{"id":"<id>","linked_object_id":"<linked_object_id>"}`

### `pandadoc_document_recipient_delete`

Delete Document Recipient · Destructive

Remove a recipient from a PandaDoc document. Requires the 'Can Manage Recipients' permission. Removing a signer is only possible while the document is in the 'Draft' status and unassigns all fields associated with that signer. Removing a CC recipient is allowed in any status except 'Expired' or 'Declined', and revokes their access.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The UUID of the document the recipient belongs to.
- `recipient_id` (`string`, required): The UUID of the recipient to remove. This is different from the recipient's contact ID; retrieve it via the Document Details endpoint.

Example input: `{"document_id":"<document_id>","recipient_id":"<recipient_id>"}`

### `pandadoc_document_section_delete`

Delete Document Section · Destructive

Delete a section (bundle) from a PandaDoc document.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): The ID of the document the section belongs to.
- `section_id` (`string`, required): The ID of the section to delete.

Example input: `{"document_id":"<document_id>","section_id":"<section_id>"}`

### `pandadoc_notarization_request_delete`

Delete Notarization Request · Destructive

Delete a notarization request. Once deleted it cannot be restored. Only requests in status SENT, WAITING_FOR_NOTARY, or INCOMPLETE can be deleted; any other status returns a 400 Bad Request. By default all invitees receive an email notification about the deletion.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `session_request_id` (`string`, required): The unique identifier (UUID) of the notarization request to delete.

Example input: `{"session_request_id":"<session_request_id>"}`

### `pandadoc_template_delete`

Delete Template · Destructive

Permanently delete a PandaDoc template by id. This action cannot be undone. Returns no content on success (204).

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The id of the template to delete.

Example input: `{"id":"<id>"}`

## Related

Other Files & Documents connectors ([all 76](/agentkit/connectors/?category=files-documents)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Google Sheets](/agentkit/connectors/googlesheets/): Scalekit connector, OAuth, 48 tools
- [Google Drive](/agentkit/connectors/googledrive/): Scalekit connector, OAuth, 47 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
