Task-specific agents for the FileMaker workflows your business already runs.
iRusty builds practical agent templates around existing FileMaker systems: agents that review exceptions, prepare approvals, reconcile records, draft follow-ups, and package work for human review before anything important is written back.
Not one chatbot. A set of jobs.
The useful pattern is a named agent with a defined task: exception reviewer, approval queue agent, report builder, order reconciler, or modernization auditor. Each one has a clear input, output, review path, and approval boundary.
FileMaker stays the source of truth
The agent can read records, summarize risk, draft next actions, and prepare change packets. FileMaker remains the trusted system, with human review before client communication, status changes, invoices, orders, or other sensitive updates.
Built around your workflow
A template starts from your actual tables, layouts, scripts, reports, privilege sets, and business rules. That keeps the automation grounded in how your team works instead of forcing a generic AI tool beside the business.
Audit trail first
Every serious agent workflow needs a record of what it checked, what it proposed, which sources it used, who approved it, and what was finally written back. That is what makes the automation inspectable instead of magical.
A FileMaker development floor, not a chatbot
The strongest agent work is controlled and inspectable. iRusty frames each FileMaker request as a bounded job with intake, triage, builder work, review, proof, and follow-through before anything sensitive changes.
If the inherited FileMaker system is already brittle, the right first move is often a rescue or reliability audit before layering in more agents. A named agent does not fix a lying report, a fragile script path, or undocumented write-back assumptions by itself.
Bounded work
Each task starts with the client, file, environment, layout, script, table, risk level, stop conditions, and proof target. That keeps the work narrow enough to review.
Native FileMaker execution
Worker machines use FileMaker Pro, approved files, screenshots, schema notes, scripts, and WebViewer packets. FileMaker remains the operating record.
Review before follow-through
Screenshots, logs, record IDs, rollback notes, and reviewer verdicts decide whether the task passes before client messages, production write-back, or broader rollout.
Start with a typed workflow contract
A FileMaker agent template should not rely on loose prompt instructions for work that touches scripts, records, approvals, reports, or write-back. The stronger pattern is a typed workflow contract: target object, allowed action, source context, validation gate, reviewer decision, result state, and proof.
In iRusty's local FileMaker Agent Mode smoke test, a typed FileMaker workflow contract compiled to the same FileMaker XML on Watson, Ultra, and Rupert. The shared output passed FMQA with 0 errors and 0 warnings on all three machines. That proves the contract layer can be reproduced before anyone talks about live production apply.
Contract before tools
The workflow names the FileMaker object, the exact operation, the evidence needed, and the stop conditions before a model or tool is allowed to prepare a change packet.
Deterministic proof gate
Generated FileMaker XML, scripts, reports, or action plans should pass a deterministic QA gate before a reviewer sees the change. Failed checks stay visible instead of becoming quiet automation drift.
Approval before write-back
The first useful agent lane is review-first: proposed action, source record, risk note, approval status, result, and proof receipt. Live write-back waits until the business approves the lane.