Update Record

filemaker.update_record

ActionDatabases & warehousesconnection required

Calls the FileMaker API with the connection's credentials.

Edit one record by its FileMaker record id.

Connection

Required: Yes — the node will not save without one
Auth type: Username & password
Providers: FileMaker
Secret shape: {"username": "…", "password": "…"} — a FileMaker account with the fmrest extended privilege
Config it needs: base_url, database, api_version
Resolved by: config.connection_id, else node.connection_id

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
layout Name of the FileMaker layout to work through; it decides which fields and portals the Data API can see.	string	Yes	—	—	Contacts
record_id The record's internal FileMaker record id, as returned by a create, a find or a listing.	string	Yes	—	—	147
field_data Field names mapped to the values to write. Leave it empty to create a record with every field at its layout default.	object	No	—	—	{"Company":"Acme","First Name":"Joe"}
portal_data Related records to write, keyed by portal object name, as FileMaker's portalData structure.	object	No	—	—	—

Every value below is the contract’s own example or default — nothing invented.

{
  "field_data": {
    "Company": "Acme",
    "First Name": "Joe"
  },
  "layout": "Contacts",
  "record_id": "147"
}

One shape.

Field	Type	Example
layout The layout the record was edited through.	string	—
record_id The record id that was edited.	string	—
mod_id The record's modification counter after the edit.	string	—

{
  "layout": "",
  "mod_id": "",
  "record_id": ""
}

In a technical demo we add the FileMaker connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.