GuiB

@Kamil can you please try this workflow and let me know if you are getting any outputs? https://alfred.app/workflows/alfredapp/deep-contacts-search/

Well, I just had a rapid look at it... Here is an updated one that work with Python3. Yes, I need to do a git repo and push it to the Alfred Gallery, but here is an updated version if you want to try and let me know if it works on your side! Download: https://d.pr/f/SX4Sn7

Yes I need to update the Workflow to use Python3 instead of 2. I did install Python 2 on my computer to make multiple of my workflows work again since I moved my OS version, but yes I need to do an update to this one and share it so anyone can keep using it I'll have a look as soon as possible. My days are very busy since many months, but I should manage to do it soon! As for the "chc" keyword, can you give me more input on your problem with this one? Do you have any error message? This is using standard Alfred objects and scanning the standard address book directory "~/Library/Application Support/AddressBook". I would think this should still work and I'm not having a problem with it on my side. I'll think some more and try to determine what it could be!

A new Workflow Gallery website is in the work and will be released after v5, as mentioned by @Vero in this post:

Hey @Andrew and @Vero ! Congrats on the new version! This looks great and I’m loving the attention to details! "Automation Tasks" looks to be a good idea to make Workflows work without breaking on system upgrade by keeping the actions maintained with Alfred. I’m looking forward to how this develops and also to the release of the task development tool! Again, congrats and all the best!

I like to use the "Quick File Search mode" to rapidly get to a file by its name and most often I get what I want especially if it's a file that has been used recently. To access this mode, make sure to have it active in your Alfred Preferences at `Features -> File Search -> Quick Search [x]`. You have access to it from a standard Alfred search but by prefixing your search term with ' character or typing the spacebar.

Hmm, you're right, I think I see why I had trouble... I've been testing with TextEdit and set it to Rich Text, but when I run the script it doesn't work, but it works when we drag and drop the file into the text field and then it asks if we want to switch to RTFD and then it works. I may have done those kind of manipulations before seeing that it worked with that strange script of converting from one to another POSIX file/path... So, to put it there, this should work on a RTFD document: set filePath to "/path/to/an/image.jpg" set the clipboard to (filePath as POSIX file) And here is a workflow as example: https://d.pr/f/JneYcR

Yes, I know it has always been strange to me as well, but this is the only way I found out at that time to make it work with simple AppleScript commands. I'll see if I can find a simpler way, but at the moment this should work. Pasting a simple `POSIX file (filePath)` doesn't work, at least, not on my tests...

This look like my script and I've tested again and it seems to work on my side. Do you have connected the "Run Script" to a "Dispatch Key Combo" set to CMD+V to do the paste action ? Another point, are you testing your workflow in a text field that accepts rich text so the image can be pasted into it ? It's better if you send the complete workflow instead of a screenshot of a single element if you want anyone to test it completely and try to find the bug.

You're right, I should have added the "+" character! However, since the ".spa" file isn't a standard zip file and @Chris Messina didn't have a default app to open this file, I don't think a filetype would be defined correctly and set to be a subtype of "public.zip-archive"

I forgot to add, make sure to press the "Modify all..." button just under so all the files with this extension will be set to open with the The Unarchiver on your system. Yes, I understand and I think it would be great as well to add all those things to the Universal Actions. @Andrew said that he have many plans to improve the Universal Actions feature, so those may be part of them... Or in the meantime, users could create workflows to add those features. Beside, here is my version of the Zip action: https://d.pr/f/xamxKe It's using the Finder Compress feature and using Automator to get a cog icon in the menubar so we know it is compressing the file.

Then maybe you should set a default application to use for those kind of files. (Get Info -> Open With -> The Unarchiver) Or you can use the "Open with" Universal Action to specify with which application you want the file to be opened. Or you can define a File Action that would work with Zip files and ".spa" files and that would be set to open the file directly in the specified application. Here is an example with the The Unarchiver: https://d.pr/f/nT46SC You may need to add one of your ".spa" file into the File Action type that it will show for. I dropped a file with a ".spa" extension on my side, but since I don't have any application that work with this kind of file, I'm not sure if the metadata are set correctly... Beside, even if Alfred have a built-in unzip action, then there's good chances you won't be able to use it with your ".spa" file since this is not a standard Zip archive type. So, I think the workflow to open with The Unarchiver or to set the default app for this kind of file to The Unarchiver are your best options.

Universal Actions is, from Alfred's website: a new way to "take any text, URLs or files and perform actions on them from anywhere within Alfred or on your Mac using your Universal Action hotkey"... "The Universal Actions panel only shows you the relevant actions for the type of item you've selected." In other words, it's simply a new way to access a list of actions relevant to a specific type of selection (Files or URLs or Text) and is some kind of an extension to the File Actions. At the moment, when invoked while selecting a file, we have the same list that we had with File Actions, but with Keywords + Script Filters objects if you activates those in the Universal Actions preferences section. There was no zip/unzip action for File Actions before and no built-in actions were added at the moment. However, you can define your own action with a Universal Action object in a workflow. That would be great, maybe that will be added later... I just downloaded the workflow, I didn't really test it, but I can see that the File Action and the Script Filter object appear correctly inside the Universal Action list. However, it may be hard to know which one is which kind since they both have the same title "macOS Services". So, to use @deanishe's workflow functionality you need to first select the "macOS Services" action in the Universal Action list and then the list of Services will appear. However, I never tried this workflow before, but I'm not getting my files Services, so you may not get what you want, but at least I think this gives you the idea regarding how Universal Actions work.

Great then! What I wanted to mention with the "not well-defined" is that I'm questioning why some actions combine the items by default (ex: "Email" + "Email to..." action), but others don't... From what I can think of is that the Email actions work with multiple elements since the "File Action" worked with multiple files before Text Actions existed, but I'm wondering why other built-in actions don't combine the items to make other built-in actions possible (ex: "Copy as Plain Text"). It's not a problem to create a workflow that would combine the items and then pop the Universal Action with the combined items as a single argument (and may be wanted in case that we don't want a new line between items), but I'm simply questioning if the default behaviour of the built-in actions should work in the same way as the "Email" actions so the behaviour is similar between each of them

You're right, it's the workflow developer job to make sure all the items are processed from the argv. I was just testing with the option active to see how it goes, but myself I find activating the "Keyword" + "Script filters" add too much clutter and prefer to add the Universal Action workflow object. Again, you're right! Sorry, I created a script that is set as the default web browser and which send the open URL to the active browser instead of defining a specific one and my script was simply using the first item. Sorry for that!