Integration

Connect PandaDoc to Wachete

When something happens in PandaDoc, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.

PandaDoc3 triggersPandaDoc19 actionsWachete2 triggersWachete7 actions

Browse all apps

Build it

What do you want PandaDoc and Wachete to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with PandaDoc and Wachete

Triggers and actions 5 triggers · 26 actions

Trigger
Document completed
Polling trigger. Fires when a document reaches completed status. Dedup by document id.
Trigger
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.
Trigger
Document updated
Polling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.
Action
Change document status
Manually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.
Action
Create contact
Creates a new contact.
Action
Create document from template
Creates a new document from a template, with recipients, tokens, fields, and pricing tables.
Action
Create document link
Generates a shareable session link for a recipient to view/sign a document.
Action
Delete contact
Deletes a contact by ID.
Action
Delete document
Deletes a document by ID.
Action
Download document PDF
Returns the document as a PDF file. Use watermark options as needed.
Action
Find document by name
Finds a document by name and emits its ID. An error occurs if none or more than one is found.
Action
Get document details
Retrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.
Action
Get document entered data
Emits arrays of field and token names and values for the specified document.
Action
Get document status
Returns the current status of a document by ID.
Action
Get template details
Retrieves details for a template by ID, including roles, fields, tokens, and pricing tables.
Action
List contacts
Lists contacts in the workspace.
Action
List documents
Lists documents, optionally filtered by status, template, folder, or search query.
Action
List folders
Lists document folders.
Action
List members
Lists workspace members (users).
Action
List templates
Lists available document templates.
Action
Send document
Moves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.
Action
Update contact
Updates an existing contact by ID.
Trigger
Any new notification
Fires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitor
Delete a Wachete monitor by its ID.
Action
Get monitor
Get information about a specific Wachete monitor by its ID.
Action
Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List folders
List folder contents, optionally under a parent folder.
Action
List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
Action
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.

Each app on its own

The other way round: Wachete to PandaDoc