AITable
DatabaseAITable (formerly APITable) is an Airtable-style database with datasheets, views, spaces and a built-in AI agent. Agents read, create, update and delete records, manage fields, datasheets, members, teams and roles, and chat with the AITable AI agent from inside a flow.
What This Integration Enables
Most Airtable-style databases give an agent the table. AITable gives it the table, the organization chart that decides who can read the table, and a generator that turns any datasheet into a URL anybody can open. That is a wider surface than a row sync, and it is the reason this connector is worth more than a data pipe: FlowRunner agents read and write records through the Fusion API, create fields and datasheets, walk spaces and nodes to find things by name, manage members, teams and roles, and put questions to the AI agent AITable ships with.
The wider surface is also why the boundary matters. Records, fields and teams are all recoverable with work. A published embed link is not, because revoking it stops future reads and does nothing about the ones that already happened. FlowRunner's human-in-the-loop design puts that asymmetry where it belongs: the agent does the walking, sampling and drafting, and a person decides what leaves the workspace.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
The operational datasheet that stays current
An intake form in Typeform or a row appended in Google Sheets reaches the agent. It calls Get Fields first, because addressing fields by id rather than by name survives somebody renaming a column in the product, then writes with Create Records in batches the API accepts. Existing rows are found with Get Records using a Filter By Formula expression rather than a full scan, and refreshed with Update Records, where a field left out keeps its old value and a field sent as null is deliberately cleared. Attachments arrive through Upload Attachment, which returns a token the agent then writes onto the record. The datasheet stays the working copy the team already looks at.
-
Asking the vendor's own agent a question the flow needs answered
A support triage flow needs to know whether an incoming account has an open escalation. Rather than paging the datasheet and reasoning over raw rows, the agent calls Chat With AI Agent, which answers from the datasheets it has been given access to, and passes the existing message history straight through. The answer routes the ticket. When the answer is ambiguous, the flow falls back to Get Records with an explicit filter, because a deterministic query is the right instrument when a decision hangs on it.
-
Onboarding a team without hand-assigning anything
A new department lands in the HR system. The agent calls Create Team to place it in the organization tree, walks Get Team Children and Get Team Members to confirm the shape, and reads Get Roles to find the permission set the department should hold. It does not invent a role. If no existing role fits, it drafts one and posts the proposed permissions to the space owner in Slack, with Get Role Units showing who already holds the nearest match. The owner approves, and Create Role plus Update Member finish the job in one pass.
Human-in-Loop Highlight
Create Embed Link is the operation on this connector that cannot be taken back. It turns a datasheet or dashboard into a URL that anyone holding it can open, and revoking it later with Delete Embed Link stops the next reader, not the last one. So an agent building a client-facing dashboard assembles everything and then stops. It posts: "Ready to publish the Q3 Delivery dashboard as a public link. It exposes 11 fields including Client Name, Contract Value and Account Owner Email. Three embed links already exist in this space, all on the Marketing folder. Publish, or narrow the view first?" The space owner answers in the channel. If the answer is narrow it first, the agent builds a filtered view instead and asks again. The judgment call is what data leaves the workspace, and that call has an owner.
Agent Capabilities
30 actionsRecords and Attachments
5- Get Records Reads records from a datasheet with filtering, sorting, field selection and paging. Naming a view returns that view's rows in its own order with its hidden fields omitted, which is the simplest way to reuse a filter somebody already configured.
- Create Records Adds records to a datasheet. The vendor caps a call at ten records, which the connector checks up front so an oversized request fails immediately rather than partway through.
- Update Records Updates records in a datasheet. Only the fields you name are written. Clearing a field takes an explicit null, because omitting it leaves the old value in place.
- Delete Records Permanently deletes records from a datasheet. There is no undo on this API, so bulk deletion belongs behind a review step.
- Upload Attachment Uploads a file to a datasheet and returns an attachment token. Uploading does not attach anything on its own: the token has to be written onto a record with Update Records.
Fields, Views and Datasheets
5- Get Fields Returns a datasheet's fields with their ids, names, types and type specific properties. Call it before any write, and use it to decide whether to address fields by name or by id.
- Create Field Adds a field to a datasheet. Each of the vendor's field types takes its own property object, so the shape comes from their Create Field reference rather than from a fixed list here.
- Delete Field Permanently deletes a field and every value stored in it across the datasheet. There is no undo.
- Get Views Returns the views defined on a datasheet. A view id narrows Get Records to that view's rows, order and visible fields.
- Create Datasheet Creates a datasheet in a space, optionally with its initial fields. The identifier it returns is what every record and field operation needs afterward.
Spaces and Nodes
3- Get Spaces Returns the spaces the API token can reach. A space holds folders, datasheets and members, so its id is what the field, node, member, team and role operations key on.
- Get Nodes Returns a space's folders, datasheets, dashboards, forms and mirrors as a tree. Used to discover a datasheet by name instead of copying an id out of a URL.
- Get Node Returns a single node with its name, type and icon, and for a folder its children.
Public Embed Links
3- Create Embed Link Creates a shareable embed link for a node, making it viewable outside AITable. The resulting URL is public, so this is a publishing decision rather than a configuration change.
- Get Embed Links Returns the embed links that currently exist for a node. Because each one is a public URL, this is the operation an exposure audit is built on.
- Delete Embed Link Revokes an embed link so the public URL stops working. It closes future access; it does not recall what has already been read.
Members
3- Get Member Returns a member of a space by unit id, with their name, email, teams and role.
- Update Member Updates a member's display name or team membership. This is a full replacement, so send the complete set of values the member should end up with.
- Delete Member Removes a member from a space. Their access ends immediately, and the records they created remain.
Teams
5- Get Team Members Returns the members of a team. Combined with Get Team Children, this walks the organization tree down to individual people.
- Get Team Children Returns the sub teams of a team, which is how the tree is walked one level at a time.
- Create Team Creates a team in a space, optionally beneath an existing team. Teams are the unit a role is usually granted to.
- Update Team Updates a team's name or its position in the tree. This is a full replacement rather than a patch.
- Delete Team Deletes a team. Its members stay in the space; only the grouping goes.
Roles
5- Get Roles Returns the roles defined in a space. A role is a named permission set that teams and members are assigned to.
- Get Role Units Returns the members and teams assigned to a role, which is how you audit who actually holds a permission set before changing it.
- Create Role Creates a role so a permission set can be granted by name rather than person by person.
- Update Role Updates a role's name or the permissions it grants. Everyone assigned to it is affected at once, which is both the point of roles and the reason to review the change.
- Delete Role Deletes a role. Everyone holding it loses what it granted, so Get Role Units belongs in the step before this one.
AI
1- Chat With AI Agent Sends a chat request to an AITable AI agent, which answers from the datasheets it has been given. The request follows the OpenAI chat completions shape, so an existing message array can be passed straight through.
Frequently Asked Questions
What can FlowRunner do with AITable?
FlowRunner agents can run Get Records, Create Records, and Update Records in AITable, plus 27 more actions.
Does connecting AITable to FlowRunner require OAuth?
No. AITable connects to FlowRunner with an API key, no OAuth flow required.
Can AITable trigger a FlowRunner workflow automatically?
AITable doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Database integrations
Start building with AITable
Free plan, no card required. Connect in minutes.