Backups and schedules
Tell a team when a backup failed, log a clean run, or start follow-up work after a server schedule finishes.
FileMaker Server Pub/Sub
Run automations when your FileMaker Server does something.
Server Pub/Sub listens for FileMaker Server events and runs FM Dojo Flows automatically. Use it for backup alerts, schedule follow-up, database state changes, activity audits, performance signals, capacity warnings, log patterns, certificate changes, and security reviews.
Server event pipeline
A listener turns FileMaker Server activity into one or more Flows.
FileMaker Server
Backups, schedules, logs, users
Backup failed
Database closed
Slow requests spiked
Pub/Sub listener
Filter the event, then choose Flows
Match: production only
Run: alert team
Run: write audit row
FM Dojo Flows
Send alerts, webhooks, rows, tasks
Notify
Webhook
Follow-up
What it can do
Turn server noise into useful work.
A server event by itself is just a signal. Server Pub/Sub lets you decide which signals matter, which ones should be ignored, and which Flows should run when the signal appears.
Database changes
React when a file opens, closes, or changes state so support and release workflows do not depend on someone checking manually.
Users and activity
Capture client connections, disconnects, unusual activity, and access signals for audit trails or support handoff.
Capacity signals
Route disk, CPU, memory, and network pressure to the people or systems that can respond before users feel it.
Log patterns
Watch for warnings, errors, access events, or recurring log text and turn those patterns into structured automation.
Certificates and security
Create reminders or escalation paths when certificates change, admins change settings, or security-sensitive events appear.
Beginner-friendly controls
Pick the event. Pick the Flow. Test it before it matters.
You do not have to build an event system from scratch. Create a listener, choose the server event, narrow it to the right database or signal, attach one or more Flows, then review delivery history.
Post failed backup details to Slack or Discord.
Create a ticket when a production database closes unexpectedly.
Send a webhook after a deployment so another system can validate data.
Append schedule results to a Google Sheet or audit log.
Email a client only when their server needs attention.
Run several Flows from one event, each with its own destination.
Automated response
Automate the response, not just the alert.
Use Server Pub/Sub when FileMaker Server activity should kick off a repeatable process: notify, log, route, validate, escalate, or hand work to another system.