FileMaker
Record CRUD, find requests and scripts on a hosted FileMaker database (Claris Data API).
OCNORA ships 7 typed FileMaker operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect FileMaker
- Authentication
- Username & password
- Credential
- {"username": "…", "password": "…"} — a FileMaker account with the fmrest extended privilege
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with FileMaker
Operations, grouped by what they do to your data.
Create and send 2
Read and search 3
Update 1
Delete and cancel 1
A sample FileMaker workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no FileMaker trigger is needed.
- 2Find Recordsfilemaker.find_recordsRun a find request against a layout.
- 3Create Recordfilemaker.create_recordCreate one record on a layout.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 7
- Create RecordCreate one record on a layout.filemaker.create_record
- Delete RecordDelete one record by its FileMaker record id.filemaker.delete_record
- Find RecordsRun a find request against a layout.filemaker.find_records
- Get RecordRead one record by its FileMaker record id.filemaker.get_record
- List RecordsRead a range of records from a layout.filemaker.list_records
- Run ScriptRun a FileMaker script in the context of a layout.filemaker.run_script
- Update RecordEdit one record by its FileMaker record id.filemaker.update_record
FileMaker questions
- How does OCNORA authenticate with FileMaker?
- With a stored Username & password credential, shaped {"username": "…", "password": "…"} — a FileMaker account with the fmrest extended privilege. A connection test can check it when you add it.
- What can I automate with FileMaker?
- 7 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the FileMaker operation I need is not listed?
- Where FileMaker has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use FileMaker?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are FileMaker calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Databases & warehouses
See your first FileMaker workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.