Make calling another workflow a step type

When designing workflows, it’s common to create several seperate but connected workflows representing business processes, and for those workflows to call each other.

Right now this is done by creating a HTTP step and calling out to an endpoint at openfn.

A better solution would be to create a Step, set its Type to “Trigger Workflow” (or something), and then select the workflow name from a picklist.

The Step would have a special icon to look less like a regular step.

The Step could have interactions, like double-clicking to open the Workflow in a new window. Or maybe even expanding the other workflow INSIDE the primary one, so you can see all the steps in one place, but the two workflows are still visually distinct

Just ended a call where the user highlighted the need for this feature. Want to be able to trigger a new workflow from a step.

We’d have to think about how this translates to the CLI! In a world where the CLI is executing a project.yaml, the CLI should also be able to trigger multiple workflows in one run. The data is all there.

A quicker solution would be to ignore the other workflow steps and maybe just log a line out.