Integration
Connect MySQL and PandaDoc
When New or Updated Row fires in MySQL, your agent runs Create contact in PandaDoc, or Document completed in PandaDoc to Add Row in MySQL. 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 MySQL and PandaDoc 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)PandaDoc holds your quotes, proposals and signed agreements, while MySQL holds the customer and order records your team reports on. Joining them means a completed PandaDoc document can write its signer details and field values straight into your tables, and a new row in MySQL can start the document your team needs to send.
Example flows
What MySQL and PandaDoc can do together
From MySQL to PandaDoc
When New or Updated Row in MySQL
then Create contact in PandaDoc
From PandaDoc to MySQL
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 MySQL and PandaDoc
Triggers and actions 7 triggers · 25 actions
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected MySQL database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected MySQL database.
- Add Row
Adds a new row.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Finds a row in a table via a lookup column.
- Find Rows via Custom Query
Run an author-written SELECT against the connected MySQL database and return every row it produced. Mirrors PostgreSQL 715ae2ac, SQL Server 8e0bbb5d and Oracle 2c308e4d; MySQL placeholder style is ?.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected MySQL database and returns the first row it matches.
- Update Row
Updates an existing row.
- 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.
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 MySQL
MySQL to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MySQL to MailchimpMailchimp marketing automation and email platform.
MySQL to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MySQL to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
MySQL to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
MySQL to SendGridSendGrid by Twilio — email delivery and marketing platform.
More into PandaDoc
HubSpot to PandaDocHubSpot is your all-in-one stop for all of your marketing software needs.
JIRA to PandaDocAtlassian JIRA Cloud — issue tracking and project management.
Intercom to PandaDocIntercom is a customer communications platform for support, engagement, and marketing.
JotForm to PandaDocJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
Questions
MySQL and PandaDoc, answered
Can a document start from data already in MySQL?
Yes. A new row, or a row returned by a SELECT you write, can trigger Create document from template in PandaDoc with recipients, tokens and pricing values from that row. You can follow it with Send document so the recipient gets it.
How do we avoid writing rows for customers we do not have yet?
Use Find Row in MySQL after the PandaDoc trigger and act only when a matching row comes back, updating it with Update Row. The agent tests every scenario, including the case where no matching row exists, before it goes live.
What can start an automation from MySQL?
Any of MySQL's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PandaDoc when something happens in MySQL?
Any of PandaDoc's 19 actions, including Create contact, Create document from template, Get document entered data and Create document link. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PandaDoc to MySQL?
Yes. When something happens in PandaDoc, your agent can act in MySQL too. This page covers both directions: PandaDoc's triggers and MySQL's actions are listed here as well.
Do I have to build a connector for MySQL or PandaDoc?
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 MySQL and PandaDoc 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.