Robert Hartshorn

Hey @giovanni I hope I find you well. What is the primary reason that the user needs to populate the scope value via workflow variable? Can they just click the file filter itself and set the scope in the "Scope" tab? 

Thank you @deanishe. I ended up tethering a keyword to the arg util first and that worked perfectly. This is solved!

@Andrew Thank you for the info! Is it possible to set the var in args/vars before I hit the script filter? (object flow: Args/Vars -> Script Filter -> Open File Action). 

From what I can tell the Script Filter needs to come first. But that could just be my infinite density at work  

Hello, 

I am using Alfred 4 along with a custom python script filter that utilizes mdfind to search our company's file shares that are hosted over AFP on a Windows server via a third party tool (Acronis File Connect). Alfred file filters cannot tap into the emulated spotlight index, likely for some good reason that is beyond me, and so with some kind advice from the Alfred team, I went this way instead with a custom implementation of mdfind.

The script filter works great and the results show in Alfred as expected.

My question is: is it possible to pass a workflow variable via the args/vars utility to a script filter?

The reason is: We now need to replace each file filter with a script filter. ATM, that means hardcoding the search scope into the script filter. I would prefer to pass the search scope to the script filter via an upstream variable. I considered Workflow Environment Variables in lieu of the args/var utility, but that got messy quick.

Any advice will be greatly appreciated. One consideration was loading a workflow env variable with key value pairs, casting that to json in the script, and pulling the entry where key = script filter keyword. That seems beefy and I wanna avoid slowing down the script where possible.