Integration
Connect Form Io and PostgreSQL
When New submission fires in Form Io, your agent runs Add Row in PostgreSQL, or New or Updated Row in PostgreSQL to Delete submission in Form Io. 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 Form Io and PostgreSQL to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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)Form Io collects the submissions and PostgreSQL holds the records your team reports on. Connecting them means a new submission can be checked against your tables, written as a row, and the submission updated with what the database returned, while changes made in PostgreSQL flow back to the matching Form Io submission.
Example flows
What Form Io and PostgreSQL can do together
From Form Io to PostgreSQL
When New submission in Form Io
then Add Row in PostgreSQL
From PostgreSQL to Form Io
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 Form Io and PostgreSQL
Triggers and actions 5 triggers ยท 13 actions
- New submission
Fires when a new submission is created on a form.
- Delete form
Delete a form/resource by id.
- Delete submission
Delete a submission by id.
- Get form
Retrieve a single form definition by id.
- Get submission
Retrieve a single submission by id.
- List forms
List available forms within a project (Index API, supports limit/skip and select).
- List submissions
List submissions within a form (Index API, supports limit/skip pagination and content filtering).
- Update submission
Update an existing submission's data.
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected PostgreSQL database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected PostgreSQL database.
- Add Row
Adds a new row.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Finds a row in a table via a lookup column.
- Find Rows via Custom Query
Runs a SELECT statement you write against the connected PostgreSQL database and returns every row it matches.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected PostgreSQL database and returns the first row it matches.
- Update Row
Updates an existing row.
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 Form Io
Form Io to OutlookOutlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...
Form Io to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Form Io to UkuUku is an accounting practice management software that helps accounting firms organize, hit deadlines, save...
Form Io to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Form Io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Form Io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into PostgreSQL
Google Sheets to PostgreSQLGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Google Calendar to PostgreSQLGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PostgreSQLGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PostgreSQLMailchimp marketing automation and email platform.
Stripe to PostgreSQLStripe is a payment processing platform for online businesses.
Shopify to PostgreSQLShopify is a commerce platform for online stores and retail point-of-sale.
Questions
Form Io and PostgreSQL, answered
Can I check whether a record already exists before writing a new row?
Yes. On a new submission in Form Io the agent can run Find Row or Find Row via Custom Query in PostgreSQL first, then either Add Row or Update Row depending on what came back. The agent tests every scenario, including when nothing matches.
Can a change in PostgreSQL reach back into Form Io?
Yes. The New or Updated Row trigger and the custom query trigger in PostgreSQL can lead to Get submission, Update submission or Delete submission in Form Io. You give the submission id held in the row so the right record is touched.
What can start an automation from Form Io?
Any of Form Io'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 PostgreSQL when something happens in Form Io?
Any of PostgreSQL's 6 actions, including Add Row, Find Row, Update Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PostgreSQL to Form Io?
Yes. When something happens in PostgreSQL, your agent can act in Form Io too. This page covers both directions: PostgreSQL's triggers and Form Io's actions are listed here as well.
Do I have to build a connector for Form Io or PostgreSQL?
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 Form Io and PostgreSQL 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.