Jump to content

[HOW TO] Script Filters: Reusing a single script filter or chaining multiple together

Recommended Posts

While the new Alfred 3 release is great (converted me into a Mega Supporter) and I'm still in the process of figuring out what to do with all the new toys, I'm curious why there isn't a native workflow action which would re-query with the given feedback and/or variables. Especially now that we have all these utilities to manipulate the stream.


These types of "looping" workflows with Script Filters are pretty common and extremely powerful. It would be nice to be able to get rid of the (flickering) Applescript workaround.

Edited by verbbis
Link to comment

You can get rid of the flickering in 3 by selecting "Don't close Alfred" on a connection.

But yeah, it's annoying that you still have to resort to AppleScript just to get Alfred to open the same Script Filter again.

External Triggers, the official solution to this scenario, are an awful UX dead end, from which there's no way back into Alfred proper.

Alfred still doesn't make the keyword used available to the workflow, either, so you have to hardcode the keyword in AppleScript.

Link to comment
  • 6 months later...

Hello jdfwarrior,


Thanks for sharing. The link looks to be down. If you could repost it, that'd be great.


I'm just getting started with workflows and the idea of reusing one script filter looks like exactly what I need. In my case, I'm using AppleScript to get info from the currently running app, and then doing SQL queries against "{query}". Saving AppleScript obtained info to a file seems like the only way I can think of as to avoid the uneeded rerunning of AppleScript.

Link to comment
  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...