Little favour to ask from Workflow Developers

[nikivi]

I hope I am not alone in wishing for this.

 

I like to call all of my workflows from external triggers. However there is one problem with this in that very few workflow developers actually include external triggers with their workflows. Spotify Mini Player for example does actually include external triggers for nearly all functions that are available in the workflow and it is one of the many reasons why this workflow is great. 

 

But most workflows do not. So when I add my external triggers on my own, on next update, everything gets erased and I have to create these external triggers again and again with each new workflow update.

 

The real power with external triggers is that you can call them from other applications. I call all my workflows from Karabiner and it saves me a lot lot of time.

 

So all in all, I do hope you will consider adding some external triggers in the workflows you export and share. I would certainly appreciate it very much. And I hope a few other people here do too.

 

I myself ship all my workflows with both a hotkey trigger and an external trigger.

 

Thank you and I hope you consider adding this little change to your workflows. ?

Edited September 10, 2017 by nikivi

[deanishe]

Why don't you submit a pull request after you've added external triggers?

[nikivi]

That actually seems like a good idea. Although most people only share their code on GitHub, not the .alfredworkflow itself. 

[deanishe]

Because you submit a pull request against source code, not the binary… External triggers live in info.plist.

 

Accepting binaries in pull requests is not a smart thing to do. There could be anything in there.