Integration
Connect Formstack Documents and Statuspage
When New Merged Document fires in Formstack Documents, your agent runs Add component in Statuspage, or New incident in Statuspage to Create Document in Formstack Documents. 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 Formstack Documents and Statuspage to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)Example flows
What Formstack Documents and Statuspage can do together
From Formstack Documents to Statuspage
When New Merged Document in Formstack Documents
then Add component in Statuspage
When New Merged Document in Formstack Documents
then Add incident in Statuspage
From Statuspage to Formstack Documents
When New incident in Statuspage
then Create Document in Formstack Documents
When New incident in Statuspage
then Update Document in Formstack Documents
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 Formstack Documents and Statuspage
Triggers and actions 2 triggers · 32 actions
Trigger
New Merged DocumentTriggers when a merged/populated document is created.
Action
Combine FilesJoins several files into one PDF or Word document. Give it the files in the order you want them, either as links or as base64 content, and it returns the combined file.
Action
Convert File to PDFTurns a Word, Excel, PowerPoint, image or HTML file into a PDF. Point it at the file with a link or supply the file content, and it returns the PDF.
Action
Copy DocumentMakes a copy of one of your Formstack Documents templates under a new name, and returns the new document with its merge key, merge URL and available merge fields.
Action
Create Data RouteCreates a data route in Formstack Documents — a single endpoint that sends one set of data to several documents at once, following the rules you give it. Returns the new route with the URL to post data to.
Action
Create Data Route MergeSends one set of data into a Formstack Documents data route, which merges it into every document the route's rules select. Optionally returns the finished documents in the response.
Action
Create DocumentCreates a new document template in Formstack Documents from HTML or from an uploaded PDF, Word, Excel or PowerPoint file, and returns its merge URL and the merge fields found in it.
Action
Delete Data RouteDeletes a data route from Formstack Documents. The documents the route pointed at are not deleted.
Action
Delete DocumentDeletes a document template from Formstack Documents.
Action
Get Data RouteReturns one Formstack Documents data route, with its name, its merge URL and the rules that decide which documents the data goes to.
Action
Get DocumentReturns one document template from Formstack Documents, with its name, type, output format, merge URL and — for HTML templates — the template's HTML.
Action
Get Document FieldsReturns the merge fields found in a Formstack Documents template, so you know which names to send when merging data into it.
Action
List Data RoutesReturns your Formstack Documents data routes, each with its name, key and the URL to send data to.
Action
List DocumentsReturns your Formstack Documents templates, each with its name, type, output format and merge URL.
Action
Update Data RouteUpdates a Formstack Documents data route — its name, folder, or the rules that decide which documents receive the data. Anything you leave blank stays as it is.
Action
Update DocumentUpdates a Formstack Documents template — its name, folder, output format, filename or the template content itself. Anything you leave blank stays as it is; the template type cannot be changed.
Trigger
New incidentPolling trigger for new incidents.
Action
Add componentCreate a component.
Action
Add incidentCreate an incident (realtime/scheduled).
Action
Add metric dataAdd data points to a metric.
Action
Add subscriberCreate a subscriber.
Action
Delete componentDelete a component.
Action
Delete incidentDelete an incident.
Action
Delete subscriberUnsubscribe/delete a subscriber.
Action
Get componentGet a component.
Action
Get incidentGet an incident by id.
Action
Get metricreturns one metric including most_recent_data_at and backfilled.
Action
List componentsList components.
Action
List incidentsList incidents for a page.
Action
List pagesList status pages.
Action
List subscribersList subscribers.
Action
List unresolved incidentsList unresolved incidents.
Action
Update componentUpdate a component (e.g. status).
Action
Update incidentUpdate an incident (status, message, components).
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 Formstack Documents
Formstack Documents to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Formstack Documents to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Formstack Documents to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Formstack Documents to Google SheetsGoogle Sheets
Formstack Documents to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Formstack Documents to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Statuspage
HubSpot to StatuspageHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to StatuspageSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to StatuspageSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to StatuspageGoogle Sheets
Gmail to StatuspageGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StatuspageGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Formstack Documents and Statuspage, answered
What can start an automation from Formstack Documents?
Any of Formstack Documents's 1 trigger in the catalog, including New Merged Document. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Statuspage when something happens in Formstack Documents?
Any of Statuspage's 17 actions, including Update component, Update incident, Add component and Add incident. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Statuspage to Formstack Documents?
Yes. When something happens in Statuspage, your agent can act in Formstack Documents too. This page covers both directions: Statuspage's triggers and Formstack Documents's actions are listed here as well.
Do I have to build a connector for Formstack Documents or Statuspage?
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.
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.