--- title: "FileMaker Integration" description: "Connect AI agents to a FileMaker Server or FileMaker Cloud database through the Data API. Agents read, create, edit, find, and delete records, run scripts, and inspect layout metadata." url: https://flowrunner.ai/integrations/filemaker date_modified: 2026-08-01T02:40:32-07:00 --- # FileMaker [Database](https://flowrunner.ai/integrations/category/databases-warehouses) Connect AI agents to a FileMaker Server or FileMaker Cloud database through the Data API. Agents read, create, edit, find, and delete records, run scripts, and inspect layout metadata. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · Session · available [FileMaker website](https://claris.com/) · [Platform Documentation](https://help.claris.com/en/data-api-guide/) · Capability data verified 2026-08-12 1. A record needs to be created in FileMaker from an upstream source 2. Agent reads the incoming data and maps it to fieldData for the layout 3. Agent calls Get Layout Metadata to confirm the field names exist 4. Agent runs Create Record on the chosen layout 5. Agent runs Run Script to trigger the solution's downstream logic 6. Agent reports the new recordId and modId to the team via Slack 7. Any Delete Record or a Run Script with side effects on a production solution pauses for approval ## What This Integration Enables Agents create, read, edit, delete, and duplicate records in a hosted FileMaker solution, run structured `_find` queries to pull matching found sets, trigger scripts and capture their result and error code, discover layouts, scripts, and layout field metadata, and set session-scoped global fields to pass context into scripts. Every record operation goes through a layout, which determines the visible and writable fields, so Get Layout Metadata is the reliable way to build a correct `fieldData` object before writing. Edit Record can supply a `modId` for optimistic locking, so an edit is rejected if the record changed since it was read. ### Without FlowRunner **Manual data entry**: Records are keyed into FileMaker by hand from another system **Session-token plumbing**: Reaching the Data API means managing login and token refresh **Deletes without review**: A record deletion in a live solution has no checkpoint ### With FlowRunner **Automated record creation**: Create Record syncs records from another system into the right layout **Sessions handled**: The connector logs in, caches the token, and re-authenticates on 401 **Guarded deletes**: Delete Record and side-effecting scripts pause for human approval ## Use Case Scenarios ### Syncing records from another system Rows arrive from another connector. For each, the agent calls Get Layout Metadata to confirm the field names, then Create Record on the matching layout with a `fieldData` object. Data entry that used to be manual now flows into the right layout automatically. ### Finding a found set for reporting The agent posts a structured query with Find Records to pull a found set, for example active records excluding a discontinued status, then exports the matching `fieldData` to a spreadsheet for reporting. The found set drives the next step without anyone opening FileMaker. ### Deletion with a human gate An agent is asked to remove a record from a live solution. Before it runs Delete Record, or runs a script with irreversible side effects, it does not act on its own. It routes the record's recordId and context for approval and proceeds only after a person confirms. ## Human-in-Loop Highlight In a live FileMaker solution, a deleted record and a script that fires downstream side effects are both hard to walk back. FlowRunner's answer is human-in-the-loop, an execution pattern where the agent pauses on its own, assembles the context and the choices, routes to a human on their preferred channel, and resumes the moment they respond. When a flow reaches Delete Record on a solution flagged as production, or a Run Script known to have side effects, the agent pauses before executing and asks through Slack: "Ready to Delete Record recordId 8842 on layout `Invoices`. Here is the record. Approve or cancel?" The action runs only after a person confirms, with the approver and timestamp captured in the run log. A connector can delete any record; an orchestration layer knows which deletes should stop and ask. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Records 6 - **Create Record** Creates a record on a layout from a \`fieldData\` object keyed by field name. - **Delete Record** Deletes a record by its internal recordId. - **Duplicate Record** Duplicates an existing record by its internal recordId. - **Edit Record** Edits a record by recordId, writing only the fields you supply, with optional modId optimistic locking. - **Get Record** Fetches one record by recordId through a layout, returning fieldData, portalData, recordId, and modId. - **Get Records** Returns a range of records from a layout with sorting, offset, and limit. ### Find 1 - **Find Records** Posts a structured find query to pull a matching found set, with OR-combined requests and omit support. ### Scripts 2 - **List Scripts** Lists the scripts available in the hosted database. - **Run Script** Runs a FileMaker script and captures its result and error code. ### Metadata 3 - **Get Layout Metadata** Returns the field names, portals, and value lists of a layout, for building fieldData objects. - **Get Product Info** Returns FileMaker Server product and version info, a lightweight connectivity check. - **List Layouts** Lists the layouts available in the hosted database. ### Globals 1 - **Set Global Fields** Sets session-scoped global fields to pass context into FileMaker scripts and calculations. ## Frequently Asked Questions ### What can FlowRunner do with FileMaker? FlowRunner agents can run Get Records, Get Record, and Create Record in FileMaker, plus 10 more actions. ### Does connecting FileMaker to FlowRunner require OAuth? No. FileMaker connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can FileMaker trigger a FlowRunner workflow automatically? FileMaker doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at FileMaker?** This integration exposes FileMaker to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/filemaker. Site index: https://flowrunner.ai/llms.txt