How about a 'conditional' action?

[MuppetGate]

Takes an input from one action and puts it straight out along multiple wires. On each of the 'wires' you can set a value. The action attached to the wire is executed if the wire's value matches the value of the conditional.

[Tyler Eich]

If I am not mistaken, this is possible in PHP and bash, two scripting environments supported by Alfred. David Ferguson's Weather workflow uses conditional switches to determine which icon to display; it is written in PHP.

[MuppetGate]

Handy to know, but I was thinking more of something that would allow you to select the next action in a workflow, rather than select the next statement inside a workflow action.

[CarlosNZ]

Yeah, I'd like to be able to select whether the output goes to a notification, or to Large Type, depending on conditions in the script.

 

I realise this is probably not that feasible under the current architecture (one module just captures the output of the previous), but maybe it could be configured to look for certain trigger words. eg. if the output begins with "%LT%", then echo to Large Type rather than notification. Well, that's one way to do it, anyway.

[MuppetGate]

Yeah, I'd like to be able to select whether the output goes to a notification, or to Large Type, depending on conditions in the script.

 

I realise this is probably not that feasible under the current architecture (one module just captures the output of the previous),

 

Mmmm.

 

If you have a look at Vero's Google Searches workflow, it looks as if the actions can have multiple inputs and outputs.

[CarlosNZ]

Mmmm.

 

If you have a look at Vero's Google Searches workflow, it looks as if the actions can have multiple inputs and outputs.

Whoa! I only just realised you can set alternate actions based on the modifier key (option etc.). This will make a big difference to my EggTimer workflow.