Integration

Connect JotForm and SQL Server

When New Form Submission fires in JotForm, your agent runs Add Row in SQL Server, or New Table in SQL Server to Add or Edit a Single Question Properties in JotForm. 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 JotForm and SQL Server 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)

Connecting SQL Server and JotForm lets form answers land in your database tables, and lets rows in your database drive what happens on your forms. A submission can be matched against an existing record, written as a new row or an update, and the resulting record details can be written back onto the submission in JotForm.

Example flows

What JotForm and SQL Server can do together

From JotForm to SQL Server

From SQL Server to JotForm

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 JotForm and SQL Server

Triggers and actions 6 triggers · 28 actions

Each app on its own

Reviews

What our customers say

More from JotForm

More into SQL Server

Questions

JotForm and SQL Server, answered

Can a submission update an existing customer row instead of always adding a new one?

Yes. The agent can use Find Row in SQL Server to look for a matching value such as an email, then choose Update Row when a match exists or Add Row when it does not. It tests every scenario before the automation goes live.

Do I have to wait for polling to see JotForm submissions in SQL Server?

No. JotForm offers New Form Submission (instant), which registers a webhook and fires as soon as the form is submitted. You can still use the polling New Form Submission trigger if you prefer it.

What can start an automation from JotForm?

Any of JotForm's 2 triggers in the catalog, including New Form Submission and New Form Submission (instant). Describe the moment in plain language and your agent picks the right one.

What can your agent do in SQL Server when something happens in JotForm?

Any of SQL Server's 7 actions, including Add Row, Find Row, Run Custom Statement and Update Row. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from SQL Server to JotForm?

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

Do I have to build a connector for JotForm or SQL Server?

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 JotForm and SQL Server 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.