Henk van Achterberg

Although this workflow is probably only for a few of us who have access to the Symantec Threat Explorer API, it is pretty cool what it can do! https://github.com/coolhva/alfred-symantec-threat-explorer

When using Alfred 4 some of the workflows stopped working because, in the workflows, a reference was made to the workflow data in the Alfred 3 folder. I used this symlink as a "dirty" way to "fix" this. ~/Library/Application Support/Alfred 3# ln -s ~/Library/Application\ Support/Alfred/Workflow\ Data/ . ~/Library/Application Support/Alfred 3# ls -ln total 16 drwxr-xr-x 5 639061583 1987437277 160 Jun 3 2018 Alfred.alfredpreferences drwxr-xr-x 9 639061583 1987437277 288 May 30 19:02 Databases drwxr-xr-x 3 639061583 1987437277 96 May 25 2018 Plugins lrwxr-xr-x 1 639061583 1987437277 75 Jun 6 16:40 Workflow Data -> /Users/<user>/Library/Application Support/Alfred/Workflow Data/ -rw-r--r-- 1 639061583 1987437277 699 May 25 2018 license.plist -rw-r--r--@ 1 639061583 1987437277 78 May 30 19:02 usage.data