xilopaint

Done.

Let me try and update the workflow to use User Configuration and sign the binary as well.

When interacting with an app via AppleScript or JavaScript for Automation (JXA), it is common to do so via its name:
 
tell application "Safari" to activate -- AppleScript
Application("Safari").activate() // JXA
 
But often the bundle identifier is a better choice:
 
tell application id "com.apple.Safari" to activate -- AppleScript
Application("com.apple.Safari").activate() // JXA
 
In Alfred’s case, the latter is always preferred. It’s what the External Trigger uses in the example. Instead of Alfred 5, which changes with new versions, com.runningwithcrayons.Alfred is unchanging so it always points to the latest one installed.

This is so good it should be a native Alfred feature. Absolutely necessary for your productivity, not only can you do more without the mouse, you don't even have to create a Hotkey! I'm triggering it with Cmd+Space.
 
---
 
Say if you’re the author or submitting someone else’s workflow.
I'm not the author, @Benzi is.

Share a link to its thread on the Alfred Forum, if available.
 
Share a link to its main page (e.g. GitHub).
https://github.com/BenziAhamed/Menu-Bar-Search

Started working now. Thanks!!

Giphy workflow.
 
Not created by me.
 
Don't know the alfred forum link since I found it via google search
 
Workflow out of the box without any config https://github.com/kejadlen/giphy.alfredworkflow

I suggest describing first what you want. More often than not it ends up being something simple that we can get you up and running with a few objects, teaching you how to make it in the process (you can get very far without a single line of code). Occasionally the request is something not feasible at all, because it depends on controlling another app (or a part of macOS) which has no API.
 
By explaining your request first, people will also be able to assess if their knowledge applies (it’s a spectrum, not a hard line).

I just released a new version of the workflow with some fixes and support for Apple Silicon.
 
 
It's not slow on new Macs but it's possible to make it faster by caching the machine icon generated by the getMacIcon.applescript. Unfortunately my AppleScript skills are a bit outdated so I would be happy if @vitor or someone else could submit a PR.

The Touchbar was an experiment by Apple, which is more or less falling by the wayside now. It's only available on a shrinking subset of Macs. As such, it hasn't been an area of focus given all the other ideas we have that will benefit the broader Alfred community.

I had to create a new Urban Dictionary workflow as my previous one was broken.
 

 
It's available on GitHub.

Workflows are not paid products. 

Alfred Gallery is exciting news for non-coders, but a vscode extension for Alfred would mean an incomparable boost for developers imho.
 
Vscode and Alfred are my top 2 favorite macOS softwares. Integrating both experiences would be amazing news.
 
Please @vitor, come to the rescue! 😄

I love Alfred but the worst part of it is debugging. I would love to have a vscode extension which outputs in the console's editor the same content as Alfred Debugger. It would make the development experience much less annoying as we can focus in a single app (vscode).
 
@Vero @Andrew

I love Alfred but the worst part of it is debugging. I would love to have a vscode extension which outputs in the console's editor the same content as Alfred Debugger. It would make the development experience much less annoying as we can focus in a single app (vscode).
 
@Vero @Andrew

You should see a new enhanced file with the same name of the original one with an [optimized] tag appended. If the file is big the optimization can take some time to finish. You can track the progress using the progress keyword. If the file is not being created I need the output of the Alfred Debugger and, if possible, the original PDF file to investigate the reason. You can send me the file by PM.

Congratulations, you have won a body part! The rump is very good, sir.

I love Alfred but the worst part of it is debugging. I would love to have a vscode extension which outputs in the console's editor the same content as Alfred Debugger. It would make the development experience much less annoying as we can focus in a single app (vscode).
 
@Vero @Andrew

We're planning an Alfred workflow gallery, to which creators will be able to contribute their own workflows.  
 
The project has been in the works for some time but, as a small team, we've prioritised getting a fantastic Alfred 5 release out first.  Once Alfred 5 has launched and users are happily up and running with the new features, we'll be working on an official site for Alfred workflows, as a separate project to v5.
 
Our aim is to create a safe and organised platform, which is easily searchable and browsable.

@vitor I contacted the maintainer of k2pdfopt and he told me how to disable the interactive mode. That was enough to, at the same time, passing the arguments to subprocess.Popen as an array and removing both the echo command and shell=True.

The only issue now is that double quotes are still an illegal character, but this is an issue with k2pdfopt that I already reported to him and he promised to look into.

@buntonn This workflow is actually now bundled into Alfred
 
Launch Alfred 3 to the Workflows tab, click the [+] in the bottom left, and choose Examples > Amazon Suggest.
 
Once you've got this keyword in place, you may wish to disable to default search for Amazon or change its keyword.
 
Cheers,
Vero

Update (v3.1)
 
• Added a Deskew file action.

It works great, even "optimize". Thank you very much for your wonderful workflow (iMac, M1, MacOS 12.2.1.)

Thanks a ton for the update, @xilopaint!! Love this workflow!

Update (v3.0)
 
• Python 3 port.
• PyPDF4 replaced with pikepdf.

Big changes were made in v3. Unfortunately, because of macOS constraints regarding unsigned binaries, the adoption of pikepdf made the new version around 5 seconds slower. Making the new version faster would require the user either installing pikepdf manually or allowing a large amount of binaries, which I decided to avoid.
 
Any feedback about v3 is appreciated.
 
Thanks to @katiefor testing beta builds before v3 release.