pandadoc-approval-send

PandaDoc Approval-Routed Send

Send a document through internal approval instead of straight to the counterparty.

Verified against live chains. Reading a chain and routing a document through it were both exercised end to end: a Draft created from a template with an approval workflow exposes a populated approval_execution, and sending it lands the document in Waiting for Approval. One shape cannot be sent at all — a group whose type is selectable — and Step 3 explains why and what to do instead.

---

Prerequisites

The PandaDoc MCP Server must be connected. Required tools: PandaDoc:templates_list, PandaDoc:templates_details_get, PandaDoc:documents_create, PandaDoc:documents_status_get, PandaDoc:documents_details_get, PandaDoc:documents_send. Useful: PandaDoc:documents_update to fix an unassigned signature field before retrying a send. If they are missing, say so and point at https://mcp.pandadoc.com.

An approval workflow must be configured on the template or document in PandaDoc. This skill cannot create one: no MCP tool exposes approval-chain configuration, only reading a chain and routing a document through it. Configuring one is a UI action in PandaDoc.

---

How approvals appear in the API

PandaDoc:documents_details_get returns approval_execution. It is null when no approval workflow applies to the document. When populated it looks like this:

{
  "next_step": "<step id>",
  "is_completed": false,
  "is_ordering_enabled": true,
  "is_editing_allowed": false,
  "sender": { "email": "[email protected]", "id": "<user id>" },
  "sender_message": "Please review and approve",
  "skip_user": null,
  "skip_message": null,
  "steps": [ /* see below */ ]
}

A step comes in one of two shapes

Group step — a named group, with one or more candidate assignees:

{
  "id": "<step id>",
  "assignee": null,
  "group": {
    "id": "<group id>",
    "name": "Finance",
    "type": "optional",
    "assignees": [
      { "id": "<assignee id>", "user": { "email": "[email protected]", "id": "<user id>" }, "is_document_sender": false }
    ]
  },
  "conditions": [], "condition_operator": "or",
  "approve_user": null, "approve_message": null,
  "reject_user": null, "reject_message": null,
  "is_skipped": false, "skip_reason": null
}