Find, read, create, edit, duplicate and delete records and run scripts in a database hosted on FileMaker Server or FileMaker Cloud through the Data API.
Explore 8 workflow actions for FileMaker, including account permissions and operation limits.
3 read actions5 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Create FileMaker record
Write
Create a record on a layout, optionally with related portal records.
Permissions and limits
Account permissions
fmrest extended privilege; create access to the layout's table
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Field validation is enforced. A lost answer is uncertain and never resent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete FileMaker record
Write
Delete a record by ID.
Permissions and limits
Account permissions
fmrest extended privilege; delete access to the record
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Deletion cannot be undone.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Duplicate FileMaker record
Write
Copy a record; the copy gets a new record ID.
Permissions and limits
Account permissions
fmrest extended privilege; create access to the layout's table
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
A lost answer is uncertain and never resent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Edit FileMaker record
Write
Change the given fields of a record, optionally only if its modification ID still matches.
Permissions and limits
Account permissions
fmrest extended privilege; edit access to the record
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Only the given fields change. A stale modId is refused by FileMaker.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Find FileMaker records
Read
Find records on a layout with one or more find requests, optionally sorted and paged. No match returns an empty list.
Permissions and limits
Account permissions
fmrest extended privilege; read access to the layout
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Find criteria use FileMaker Pro find operators, such as = for a whole-word match.
Pagination: offset. Check the result for additional pages; a single action may not return every record.
Get FileMaker record by ID
Read
Read one record, with its portal data, by record ID.
Permissions and limits
Account permissions
fmrest extended privilege; read access to the layout
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Get FileMaker records
Read
Read a range of records from a layout, optionally sorted.
Permissions and limits
Account permissions
fmrest extended privilege; read access to the layout
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Offsets start at 1.
Pagination: offset. Check the result for additional pages; a single action may not return every record.
Run FileMaker script
Write
Run a script in the context of a layout, with an optional text parameter.
Permissions and limits
Account permissions
fmrest extended privilege; permission to run the script
Operation limits
Each action opens a Data API session with the connection's account and closes it afterwards.
Script names must be unique in the file. A script can change data; a lost answer is uncertain and never resent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in FileMaker. A saved workflow is not a completed provider action.
Data & Docs · CONNECTION
