AlexA

Amazing, and thanks so much for the clear explanation. I really had no idea how to configure the JSON box. This makes a lot of sense. Again, I really appreciate this.

Sorry about that, and thank you so much for your continued time on this. I really do appreciate it. Here's a link: https://web.tresorit.com/l/iulyI#YTV_OyRpvWt7XOvxES01cg

I'm sure it works, but I'm having a hard time recreating it. Here's what my workflow looks like currently: But I don't know how to configure either the JSON config box or the subsequent File Filter so that the folder I pick in step one is actually used to limit the search in step two. Sorry if this is a really basic question, or if there's some place I should RTFM. Any help much appreciated. Thanks! Alex

@deanishe and @Vero — I've now successfully set up a work flow to search for a tag and then to search for only files with those tags. I used @deanishe's extremely helpful template to start. What I can't figure out, though, is how to do the same for folders. I tried replicating what @Vero has above, but I can't figure out how to use the JSON utility to set the folder scope for the subsequent file filter search. Any help would be much appreciated, and sorry this is so remedial. Thanks, Alex

Awesome. Thanks so much, @deanishe!

Thanks so much, @Veroand @deanishe, for the suggestions. I’ll give the File Filter a try. Do you know whether it’s possible to do something similar for tags? In other words, a workflow where I can first pick a tag (or even multiple tags?) and then search for files? Also, do you think it would be possible for me (with relatively little scripting experience) to make similar workflows where you can start with a folder filter but then do an “in” search rather than the standard filename search? Really appreciate your help! Alex

It wouldn't necessarily search a particular folder, but it would search only folders that match the first filter. That would be quite helpful, I think, because it would allow you to more reasonably limit your searches. But setting aside the folder example, the more general suggestion is to have the ability to use multiple search prefixes. In terms of whether it's possible to do this with Alfred, it seems like it should be, right? Alfred can individually parse each of the searches using a prefix, and then return only the results that satisfy all of them. Right? Of course, I don't know how Alfred actually works underneath the hood, so please forgive any mistaken assumptions. Best, Alex

It would be great to be able to use multiple search prefixes in Alfred. This can be done right now using a workflow to create a pre-defined set of search prefixes. But there is no way to use an arbitrary combination of search prefixes, which would be extremely useful. For example, suppose you want to search a particular folder for files that contain a particular word. It would be nice to be able to search: f [folder to search] in [search text within files] Or suppose you want to search for a file that you know has a particular tag, etc.: in [search text within files] tags [matching these tags] Again, if you know in advance that there's a specific combination of search prefixes that you intend to use frequently, you can set up a workflow. But that's cumbersome and very different than allowing users the ability to come up with these combinations on the fly. By the way, a great example of this kind of search functionality is in the mail client MailMate. The searching in MailMate is so powerful because you can use multiple search prefixes extremely easily. E.g., this search string looks for all emails from any address that matches "alice", to any other address that matches "bob", with the word "confirmation" in the subject, and containing an attachment with "doc" in the filename: f alice t bob s confirmation A doc Thanks! Alex