Connect PandaDoc to V7 Go

🚧

Preview

This feature is new and evolving. Details on this page may change as we
improve it.

V7 Go connects to PandaDoc through PandaDoc's MCP server, so the agent can
search, create, and send documents from chats, playbooks, and workflows.

PandaDoc hosts accounts in two regions. Pick the tile that matches where
you sign in:

• PandaDoc if you use app.pandadoc.com
• PandaDoc (EU) if you use app.pandadoc.eu

The wrong region fails sign-in. This is PandaDoc's data region, not V7's.

The short version

1. In Go, open Integrations → MCP Connectors and choose PandaDoc or
   PandaDoc (EU) — or ask the agent in chat to use PandaDoc.
2. Press Connect and authorize PandaDoc in the popup.
3. The agent re-runs the tool it was trying to use against your live
   documents.

There is no client ID or API key to paste.

Troubleshooting

• Sign-in fails or the account looks empty. You picked the other
  region. Disconnect, then connect the EU or global tile instead.
• The agent keeps asking to connect. The stored token was revoked.
  Reconnect from the connector page.

For messages Go shows on the connect card, see
MCP connector errors.

FAQ

Is the connection shared? Connections follow the sharing policy on the
connector page. Private connections only work for the user who created
them.

What can the agent do? Search documents and templates, create from a
template, and send or remind — whatever your PandaDoc user can already do.
Ask "what PandaDoc tools do you have?" for the live list.