Reference

The tables on this page are generated from the code by pnpm docs, and CI fails if they drift. If they say something, that is what the build does. The activity log format below is written by hand, from apps/connector/src/activity.ts.

Environment variables

Only FM_USER and FM_PASS are required.

Credentials for several files

With more than one profile, each may have its own FileMaker account, named after the profile's slug in upper snake case, falling back to the unsuffixed pair:

FM_USER_SALES_LIVE=...
FM_PASS_SALES_LIVE=...

Each profile also has its own server address, set in the wizard. So files on different servers, such as https://www5.example.com and https://www6.example.com with a different user on each, are simply two profiles with their own variables:

FM_USER_SERVER5=...
FM_PASS_SERVER5=...
FM_USER_SERVER6=...
FM_PASS_SERVER6=...

FM_HOST does not choose the server for a profile. It only pre-fills the address on a new connection. You do not need it when you use several servers.

To add another account, for example when a second FileMaker file or server needs a user with its own privileges:

1. Add the profile in the wizard and note its slug, such as sales-live.
2. Add FM_USER_SALES_LIVE and FM_PASS_SALES_LIVE to .env. Hyphens in the slug become underscores.
3. Restart: docker compose up -d --force-recreate.

Each account needs the fmrest extended privilege for scripts and fmodata for tables. The Connection step tells you whether a file is using its own account or the default one, and which variable names it looks for.

Credentials are read from the environment only. They are never written to the config file and never handled by the wizard, which is why adding a profile with its own account means editing .env and restarting.

Endpoints

/healthz and /docs are deliberately unauthenticated: one is a liveness probe that reveals nothing, the other is this manual.

Tools

A table called invoices, a saved search called unpaid and a script exposed as recalculate_totals produce:

Limits

Config file

One JSON file per profile, under profiles/ on the config volume. You should not need to edit it by hand, but it is plain JSON so you can read it and keep it in version control if you want to.

Activity log format

What the Activity screen searches is plain text on the config volume, so you can also read it on the server, back it up, or feed it to your own monitoring or log system.

/config/activity/
  2026-09-28.jsonl          changes, script runs and admin actions, one file per day
  2026-09-27.jsonl
  reads/
    2026-09-28.jsonl        Claude's reads, only for connections that record them

• One file per day, named by the UTC date of its entries. Each line is one complete JSON object, so the files work with grep, jq and any log shipper that reads JSON lines.
• Old files are deleted whole once they pass ACTIVITY_RETAIN_DAYS (365) or, for reads/, ACTIVITY_READS_RETAIN_DAYS (30). Deletion happens when the connector starts and on the first entry of each new day.
• Times are UTC, in ISO 8601. The Activity screen shows them in your browser's time zone.

Fields

What a read never contains: the rows that came back. A read records the question and the count, so the log does not become a second copy of your data. A change does contain the values written, which is why Activity is for editors and owners only.

One entry of each kind

A change:

{"ts":"2026-09-28T09:05:12.441Z","kind":"change","connection":"sales","actor":"Claude","tool":"update_invoices","record":"INV-70114","fields":{"payment_status":"Paid"},"outcome":"ok","ms":312}

A script run that FileMaker refused:

{"ts":"2026-09-28T09:06:40.118Z","kind":"script","connection":"sales","actor":"Claude","tool":"recalculate_totals","fmScript":"Recalculate Totals","args":{"invoice_id":"INV-70114"},"outcome":"error","error":"FileMaker script Recalculate Totals returned error 401: no records matched the request.","ms":540}

A search, on a connection that records reads:

{"ts":"2026-09-28T09:04:58.003Z","kind":"read","connection":"sales","actor":"Claude","tool":"find_invoices","args":{"payment_status":"Overdue"},"outcome":"ok","returned":50,"matches":400,"ms":188}

An admin action:

{"ts":"2026-09-28T08:59:30.772Z","kind":"admin","actor":"[email protected]","action":"published a connection","connection":"sales","readOnly":false,"logReads":true,"tables":4,"scripts":1}

Searching on the server

# Everything that touched one record
docker compose exec ailimu sh -c 'grep -h INV-70114 /config/activity/*.jsonl'

# Every failed call in the last day's file, with jq on the host
docker compose exec ailimu cat /config/activity/2026-09-28.jsonl | jq -c 'select(.outcome == "error")'

Known FileMaker behaviour

Things the FileMaker APIs do that Ailimu works around. They are listed here because they look like Ailimu bugs and are not:

• OData returns malformed JSON past roughly 280KB. The body arrives truncated mid-number. On a 208-column table, 30 rows come back intact while 40 and 50 do not, and 50 rows of 150 columns also fails: the limit tracks payload size, not row or column count. This is why samples are capped by cell count.
• $count=true inline is ignored. FileMaker answers the /$count segment instead, and refuses that request if Accept names a type.
• Percent-encoded quotes, parens, commas and colons are rejected by FileMaker's OData parser, so those are sent raw in filters.
• Without $top, up to 10,000 rows come back. Every read is bounded.
• A container field is returned as the file itself, base64 inline. A single row can reach 1.4MB this way, so containers are never exposed.
• The Data API lists scripts by name only: no body, no parameters, and a duplicated name cannot be addressed by script=.
• A table appears once per relationship path. A large file can expose 231 entity sets covering around 75 distinct tables. The wizard groups the copies and shows you the plainest name.