> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/pandadoc.md).

# PandaDoc

Connect to PandaDoc to access documents, templates, and forms. Supports document management, template creation, and e-signature workflows.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| PandaDoc  | OAuth sign-in  |

#### PandaDoc

Connect to PandaDoc to access documents, templates, and forms. Supports document management, template creation, and e-signature workflows.

**Set up in PandaDoc**

1. Use a PandaDoc account with access to the records and operations that your workflow needs.
2. If your organization restricts application access or user consent, have its administrator approve the connection before you sign in.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **PandaDoc**.
2. Select **Connect**, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

StackAI obtains the OAuth credentials during sign-in. You do not need to paste an access token or refresh token.

**Provider documentation:** [Setup reference](https://developers.pandadoc.com/reference/about).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **PandaDoc** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Create Document from Template

Create a new PandaDoc document from an existing template

**Inputs**

| Field                | Type          | Required | Description                                                         |
| -------------------- | ------------- | -------- | ------------------------------------------------------------------- |
| Template UUID        | string        | Yes      | Enter the PandaDoc template UUID to use for document creation.      |
| Document Name        | string        | Yes      | Name for the new document.                                          |
| Recipient Email      | string        | Yes      | Email address of the primary recipient/signer.                      |
| Recipient First Name | string        | No       | First name of the recipient.                                        |
| Recipient Last Name  | string        | No       | Last name of the recipient.                                         |
| Recipient Role       | string        | No       | Role of the recipient in the template (e.g., Customer, Contractor). |
| Template Fields      | object        | No       | Key-value pairs to populate template fields.                        |
| Metadata             | object        | No       | Additional metadata to attach to the document.                      |
| Document Tags        | string\_array | No       | Tags to categorize the document.                                    |

**Outputs**

| Field           | Type        | Description                                         |
| --------------- | ----------- | --------------------------------------------------- |
| Document ID     | string      | Unique identifier of the created document.          |
| Document Name   | string      | Name of the created document.                       |
| Document Status | string      | Current status of the document.                     |
| Date Created    | string      | When the document was created.                      |
| Date Modified   | string      | When the document was last modified.                |
| Expiration Date | string      | Document expiration date if set.                    |
| Version         | string      | Document version.                                   |
| Document UUID   | string      | Document UUID (same as ID).                         |
| Document Links  | dict\_array | Available API links for this document.              |
| Info Message    | string      | Additional information about the document creation. |

#### Create or Update Contact

Create a new contact or update an existing one in PandaDoc

**Inputs**

| Field          | Type   | Required | Description                                               |
| -------------- | ------ | -------- | --------------------------------------------------------- |
| Email Address  | string | Yes      | Email address of the contact (used as unique identifier). |
| First Name     | string | No       | First name of the contact.                                |
| Last Name      | string | No       | Last name of the contact.                                 |
| Company        | string | No       | Company or organization name.                             |
| Phone Number   | string | No       | Phone number of the contact.                              |
| State/Province | string | No       | State or province of the contact.                         |
| City           | string | No       | City of the contact.                                      |
| Street Address | string | No       | Street address of the contact.                            |
| Postal Code    | string | No       | Postal/ZIP code of the contact.                           |

**Outputs**

| Field               | Type    | Description                                 |
| ------------------- | ------- | ------------------------------------------- |
| Contact ID          | string  | Unique identifier of the contact.           |
| Email Address       | string  | Email address of the contact.               |
| First Name          | string  | First name of the contact.                  |
| Last Name           | string  | Last name of the contact.                   |
| Company             | string  | Company of the contact.                     |
| Operation Performed | string  | Whether the contact was created or updated. |
| Success             | boolean | Whether the operation was successful.       |

#### Send Document

Send a PandaDoc document to recipients via email. The recipient is already set when the document was created

**Inputs**

| Field         | Type     | Required | Description                                                                                                   |
| ------------- | -------- | -------- | ------------------------------------------------------------------------------------------------------------- |
| Document ID   | string   | Yes      | The ID of the document to send (must be in draft status).                                                     |
| Email Subject | string   | No       | Custom subject line for the email notification.                                                               |
| Email Message | textarea | No       | Custom message body for the email notification.                                                               |
| Silent Mode   | boolean  | No       | If set to true, disables email notifications for document recipients and the document sender. Default: false. |

**Outputs**

| Field                  | Type    | Description                                   |
| ---------------------- | ------- | --------------------------------------------- |
| Success                | boolean | Whether the document was successfully sent.   |
| Document ID            | string  | ID of the sent document.                      |
| Document Status        | string  | Current status of the document after sending. |
| Status Message         | string  | Information about the send operation.         |
| Additional Information | string  | Additional information from the API.          |

### Important behavior

If an operation is denied, check the connection’s granted permissions and the account’s access in the provider. Reauthorize the connection when it needs additional permissions.

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/pandadoc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
