Repository navigation
Workflow generator needs to include triggers #1089
Description
Hit a bit of a problem
The workflow generator produces nice workflows for us, with nodes and edges.
But they're trigger-agnostic. They don't know what a trigger is, and don't add one.
In lightning state, triggers have special rules. They must exist. A step must have a source_trigger_id.
In order to test the same workflow in CLI and Lightning, we need to add proper trigger support to the workflow generator.
I'm not even sure how we'll do that really. Aside from the syntactic problem, nothing in the kit stack really gives any special provenance to triggers. How will the statefile generator look at a workflow and know to convert a node into a trigger?
Activity
josephjclark commentedon Oct 24, 2025
Ah but there is hope - the serializer will infer the presense of triggers from particular properties (the
typekey being the big one.So if we just give a node a
typeproperty, it'll be treated as trigger right?That's cool if true, but I'd like to explore some syntactic sugar for this in the generator. Maybe a node called "cron" or "webook", with no parent, should be converted into a trigger.