Actionist·FileMaker
FileMaker

FileMaker

· #218 most-used

Query, create, and automate your FileMaker databases from any agent workflow

ProductivityDocumentsDatabaseDeveloperAutomationNo-Code

Claris FileMaker is a low-code application development platform trusted by businesses worldwide to build custom database apps. Its REST-based Data API lets Actionist agents read records, run finds, create and edit rows, execute server-side scripts, and upload files to container fields — all without opening the FileMaker client. Connect it to Actionist and your agents can keep CRM records in sync, trigger server scripts on a schedule, pull operational data into reports, and automate the manual database work that currently falls between the cracks.

Try FileMaker with ActionistVisit FileMaker
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of opening FileMaker Pro to copy data, run finds, trigger scripts, and compile reports — tasks that previously required database access and typically took 5-10 minutes each across multiple team members each day.

Schedule

What your FileMaker agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

FileMaker × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
6Apps spanned
~25 hrsSaved / week
6Personas served
For sales
Featured3 apps

New CRM lead synced to FileMaker in under a minute

When HubSpot captures a new contact, the agent checks FileMaker for a duplicate by email, creates the contact record if none exists, fires the territory-assignment script to route the lead to the right rep, and posts a summary to Slack — all within about a minute of the form submission.

~8 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new contact is created in HubSpot
Trigger
Step 1
HubSpot
Detect new contact created in HubSpot
read
Step 2
FileMaker
Find Records — search Contacts layout for matching email
write
Step 3
FileMaker
Create Record — new Contact record with all HubSpot fields
write
Step 4
FileMaker
Perform Script — run 'Assign Territory' with contact record ID
write
Step 5
Slack
Post new lead summary to #sales-new-leads channel
Result
Create Record — new Contact record with all HubSpot fieldsPerform Script — run 'Assign Territory' with contact record IDPost new lead summary to #sales-new-leads channel
The win
Saved per run
12 min
Runs / week
~40×
Every lead reaches FileMaker without a rep copy-pasting between tabs
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    60 min / week
    Manual lead entry into FileMaker

    Reps copy new HubSpot leads into FileMaker by hand — pasting name, email, company, and source into individual fields, then switching to FileMaker to trigger the territory script manually.

    Sales Agent
    0 min
    Agent syncs leads and fires scripts automatically

    When a new contact enters HubSpot, the agent deduplicates against FileMaker, creates the record, and runs the territory-assignment script — the database is current within about a minute with no rep involvement.

  • Marketing
    120 min / week
    Manual export and deduplication before campaigns

    The marketing team exports the FileMaker contacts table to CSV, checks for duplicates in a spreadsheet, and reimports the cleaned list before each campaign — a process that takes two hours each time.

    Marketing Agent
    0 min
    Agent finds and flags duplicates before the import

    The agent runs a Find Records query before each import batch, identifies duplicates by email, and excludes them — the marketing team gets a clean list ready to use without touching FileMaker or a spreadsheet.

  • Customer Support
    200 min / week
    Agents manually create and look up FileMaker cases

    Support agents switch between the email inbox and FileMaker Pro, manually create a case record for each inbound email, look up the customer account, and then reply with the case number — adding 5-10 minutes per ticket.

    Customer Support Agent
    0 min
    Agent creates cases and sends acknowledgements automatically

    When an email arrives, the agent finds the customer in FileMaker, creates the case record, runs the priority script, and sends the acknowledgement — support agents see a pre-populated case rather than a blank form.

  • Human Resources
    90 min / week
    New hire records entered manually into FileMaker

    HR specialists copy data from the offer letter and HRIS into FileMaker Pro fields for each new hire, then manually trigger the provisioning script — a 30-minute task per employee that frequently slips on busy hiring weeks.

    Human Resources Agent
    0 min
    Agent creates the record and fires onboarding on day one

    When a new hire row appears in the onboarding sheet, the agent creates the FileMaker employee record, triggers the provisioning script, attaches the signed offer letter, and posts the welcome — before anyone opens FileMaker Pro.

  • Finance
    45 min / week
    Overdue invoice list built manually each week

    A finance team member opens FileMaker, runs the overdue find manually, copies the results into a spreadsheet, and formats the list for the weekly review — a Friday morning ritual that takes 45 minutes.

    Finance Agent
    0 min
    Agent delivers the overdue report before the team is in

    Every Friday at 08:00, the agent runs the find, writes results to the Google Sheet tracker, marks records as followed-up, and posts the summary to #finance — the report is ready before the first person sits down.

  • Operations
    40 min / week
    Database maintenance scripts run ad hoc when remembered

    Ops staff open FileMaker Server Admin Console, navigate to scheduled scripts, and run maintenance jobs manually — often skipped during busy periods, leaving log records and data quality flags accumulating.

    Operations Agent
    0 min
    Agent runs maintenance scripts on a nightly schedule

    The agent confirms the database is online, fires the cleanup script, checks for data quality flags, logs results to a Google Sheet, and posts a health summary to Slack — every night without anyone remembering.

  • Legal
    60 min / week
    Contract expiry dates checked manually each week

    A paralegal opens FileMaker, runs a find for contracts expiring in 30 days, manually creates renewal tasks in the task system, and emails the relevant contact — an hour-long Monday ritual that slips when they are busy.

    Legal Agent
    0 min
    Agent surfaces expiring contracts and creates renewal tasks

    Every Monday at 09:00, the agent finds expiring contracts, creates Notion renewal tasks for each, marks the FileMaker records as notified, and posts a digest to #legal — the team never misses a renewal window.

