Build solutions, not workarounds.
What do you want Formstack and Stedi 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 can start in Stedi
When New Form in Formstack
then Add event destination in Stedi
When New Form in Formstack
then Update event destination in Stedi
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 and Stedi
Triggers and actions 1 trigger · 26 actions
Trigger
New FormTriggers when a new form is created in the account.
Action
Copy FormCreate a copy of an existing form.
Action
Create FolderCreate a new form folder.
Action
Create FormCreate a new form.
Action
Create Form FieldAdd a new field to a form.
Action
Create SubmissionSubmit data to a form. Field values are passed as field_<id> keys.
Action
Create WebhookCreate a webhook on a form that POSTs to a URL when a submission is received.
Action
Delete folderDelete a folder.
Action
Delete FormDelete a form by ID.
Action
Delete SubmissionDelete a submission by ID.
Action
Delete WebhookDelete a webhook by ID.
Action
Get FormRetrieve details for a single form by ID.
Action
Get form fieldGet one field on a form.
Action
List Form ConfirmationsList confirmation emails configured on a form.
Action
List Form FieldsList all fields on a form.
Action
List form notificationsList notification emails for a form.
Action
List WebhooksList webhooks configured on a form.
Action
Update folderUpdate a folder.
Action
Add event destinationCreate a new event destination for receiving Stedi webhook events.
Action
Check eligibilityRuns a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response.
Action
Delete event destinationPermanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED.
Action
Find payers by criteriaSearches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance.
Action
Get event destinationRetrieve an event destination by id.
Action
Get payerRetrieve a single payer record by id.
Action
List event destinationsLists the event destinations configured in your Stedi account, optionally filtered by status or event type.
Action
List payersLists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements.
Action
Update event destinationUpdates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed.
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
Formstack to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Formstack to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Formstack to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Formstack to Google SheetsGoogle Sheets
Formstack to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Formstack to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Stedi
HubSpot to StediHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to StediSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to StediSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to StediGoogle Sheets
Gmail to StediGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StediGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Formstack and Stedi, answered
What can start an automation from Formstack?
Any of Formstack's 1 trigger in the catalog, including New Form. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Stedi when something happens in Formstack?
Any of Stedi's 9 actions, including Update event destination, Add event destination, Check eligibility and Find payers by criteria. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Stedi to Formstack?
Stedi has no triggers in the catalog today, so automations start in Formstack. If you need the other direction, ask: your agent reads Stedi's API documentation and adds it.
Do I have to build a connector for Formstack or Stedi?
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.