Integration
Connect Formstack Documents to Instatus
When New Merged Document fires in Formstack Documents, your agent runs Add component in Instatus. 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 Instatus 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 can start in Instatus
When New Merged Document in Formstack Documents
then Add component in Instatus
When New Merged Document in Formstack Documents
then Add incident update in Instatus
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 Instatus
Triggers and actions 1 trigger · 29 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.
Action
Add componentCreates a new component on an Instatus status page and returns the created component.
Action
Add incident updatePosts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
Action
Add maintenanceSchedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
Action
Add subscriberAdds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
Action
Create IncidentCreates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
Action
Delete incidentDeletes an incident from an Instatus status page.
Action
Get componentReturns one component on an Instatus status page, including its name, current status, description and group.
Action
Get incidentReturns a single incident on a status page, including its updates, affected components and the teammate who created it.
Action
Get maintenanceReturns one scheduled maintenance on a status page, including its updates and affected components.
Action
List componentsReturns the components on an Instatus status page, with each component's name, status and group.
Action
List maintenancesReturns the scheduled, in-progress and completed maintenances on an Instatus status page.
Action
List status pagesReturns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
Action
List subscribersReturns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
Action
Update componentUpdates a component on an Instatus status page, such as its name, description, status, order or group.
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 Instatus
HubSpot to InstatusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to InstatusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to InstatusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to InstatusGoogle Sheets
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Formstack Documents and Instatus, 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 Instatus when something happens in Formstack Documents?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Formstack Documents?
Instatus has no triggers in the catalog today, so automations start in Formstack Documents. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Formstack Documents or Instatus?
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.