PandaDoc actions

The PandaDoc block creates, sends and tracks PandaDoc documents and manages templates, folders, contacts, workspaces and webhooks through the PandaDoc public API. For the plain-language guide, see PandaDoc.

When to use it

Use it to generate an order form or contract from a template when a deal closes, send it for signature, poll its status, and download the completed PDF for the customer file. There is no PandaDoc trigger; poll getDocumentStatus or listDocuments on a schedule.

Connection

Provider id: pandadoc. Two connection methods, chosen in the connect dialog (authVariant):

Select the matching account in config.connection. Without it, the step uses the company's default PandaDoc connection.

Actions

The first group is the core document flow; the rest map one-to-one to PandaDoc public API operations.

Settings

How the fields are used

• The core actions (createDocument through deleteContact) take named fields. createDocument needs templateId, or url with name. recipients is an array of { email, first_name?, last_name?, role?, signing_order? }; tokens is an array of { name, value }; pricingTables follows PandaDoc's pricing_tables shape.
• The other REST actions take the request body in data (JSON) and expose path and query parameters, such as documentId or count, as their own fields.
• listDocuments and updateDocumentStatus use PandaDoc's numeric status values. updateDocumentStatus accepts 2 (completed), 10 (paid), 11 (voided) or 12 (declined).
• sendDocument sends to the recipients already on the document. Wait for the document to reach draft status before sending.
• callMcpTool takes toolName and arguments (JSON). Call listMcpTools first to get the tool names and their input schemas.

Output

The step output is the PandaDoc response. createDocument returns the new document's id and status; read it with {{steps.create_contract.id}}. Download actions return the file as base64 content, not a URL.

Example

Create a contract from a template for a closed deal, wait for PandaDoc to prepare it, then send it.

{
  "name": "Send an order form",
  "trigger": { "type": "api" },
  "steps": [
    {
      "id": "create_contract",
      "type": "action",
      "name": "Create the order form",
      "action": "pandadoc.createDocument",
      "config": {
        "templateId": "{{input.templateId}}",
        "name": "Order form - {{input.customerName}}",
        "recipients": [
          { "email": "{{input.signerEmail}}", "first_name": "{{input.signerFirstName}}", "role": "Client" }
        ],
        "tokens": [
          { "name": "Client.Company", "value": "{{input.customerName}}" },
          { "name": "Deal.Amount", "value": "{{input.amount}}" }
        ]
      }
    },
    {
      "id": "pause",
      "type": "wait",
      "name": "Let PandaDoc prepare the document",
      "config": { "duration": 10, "unit": "seconds" }
    },
    {
      "id": "send_contract",
      "type": "action",
      "name": "Send for signature",
      "action": "pandadoc.sendDocument",
      "config": {
        "documentId": "{{steps.create_contract.id}}",
        "subject": "Your order form",
        "message": "Please review and sign."
      }
    }
  ]
}

Live catalog

• GET /api/v1/blocks/pandadoc returns the actions and fields.
• GET /api/v1/blocks/pandadoc/actions/<operation>/examples returns stored examples where they exist.

Errors and limits

• A PandaDoc API error fails the step.
• Sandbox keys have PandaDoc's own limits and recipient restrictions.
• An MCP action on an API key connection, or a REST action on an MCP connection, fails.