Triggers
Triggers are the starting point of every Flowgine workflow. They listen for something to happen, capture the payload, and hand control to the rest of the automation.
Supported trigger types
1. Event-based triggers
These listen to Strapi lifecycle events (create, update, delete, publish, etc.) or other events emitted through the EventHub. Use them whenever you want workflows to respond instantly to content or admin activity inside Strapi.
2. Schedule-based triggers
Use the Scheduler app to run workflows on intervals. Flowgine currently ships hourly, daily, and minute-based schedules, and you can add your own cron-like logic when building custom triggers.
3. Webhook triggers (coming soon)
Webhook triggers will allow Flowgine to start workflows from external services. They are on the roadmap, so you can already plan flows that react to third-party systems, even if today you rely on HTTP actions as a workaround.
Anatomy of a trigger
- Key & name – Identify the trigger inside the workflow builder.
- Fields – Prompt the user for any configuration needed (filters, model IDs, cron expressions, etc.).
- Runner – An async
runfunction that listens for the event and posts payloads into the Flowgine execution queue.
When a trigger fires, Flowgine packages the input data and passes it to the first action node in your workflow, where you can reference it through Flowgine variables.