Query and edit records with agent tools

Record operations use the open FileMaker Pro session and the account already signed in to the file. They are separate from native schema, script, and layout authoring.

Read records

Ask the coding agent to use read-only SQL for targeted analysis that does not need FileMaker layout formatting or portal structure:

List the 20 most recent open orders with their customer names. Do not change any records.

SQL queries are limited to reads. The agent should inspect table and field names first and return only the fields and row count needed for the task.

Use FileMaker data operations when the request depends on a layout, portal, value list, container, or FileMaker Data API response shape.

Create, edit, or delete records

Record writes go through validated FileMaker data operations. Name the target layout or let the agent inspect an appropriate one, identify records by stable keys, and state the intended change precisely.

The active FileMaker account must have access to the layout, fields, records, and scripts involved. A schema-capable account does not automatically imply the same record-level access in every privilege set.

Ask the agent to read changed records back after a write. For deletions, review the selected record IDs or keys before approving the operation.

Use a FileMaker script for business transactions

Use a FileMaker script when one action must change several related records, enforce existing business logic, or commit or revert as one transaction. The Web Viewer app can pass one JSON parameter and receive one JSON result through the standard script-call helpers.

See Call FileMaker scripts and Script Calls.