Integration
Connect Flatfile and QuintaDB
When something happens in Flatfile or QuintaDB, your agent does the next thing in the other. Describe it 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 Flatfile and QuintaDB 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 Flatfile and QuintaDB can do together
From Flatfile to QuintaDB
When New Agent in Flatfile
then Add form in QuintaDB
From QuintaDB to Flatfile
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 Flatfile and QuintaDB
Triggers and actions 15 triggers · 14 actions
- New Agent
Triggers when a new agent is created.
- New App
Triggers when a new app is created.
- New Document
Triggers when a new document is created in a space.
- New Event
Triggers when a new event occurs in Flatfile.
- New Prompt
Triggers when a new prompt is created.
- New Sheet
Trigger when a new sheet is created in a Flatfile workbook.
- New User
Triggers when a new user is created.
- New Workbook
Trigger when a new workbook is created in Flatfile.
- Create Document
Creates a new document in Flatfile.
- Create Prompt
Creates a new AI prompt in Flatfile.
- Get Document
Retrieves a single document from a Flatfile space by its ID.
- Upload File
Uploads a file to Flatfile.
- New Database
Triggers when a new database is created in the connected QuintaDB account.
- New Form
Triggers when a new form is added to a QuintaDB database.
- New Form Field
Triggers when a new field is added to a QuintaDB form.
- New or Updated Record
Triggers when a record in a QuintaDB form is added or changed.
- New Record
Triggers when a new record is added to a QuintaDB form.
- New Table Record
Triggers when a new record is added to a QuintaDB form.
- New Table Report
Triggers when a new report is created on a QuintaDB form.
- Add form
Adds a new form (table) to a QuintaDB database. Returns the created form.
- Create Record
Adds a new record to a QuintaDB form. The form's own fields are offered for mapping, and the created record's id is returned.
- Delete form
Deletes a form (table) and its records from a QuintaDB database.
- Delete Record
Deletes a record from a QuintaDB form.
- Delete records
Deletes several records from a QuintaDB form in one call.
- Find Records
Returns the records in a QuintaDB form that match the conditions you specify.
- Get record
Returns one record from a QuintaDB form, including all of its field values.
- Update Cell
Changes the value of one field on one QuintaDB record.
- Update Record
Changes field values on an existing QuintaDB record. Fields you leave blank keep their current value.
- Upload file
Uploads a file into a file field on an existing QuintaDB record.
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 Flatfile
Flatfile to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Flatfile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Flatfile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Flatfile to Google SheetsGoogle Sheets
Flatfile to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Flatfile to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into QuintaDB
Dub to QuintaDBDub is the open-source link management infrastructure for modern marketing teams.
Pixabay to QuintaDBPixabay is a free image and video library. Search over 4 million royalty-free photos, illustrations, vector...
Gmail to QuintaDBGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Flatfile and QuintaDB, answered
What can start an automation from Flatfile?
Any of Flatfile's 8 triggers in the catalog, including New Agent, New App, New Document and New Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in QuintaDB when something happens in Flatfile?
Any of QuintaDB's 10 actions, including Create Record, Update Cell, Update Record and Upload file. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from QuintaDB to Flatfile?
Yes. When something happens in QuintaDB, your agent can act in Flatfile too. This page covers both directions: QuintaDB's triggers and Flatfile's actions are listed here as well.
Do I have to build a connector for Flatfile or QuintaDB?
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.