Jump to content


  • Posts

  • Joined

  • Last visited

MetalRufflez's Achievements

Helping Hand

Helping Hand (3/5)



  1. That is exactly what I needed, and works wonderfully. Thank you SO very much. I'll update my workflow with a list filter at first, then work on a script to parse `info.plist`, if you have any tips/caveats, please, let me know
  2. 1. All the "tools" are part of the same workflow. As it is easier to distribute this tool amongst my organization 2. Depends on the "tool", most open URLs with an item selected from a filter or passed by the user, others to external scripts or filters 3. Either "Placeholder Title" for Script Filters or "Title" for Keywords 4. Workflow objects. I thought about setting variables for each one to make it more customizable, but decided against it (for now). The screenshot below is a part of the workflow and each keyword or script filter that starts a "flow" is what I consider a "tool". Sorry if I'm not using the correct terms to describe what I'm trying to explain here, long time user, first time workflow developer (also, ignore the loose script in there, I was debugging stuff and forgot to delete it). Generating a list of all available keywords/tools is the lesser issue, as I can always just keep it updated manually (although that's suboptimal). I don't see how I can start one of these "flows" from an item selected in a list or a script filter.
  3. I have a workflow that contains multiple keywords, each one performs a small/quick action and/or opens an internal tool in my company. There's around 20 keywords at this moment. One of my peers asked if I can implement a "cheat sheet" of sorts, where they don't have to remember the keyword for a specific tool, but can search for it. For example: Cheat sheet keyword: wfl Tools: tl1 - Tool1 tl2 - Tool2 tl3 - Tool3 They would like to type "wfl Tool1" and when pressing enter, activate/autofill/substitute what they have typed with the "tl1" keyword, so they can type the argument and execute the workflow for that keyword. If Alfred was able to fuzzy search keyword/hotkey input Titles, it would do what they expect already, but alas it is not the case at the moment. I know about ?keyword, but actioning it, goes to the workflow, doesn't copies the keyword (and also doesn't search the Title) At first I can easily create a script filter, parsing a csv (or variable) that contains tool,description, and pass that as a {query} to the next action, but the I don't know what is the best approach after that. I though about two possibilities here: Have a giant conditional block that receives query, exact matches it and links to every other keyword in the workflow. (Ugly, messy and a pain to maintain) Don't call anything, just copies the keyword to the clipboard and expect the user to open alfred again, paste the keyword and continues with the desired workflow action. Is there another, more elegant, way to reach the same or similar goal?
  4. Thank you for the workflow, but it always left the SysPref window open after I used it and since I don't know/want to learn AppleScript, I reused your icons and made it in bash script. Only problem is that for the Bluetooth toggle, there is no easy way to do this with vanilla osx. You have to install a small utility called blueutil, that you can get here: http://www.frederikseiffert.de/blueutil/ The extension is here: http://cl.ly/2Q3v191C0G37
  • Create New...