Get Record
filemaker.get_record
ActionDatabases & warehousesconnection required
Calls the FileMaker API with the connection's credentials.
Read 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
Configuration
3 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 |
layout_response Return the record data in the context of this other layout instead of the one the request ran on. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"layout": "Contacts",
"record_id": "147"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
layout The layout the record was read through. | string | — |
record_id The record id that was requested. | string | — |
record The record, with its fieldData and portalData. | object | — |
found True when FileMaker returned a record. | boolean | — |
{
"found": false,
"layout": "",
"record": {},
"record_id": ""
}Related FileMaker nodes
See Get Record run in a workflow.
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.