Integration
Connect PandaDoc to Buildfire
When Document completed fires in PandaDoc, your agent runs Update CMS record in Buildfire. 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 Buildfire 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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)Example flows
What PandaDoc can start in Buildfire
When Document completed in PandaDoc
then Update CMS record in Buildfire
When Document updated in PandaDoc
then Insert CMS Record in Buildfire
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 Buildfire
Triggers and actions 3 triggers · 29 actions
Trigger
Document completedPolling 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 updatedPolling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.
Action
Change document statusManually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.
Action
Create contactCreates a new contact.
Action
Create document from templateCreates a new document from a template, with recipients, tokens, fields, and pricing tables.
Action
Create document linkGenerates a shareable session link for a recipient to view/sign a document.
Action
Delete contactDeletes a contact by ID.
Action
Delete documentDeletes a document by ID.
Action
Download document PDFReturns the document as a PDF file. Use watermark options as needed.
Action
Find document by nameFinds a document by name and emits its ID. An error occurs if none or more than one is found.
Action
Get document detailsRetrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.
Action
Get document entered dataEmits arrays of field and token names and values for the specified document.
Action
Get document statusReturns the current status of a document by ID.
Action
Get template detailsRetrieves details for a template by ID, including roles, fields, tokens, and pricing tables.
Action
List contactsLists contacts in the workspace.
Action
List documentsLists documents, optionally filtered by status, template, folder, or search query.
Action
List foldersLists document folders.
Action
List membersLists workspace members (users).
Action
List templatesLists available document templates.
Action
Send documentMoves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.
Action
Update contactUpdates an existing contact by ID.
Action
Assign Tags to UserAdds one or more tags to a Buildfire app user.
Action
Delete CMS recordDeletes a record from a BuildFire plugin's CMS data by its key.
Action
Delete userRemoves a user from your BuildFire app by username.
Action
Find CMS recordsFinds CMS (plugin data) records in a Buildfire plugin instance by tag, optionally within a date range.
Action
Get User by Access TokenReturns the Buildfire app user that a login access token belongs to, including name, email and activity dates.
Action
Insert CMS RecordAdds a data record to a plugin instance's CMS data under a tag.
Action
Register UserRegisters a new user in a Buildfire app with their email and optional password and name.
Action
Remove tags from userRemoves one or more tags from a BuildFire app user.
Action
Schedule Push NotificationSchedules a push notification to the app's users, to one group, or to users with given tags.
Action
Update CMS recordUpdates (saves) a record in a BuildFire plugin's CMS data collection.
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 Buildfire
HubSpot to BuildfireHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BuildfireSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BuildfireSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BuildfireGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to BuildfireGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BuildfireGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
PandaDoc and Buildfire, answered
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 Buildfire when something happens in PandaDoc?
Any of Buildfire's 10 actions, including Update CMS record, Assign Tags to User, Find CMS records and Get User by Access Token. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Buildfire to PandaDoc?
Buildfire has no triggers in the catalog today, so automations start in PandaDoc. If you need the other direction, ask: your agent reads Buildfire's API documentation and adds it.
Do I have to build a connector for PandaDoc or Buildfire?
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 Buildfire 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.