Integration

Connect Fillout Forms and Grist

When New Submission fires in Fillout Forms, your agent runs Create Record in Grist, or New or Updated Record in Grist to Add Submission in Fillout Forms. 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 Fillout Forms and Grist to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

Fillout Forms collects the answers; Grist holds the tables your team actually works from. Connecting them means a new submission can become a row in the right Grist table, matched against records you already have, and a change in Grist can create or remove a submission in Fillout Forms. Describe what should happen and the agent builds it, tests every scenario and keeps it running.

Example flows

What Fillout Forms and Grist can do together

From Fillout Forms to Grist

From Grist to Fillout Forms

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 Fillout Forms and Grist

Triggers and actions 5 triggers · 26 actions

Each app on its own

Reviews

What our customers say

More from Fillout Forms

More into Grist

Questions

Fillout Forms and Grist, answered

Can I keep one Grist row per person instead of a new row for every submission?

Yes. Use Create or Update Record with a match column such as email, so a repeat submission updates the existing Grist row, and only a new email adds one.

What can start a run between these two apps?

On the Fillout Forms side, New Submission is the trigger. On the Grist side, you can start from New Record or New or Updated Record, including the instant versions, and then act on a form with Add Submission, Get Submission or Delete Submission.

What can start an automation from Fillout Forms?

Any of Fillout Forms's 1 trigger in the catalog, including New Submission. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Grist when something happens in Fillout Forms?

Any of Grist's 21 actions, including Create Record, Find Record, Update Record and Create Document. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Grist to Fillout Forms?

Yes. When something happens in Grist, your agent can act in Fillout Forms too. This page covers both directions: Grist's triggers and Fillout Forms's actions are listed here as well.

Do I have to build a connector for Fillout Forms or Grist?

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 Fillout Forms and Grist 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.