Trigger Workflows on Platform Changes | FluidGrids Use Cases

Some automations should not wait for an external system to call them — their trigger is something that happens right inside your own workspace. A file lands in a folder and needs processing. A form is submitted and needs routing. A record changes state and needs a downstream action. FluidGrids lets a workflow subscribe to those platform events directly, so the starting signal is the change itself.

You register the interest, not a polling loop. Creating an event registration binds a workflow to a class of platform event, and from that point the workflow is listening — when a matching event occurs inside the workspace, a run is created just as if a webhook had arrived. The same registration machinery that powers external triggers powers these internal ones, so everything you already rely on carries over: your registrations are listed in one place, and each run records the trigger that started it.

Raw event streams are noisy, so filtering is first-class. You can attach a condition to a registration — a filter expression that decides which events actually start runs — and review what each registration is watching for. The "record changed" firehose becomes "record changed to a state I care about," so a workflow reacts to the handful of events that matter instead of every ripple in the workspace.

Control stays in your hands the whole time. You can turn a registration on or off without deleting it, so you can pause an event-driven workflow during a migration and switch it back on afterward with no reconfiguration. Deleting a registration is deliberate and separate. Nothing fires because someone forgot a listener was live, and nothing goes dark because a toggle was the only way to stop it.

The result is automation that closes the loop inside the platform. The reconciliation still runs on its 06:00 cron and the alerting workflow still answers its webhook — but now the workflow that files an uploaded document, or acts on a submitted form, or responds to a changed record, starts itself the instant the workspace changes, with filters keeping it focused on exactly the events worth a run.