add-document-recipient
ChatGPTUse this tool to add a new recipient to a document. Requirements: - At least one of email or phone must be provided.
Productivity
Overview
PandaDoc lets you create, send, and track documents for signature directly from your Claude conversation. Ask Claude to prepare an NDA from your existing templates, send a proposal to a client, check which contracts are still waiting to be signed, or pull the complete audit trail for any document. Connect your PandaDoc account to manage your entire document workflow without leaving the conversation.
Tools
assign-document-recipient-fields
ChatGPTUse this tool to assign, reassign, or remove document field assignments. Each entry maps a list of field external IDs to a recipient. Provide recipient_id to assign or change the recipient for the given fields. Omit recipient_id to remove the assignment so those fields become unassigned. In case it is unclear which recipient should be assigned to a field, ask clarifying questions based on fields present in the document. After fields are assigned to a recipient, that recipient becomes a signer and will be able to sign on the assigned fields in the document.
create-document-edit-token
ChatGPTUse this tool to obtain an editing session token (e-token) for a specific document. The token is required by the editor widget to render the document in the chat. Call this tool after document creation to initialise the editor view. If the document is not yet in draft status the tool will return an error — retry up to 3-5 times with a short delay between attempts.
create-document-from-markdown
ChatGPTCreate document from markdown in PandaDoc tool Use this tool to create a new document in PandaDoc when there is only text representing the document content. Document content must be generated according to the guidelines below. The response includes a 'link' field with a direct URL to open the created document in PandaDoc. Document creation is asynchronous. After this tool returns, the document starts in
UPLOADED status and transitions to DRAFT after some time (or to ERROR if creation fails). The document must be in DRAFT status before it can be edited or sent. Markdown guidelines You can use standard CommonMark and GitHub-Flavored Markdown (tables, strikethrough, etc), plus the following custom extensions: Custom Syntax Extensions 1. Variables Variables are placeholder values that the document creator fills in PandaDoc before sending to recipients. Prioritize variables over fields for any value that the sender controls or pre-fills, even if it may be visible to recipients. Syntax: [VariableName] or [Variable.Name] or [Multi.Part.Variable] - Can include underscores, numbers, and multiple dot-separated parts Use variables for values controlled by the document creator: - Document metadata: [Effective.Date], [Agreement.Number], [Contract.Value] - Company/sender information: [Company.Name], [Company.Address] - Pre-calculated values: [Invoice.Total], [Discount.Amount] - Recipient information already known: [Recipient.CompanyName], [Recipient.FirstName] Key principle: If the sender controls the value, use a variable. 2. Fields Fields are interactive form elements that recipients fill in or interact with during the signing process. Recipients see these as input boxes, checkboxes, or signature areas. Use fields for values controlled by the recipient: - Recipient signatures: [[signature]] - Recipient personal data they must enter: [[text]], [[email]], [[phone]], [[date]] - Recipient choices/consents: [[checkbox]] - Information only the recipient knows or decides Key principle: If the recipient controls the value, use a field. Fields can be prefilled with default values, but are typically left empty for the recipient to fill. Syntax: [[field_type attributes]] Field Types: - text - Text input field - email - Email input field - phone - Phone number input field (`format` is required — see below) - number - Number input field - date - Date input field - checkbox - Checkbox field - signature - Digital signature field - dropdown - Dropdown selection field (`option` is required — see below) Attributes (HTML-style): - required="true" - Makes field required - placeholder="text" - Placeholder text - checked="true" - Pre-checked (checkbox only) - value="timestamp" - For date fields, use UNIX timestamp with millisecond precision (e.g., value="1718406000000"). For other fields, use plain text (e.g., value="John Doe"). - format="US" or format="international" - Required for `phone` fields. Must be exactly "US" or "international". There is no default — omitting it causes a validation error. - date_format="yyyy/MM/dd" - Date format in ICU notation (e.g., "dd/MM/yyyy", "MM-dd-yyyy"). Defaults to "yyyy/MM/dd" if omitted. - option="Text" - Required for `dropdown` fields. Repeatable — add one per option (e.g., option="Yes" option="No"). To assign a stable UUID to an option, use option="uuid:Text" format. - id="Client_Text1" - Specify an external ID that describes who should fill this field and what it represents (e.g., id="Client_Signature", id="Landlord_FullName", id="Buyer_Email"). Use the pattern <RecipientRole>_<FieldPurpose> so the field can later be assigned to the correct recipient. Multiple fields MAY share the same ID (they'll be synced — when one is filled, all are filled with the same value), but they MUST have the same type and attributes. Examples: - [[text placeholder="Enter name"]] - [[email required="true" placeholder="Email address"]] - [[phone format="US"]] …create-document-from-template
ChatGPTUse this when the user wants to generate a new PandaDoc document from an existing template they have already chosen (e.g. "draft an NDA from the Standard NDA template for alice@example.com", "create a Sales Contract from template TPL-123 for these recipients"). Returns the new document's id, name, status, and links; the document is created in
document.uploaded and transitions to document.draft once PandaDoc finishes processing. Before calling this, you must know the template_uuid and have at least one recipient. If the user has not named a template, first call get-templates to find one. To discover the roles, fields, and variables the template expects, call get-template-details and map recipient roles, field values, and variable values from that schema. Do not use this to: edit an existing document (use update-document or related update tools); create a document from raw markdown (use create-document-from-markdown).delete-document-recipient
ChatGPTUse this tool to remove a recipient from a document. Requirements: - recipient_id is required — obtain it from get-document-recipients or document details.
fetch
ChatGPTFetch the full markdown content and metadata of a PandaDoc document by id or URL. Accepts an id returned by
search or a PandaDoc URL.fill-variables
ChatGPTUse this tool to fill variable values on a PandaDoc document. Variables are placeholders defined in the document that can be replaced with actual values. Provide a list of variable name/value pairs to populate.
get-audit-trail
ChatGPTFetches audit trail data for a given document id. As it is a V2 public api endpoint it requires a dedicated public api authorization token.
get-document-details
ChatGPTRetrieve full details of a specific PandaDoc document by its ID. Returns document metadata (name, status, dates, version, ref number), creator info, template, fields, variables, tags, recipients, grand total, linked objects, custom metadata, and a 'link' field with a direct URL to open the document in PandaDoc. Useful for inspecting a document after creation or before taking action on it.
get-document-status
ChatGPTUse this tool to get the status of a document in PandaDoc. This is useful after creating a document from markdown to ensure that document has been processed successfully and in DRAFT status. If the document is in UPLOADED status, retry with exponential backoff up to 3-5 times.
get-documents
ChatGPTRetrieve a paginated list of PandaDoc documents.
get-template-details
ChatGPTUse this when the user (or an upstream step) needs to inspect a specific PandaDoc template's schema — its roles, fields, variables (variables), pricing tables, content placeholders, tags, and metadata — usually as preparation for
create-document-from-template (e.g. "what roles does the Sales Contract template have?", "which variables does template TPL-123 expect?", "can I use the NDA template for an external signer?"). Returns the full template-details payload for one template id. Typical flow: call get-templates first to find the right id, then this tool to read the schema, then create-document-from-template with recipient roles, field values, and variable values mapped to that schema. Do not use this to: list/search templates (use get-templates); fetch a regular document (use get-document-details); or actually create a document (use create-document-from-template).get-templates
ChatGPTUse this when the user wants to discover, browse, or pick a PandaDoc template by name, tag, or folder (e.g. "what templates do we have?", "find the NDA template", "list templates tagged sales"). Returns a paginated list of templates with id, name, version, and timestamps. Pair a returned template id with
get-template-details to inspect roles/fields/variables, or with create-document-from-template to generate a new document. Do not use this to search documents (use get-documents), to fetch a template's roles/fields/variables (use get-template-details), or to create a document (use create-document-from-template).get-widget-context
ChatGPTReturns the widget context required by the widget to initialise. This tool is intended for widget use only.
search
ChatGPTUse this when a request requires searching the user's PandaDoc workspace for existing documents by keyword, topic, title or document context. Returns matching contracts, proposals, quotes, and other PandaDoc documents.
send-document
ChatGPTUse this tool to send document to recipients. Document must be in draft status. If the document is not in draft status, it won't be sent. After document is sent it will be moved to 'sent' status and recipients will receive notification and document will appear in recipients list.
update-document-recipient
ChatGPTUse this tool to update an existing recipient on a document. Requirements: - recipient_id is required — obtain it from get-document-recipients or document details. Constraints: - Only phone, email, first name and last name can be changed
view-document
ChatGPTUse this tool only when the user explicitly requests to open the document in the chat. Opens a DRAFT document in the editor widget so the user can interact with it directly inside the chat. Returns full document details including a 'link' field with a direct URL to open the document in PandaDoc. Don't use it automatically to refresh the document widget. Don't offer to open the document or review it after document creation.
pandadoc_documents_content_get
Claudepandadoc_documents_create
Claudepandadoc_documents_create_from_markdown
Claudepandadoc_documents_details_get
Claudepandadoc_documents_list
Claudepandadoc_documents_search
Claudepandadoc_documents_send
Claudepandadoc_documents_status_change
Claudepandadoc_documents_status_get
Claudepandadoc_documents_summary_get
Claudepandadoc_documents_update
ClaudeApp Stats
30
Tools
2
Prompts
May 6, 2026
First seen
ChatGPT, Claude
Platforms
Category
Document SigningWorks with
ChatGPT
Claude
Data refreshed daily