Integration
Connect PandaDoc and Wachete
When Document completed fires in PandaDoc, your agent runs Create monitor in Wachete, or Any new notification in Wachete to Create contact in PandaDoc. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want PandaDoc and Wachete to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Wachete watches the web pages your deals depend on — supplier price lists, client terms, tender boards — while PandaDoc holds the quotes and proposals built on them. Joining them means a change notification in Wachete can raise, send or void the right PandaDoc document, and a completed PandaDoc document can start a new Wachete monitor.
Example flows
What PandaDoc and Wachete can do together
From PandaDoc to Wachete
When Document completed in PandaDoc
then Create monitor in Wachete
From Wachete to PandaDoc
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with PandaDoc and Wachete
Triggers and actions 5 triggers · 26 actions
- Document completed
Polling trigger. Fires when a document reaches completed status. Dedup by document id.
- Document completed (instant)
Instant trigger: fires when a PandaDoc document reaches the completed state. Self-registering — APIANT creates the PandaDoc webhook when you turn the automation on and removes it when you turn it off, so there is nothing to paste. Only document_state_changed events with status document.completed are passed through; each fires once with the document id, name, status, created/modified/completed timestamps and the full document object.
- Document updated
Polling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.
- Change document status
Manually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.
- Create contact
Creates a new contact.
- Create document from template
Creates a new document from a template, with recipients, tokens, fields, and pricing tables.
- Create document link
Generates a shareable session link for a recipient to view/sign a document.
- Delete contact
Deletes a contact by ID.
- Delete document
Deletes a document by ID.
- Download document PDF
Returns the document as a PDF file. Use watermark options as needed.
- Find document by name
Finds a document by name and emits its ID. An error occurs if none or more than one is found.
- Get document details
Retrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.
- Get document entered data
Emits arrays of field and token names and values for the specified document.
- Get document status
Returns the current status of a document by ID.
- Get template details
Retrieves details for a template by ID, including roles, fields, tokens, and pricing tables.
- List contacts
Lists contacts in the workspace.
- List documents
Lists documents, optionally filtered by status, template, folder, or search query.
- List folders
Lists document folders.
- List members
Lists workspace members (users).
- List templates
Lists available document templates.
- Send document
Moves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.
- Update contact
Updates an existing contact by ID.
- Any new notification
Fires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from PandaDoc
PandaDoc to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PandaDoc to StripeStripe is a payment processing platform for online businesses.
PandaDoc to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
PandaDoc to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
PandaDoc to PipedrivePipedrive is a sales CRM and pipeline management tool.
PandaDoc to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Wachete
HubSpot to WacheteHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to WacheteSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to WacheteMailchimp marketing automation and email platform.
Questions
PandaDoc and Wachete, answered
Can a Wachete change notification create the right PandaDoc document, not just any document?
Yes. The agent can read the captured data for the monitor in Wachete, check the change against your condition, then create a document from the template you name in PandaDoc with the tokens and recipients you want. It tests every scenario before it runs on live notifications.
What can happen in Wachete after a PandaDoc document is signed?
A completed PandaDoc document can create a monitor in Wachete on a page tied to that customer, and a document status change can update an existing monitor's URL, watched part or check frequency. Monitors can also be deleted when the work they supported is done.
What can start an automation from PandaDoc?
Any of PandaDoc's 3 triggers in the catalog, including Document completed, Document completed (instant) and Document updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in PandaDoc?
Any of Wachete's 7 actions, including Create monitor, Get monitor data, Update monitor and Get monitor. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wachete to PandaDoc?
Yes. When something happens in Wachete, your agent can act in PandaDoc too. This page covers both directions: Wachete's triggers and PandaDoc's actions are listed here as well.
Do I have to build a connector for PandaDoc or Wachete?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use PandaDoc and Wachete without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.