Integration
Connect Formstack Documents to Fly.io Machines API
When New Merged Document fires in Formstack Documents, your agent runs Create App in Fly.io Machines API. 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 Fly.io Machines API 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 Fly.io Machines API
When New Merged Document in Formstack Documents
then Create App in Fly.io Machines API
When New Merged Document in Formstack Documents
then Create Machine in Fly.io Machines API
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 Fly.io Machines API
Triggers and actions 1 trigger · 26 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
Create AppCreates a new Fly.io app in the chosen organization and returns its id.
Action
Create MachineCreates a new Machine in a Fly.io app from the image and configuration you provide, and returns the created Machine.
Action
Create VolumeCreates a persistent storage volume for a Fly.io app in the chosen region.
Action
Delete AppDeletes a Fly.io app by its name.
Action
Delete MachineDeletes a Machine from a Fly.io app, optionally force-killing it if it is still running.
Action
Delete VolumeDestroys a volume in a Fly.io app and returns the deleted volume's details.
Action
Extend VolumeExtends a Fly.io volume to a larger size in gigabytes. Returns the updated volume and whether its Machine needs a restart.
Action
Start MachineStarts a stopped or suspended Machine in a Fly.io app.
Action
Stop MachineStops a running Fly.io Machine in an app, optionally choosing the stop signal and how long to wait before it is killed.
Action
Suspend MachineSuspends a Machine in a Fly.io app so its next start can resume from a snapshot instead of a cold boot.
Action
Update MachineUpdates a Fly.io Machine's configuration, such as its image, guest size, environment variables, services or restart policy, and returns the updated Machine.
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 Fly.io Machines API
HubSpot to Fly.io Machines APIHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Fly.io Machines APISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Fly.io Machines APISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Fly.io Machines APIGoogle Sheets
Gmail to Fly.io Machines APIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Fly.io Machines APIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Formstack Documents and Fly.io Machines API, 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 Fly.io Machines API when something happens in Formstack Documents?
Any of Fly.io Machines API's 11 actions, including Create App, Create Machine, Create Volume and Update Machine. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fly.io Machines API to Formstack Documents?
Fly.io Machines API has no triggers in the catalog today, so automations start in Formstack Documents. If you need the other direction, ask: your agent reads Fly.io Machines API's API documentation and adds it.
Do I have to build a connector for Formstack Documents or Fly.io Machines API?
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.