A workflow needs a reliable starting signal. FluidGrids currently supports five trigger types: manual or API invocation, incoming webhooks, cron schedules, hosted forms, and a failure from another workflow. Choose the one that matches the system you are integrating, then configure its registration against an active workflow version.
Webhooks are the path for external systems: create a registration, use the issued endpoint in the sending system, and inspect delivery records and run linkage when a request arrives. Schedules are the path for recurring work: activate a workflow with a cron registration and the worker creates runs on that cadence. Forms and error triggers cover the supported in-product entry points.
Registrations can be listed, filtered, toggled, and audited. Deactivating a workflow disables its scheduled triggers; delivery and run records make it possible to investigate what started a particular execution.
This page intentionally does not promise platform-event, polling, MCP, or per-vendor trigger presets. Those trigger types are retired; use a generic webhook or schedule where it fits the integration.
Ready to make this your story?
