Workflows created or edited in any version of Alfred are fundamentally incompatible with earlier versions, even if no new features are used.

https://www.deanishe.net/alfred-workflow/guide/update.html#id3

I am using alfred 4, therefore I cannot make it compatible with alfred 3

Install brew https://brew.sh/

And then run this command on a terminal:

brew install blueutil

https://www.alfredapp.com/help/kb/python-2-monterey/

This is the recommended solution by Alfred and the solution implemented from release 3.0.0 and above, therefore I don't recommend to upgrade your workflow if you don't have macOS Monterrey.

export PATH="/opt/homebrew/bin:/usr/local/bin:${PATH}"
eval "$(brew shellenv)"
brew install pyenv
pyenv install 2.7.18
ln -s "${HOME}/.pyenv/versions/2.7.18/bin/python2.7" "${HOMEBREW_PREFIX}/bin/python"

Which should lead to have linked the python bin to this path /usr/local/bin/python. To check if all the previous commands were successful, run this command:

/usr/local/bin/python --version
# Which should print this "Python 2.7.18"

macOS Monterey or previous macOS

• bset: Set the default device
• bc: Connect the default device
• bd: Disconnect the default device
• bcs: Select the device you would like to connect to
• bds: Select the device you would like to disconnect to
• bm:
  • Bluetooth on and off
  • Enable and disabled check of updates
  • Manually check for an update
  • Clear data: Allowing to clear the blueutil path saved(just in case 🤷🏽‍♂️)

Default device = Is the device used in bc and bd commands without having to select one like in bcs or bds.

To get them, run the following commands in your own terminal:

> which brew # paste this command
/usr/local/bin/brew # this is just an example result
> which blueutil # and paste this one
/usr/local/bin/blueutil # this is just an example result

Copy both results and follow the steps in the next point.

Easy peasy! 😋