+ 100s of other FileMaker automations
Average time saved
62 hrs / person / month
Calculator

Calculate what your team saves

Team size
8 people
Hourly rate
$75 / hr
Hours saved / week
20
Hours saved / year
1,000
Annual ROI
$75,000

Based on FileMaker's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug FileMaker into Actionist

Pick the connection method that suits your environment.

FileMaker's Data API uses a session-token flow: provide your FileMaker Server URL, database name, account name, and password. Actionist exchanges these credentials for a bearer token and refreshes it automatically on expiry.

1
Enable the Data API extended privilege

In FileMaker Pro, open the database, go to File → Manage → Security, and ensure the account you plan to use has the fmrest extended privilege enabled. Without this, all API calls return 401.

2
Enable the FileMaker Data API on the server

In FileMaker Server Admin Console, go to Connectors → FileMaker Data API and toggle it on. The API endpoint is at https://<yourserver>/fmi/data/v1.

3
Enter credentials in Actionist

Paste your server URL, database name, account name, and password into the fields below. Actionist fetches a session token and runs a test Find to confirm the connection.

Credentials you'll need
Server URL*
e.g. https://yourserver.example.com
Database name*
The hosted FileMaker database filename (without .fmp12)
Account name*
FileMaker account with Data API extended privilege
Password*
Password for the account above
Actions

14 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

0 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

This app has no triggers yet.
FAQs

Questions about FileMaker + Actionist

How does Actionist connect to FileMaker?
Actionist connects to Claris FileMaker using the FileMaker Data API, a REST interface built into FileMaker Server and FileMaker Cloud. You provide your server URL, the name of the hosted database, and account credentials (account name and password). Actionist authenticates once to obtain a session token and refreshes it automatically. Before connecting, make sure the account you use has the fmrest extended privilege enabled in FileMaker's security settings, and that the Data API connector is turned on in the FileMaker Server Admin Console.
What FileMaker Server version do I need for the Data API?
The FileMaker Data API was introduced in FileMaker 17 and has been stable since. Any FileMaker Server version from 17 onwards (including 18, 19, 20, and Claris FileMaker 2023/2024 releases) supports the API endpoints Actionist uses. FileMaker Cloud (the hosted SaaS offering from Claris) also supports the Data API. Older FileMaker Server versions prior to 17 do not include a Data API and cannot connect to Actionist.
Can Actionist work with any layout in my FileMaker database?
Yes — you specify the layout name in each action. The account connecting via the Data API must have at least read access to a layout to fetch records, and read/write access to create or edit records on it. Layouts that use external data sources or that reference unstored calculation fields may return partial data — design your integration layouts to include only the fields the agent needs, following Claris's recommendation to use dedicated API access layouts. Get Layout Metadata is useful for confirming which fields are available before configuring actions.
Can I run FileMaker scripts from an Actionist agent?
Yes. The Perform Script action calls any named script in your FileMaker database and can pass a parameter string. Scripts run on FileMaker Server (server-side scripting), so they execute without a client session and can access all server-side script steps. Script triggers attached to layouts or fields are not activated through the Data API — only explicitly called scripts run. Use Perform Script to fire reporting exports, email dispatches, data validation sweeps, or any server-side automation your database already has scripted.
Does Actionist support FileMaker container fields?
Yes. The Upload to Container Field action lets an agent attach a file (PDF, image, Word document, or any binary) directly into a container field on a specified record without opening the FileMaker client. Common uses are attaching signed contracts to contract records, archiving invoice scans against invoice records, and uploading employee photos to HR records. Container field downloads (reading the binary back out of FileMaker) are not a current supported action — contact Actionist support if this is a requirement.
Does FileMaker have real-time triggers or webhooks?
The FileMaker Data API does not expose native webhooks or push-based event triggers. That means Actionist cannot listen for a record change or a script completion in real time. Instead, you use scheduled agent tasks on a polling cadence — for example, running Find Records every 15 minutes to check for new or modified records, or triggering a daily Perform Script at a set time. For time-critical workflows, keep the polling interval short and use FileMaker's built-in scripting to stamp a timestamp or status flag that the Find query can detect.
How do I handle FileMaker finds that return too many records?
The Get Records and Find Records actions support pagination via offset and limit parameters. For large result sets, the agent pages through results in batches (typically 100 records at a time) until all matching records have been processed. If the dataset is consistently large, consider using a dedicated FileMaker script (Perform Script) to do the heavy aggregation server-side and return only a summary — this is faster and avoids pulling thousands of records across the API.
Can Actionist work with FileMaker Cloud as well as on-premises FileMaker Server?
Yes. Both FileMaker Cloud (Claris's hosted SaaS product) and on-premises FileMaker Server expose the same Data API endpoints. The connection setup is the same — server URL, database name, account name, and password. For FileMaker Cloud, the server URL is the Claris ID-authenticated cloud host URL provided in your Claris account dashboard. The one difference is authentication: FileMaker Cloud requires a Claris ID token in addition to account credentials on some API endpoints. Actionist handles this automatically when the Cloud connection type is selected.