STEP 1
Select FileMaker in workflow
Pick FileMaker app in the workflow builder [4] - just one click to select the app.
FileMaker Integration
Read and write records in FileMaker databases hosted on FileMaker Server or FileMaker Cloud, run scripts, and inspect layout metadata. Connect FileMaker to AI agents and downstream tools whenever important data changes. When Find Records fires, follow with Get Layout Metadata or Get Product Info so connected systems stay up to date.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for FileMaker integration
Triggers can detect changes in FileMaker and run actions that can create, search or modify data inside FileMaker automatically [3] — exactly how you set them.
- Find RecordsRetrieves the records on a layout that match the given find criteria.
- Get Layout MetadataReturns the field, portal, and value list definitions for a layout.
- Get Product InfoReturns version and locale format information about the FileMaker host.
- Get RecordReturns a single record from a layout by its record ID.
- List DatabasesRetrieves a list of hosted databases available through the Data API.
- List LayoutsRetrieves a list of layouts in the connected database.
- List RecordsRetrieves a list of records from a layout.
- List ScriptsRetrieves a list of scripts in the connected database.
- Run ScriptRuns a FileMaker script in the connected database.
- Create RecordCreates a new record on a layout.
- Delete RecordDeletes a record from a layout.
- Duplicate RecordCreates a copy of an existing record on a layout.
- Edit RecordUpdates the field values of an existing record.
- Make an API CallPerforms an arbitrary authorized API call.
- Set Global Field ValuesSets the values of global fields in the connected database.
- Upload Container DataUploads a file into a container field on a record.
How to integrate FileMaker in automation workflow?
3 simple steps to make your FileMaker connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect FileMaker
When prompted, authorize access to FileMaker in WEXTL once. FileMaker credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your FileMaker account. Approve?
STEP 3
Build a workflow
Build your workflow with FileMaker yourself or with WEXTL® AI Builder. Connect FileMaker to any available integrations [5], or use HTTP node to go beyond them.
FileMaker
How FileMaker connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever FileMaker app is called in workflows. That allows your database automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that FileMaker supports.
The following table illustrates what fields FileMaker integration require during authorization flow inside our workflow builder [4].
Connect FileMaker
Server Host*Text
••••••••
Database Name*Text
••••••••
Demonstration of FileMaker connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
Server HostRequired | text | The server origin, for example https://fms.example.com. Do not include /fmi/data/v2 — the app adds that path. |
Database NameRequired | text | The hosted database file name without the .fmp12 extension. |
HostingRequired | select | FileMaker Server uses an account name and password. FileMaker Cloud uses a Claris ID token that expires after one hour. |
Connect FileMaker to popular apps on WEXTL
Enter a name of the other app you want to sync with FileMaker below. Click on selected app to explore integration options with FileMaker. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with FileMaker integration
Select Find Records action from FileMaker - this will be a starting point in your automation. Whenever event happens in FileMaker, workflow will start [7] from Find Records node.
Search for Delete Record, connect it as the next step of integration sequence. You can use filters between Find Records and Delete Record, so only important data pass from Find Records to the next step. WEXTL gives you full control over the process of FileMaker automation. All parts of workflow are visible on the canvas [4].
FileMaker on WEXTL has 16 modules for crafting database automations. Explore FileMaker documentation for more.
FileMaker
Find Records
Firebase
Performs action
OR
Firebase
Triggers
FileMaker
Delete Record
Demonstration of how visual FileMaker automation [6] looks in WEXTL.
Frequently asked questions
Common questions about automating FileMaker in your workflows.
FileMaker has no triggers, but it provides 16 actions including "Find Records", "Get Layout Metadata", and "Get Product Info". Pair them with triggers from other apps to automate FileMaker tasks.
Integration has 16 actions, including "Find Records", "Get Layout Metadata", and "Get Product Info", and more. Refer to our FileMaker Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The FileMaker integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by FileMaker official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where FileMaker provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever FileMaker or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for FileMaker inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with FileMaker modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the FileMaker integration.
- FileMaker integration source code, module specs and credentials implementation.
- Internal FileMaker integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official FileMaker vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® FileMaker App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation