jdfwarrior

Are you currently using any software to sync settings to other machines such as Dropbox, Google Drive, etc? If so, then most settings could easily be restored after the reinstall by allowing all files to sync back to your machine, then setting up syncing in Alfred again.
 
If you currently aren't using some 3rd party app to sync settings, then Alfred's preferences and settings live at ~/Library/Application Support/Alfred 2/
Those settings could be copied or backed up and restored after the reinstall. 

To make a new window in Safari, you could do the following...
 
Make a new workflow, add a hotkey, add a run script, set the language to osascript and enter the following code.
tell application "Safari" activate make new document end tell

Are you familiar with creating Custom Searches in Alfred? Custom Searches will let you use custom urls for a site to search it from Alfred. Copy the url below and enter it into Alfred. This should import a custom search that will allow you to search the site you inquired about. The keyword for it is 'tax' and uses the same search parameters the site does. So, in Alfred you would type 'tax Public John Q'
 
alfred://customsearch/Property%20Tax%20Search/tax/ascii/plus/http://www.jcsoky.org/ptax_search_results_name.asp?WEONM1={query}

I don't have access to the latest version of Outlook but just taking a glance at the workflow you mentioned, it looks like there may be one other thing to change. Without being able to see the structure, I can't confirm that this will fix it but, let try this..
 
In the workflow, it also specified a file type. The workflow specified a com.microsoft.outlook14.message file type. Try navigating to the area that you know the data resides and find a file that you can confirm is an outlook message. Remove the current file type in the workflow, then drag one of the files that you believe to be a message into the file types box. It COULD be that it was attempting to filter on an outdated file type.  As mentioned, this is just a guess. Let me know back how this works please.

Click/Select the item and press the Delete key. You'll be prompted for confirmation before deletion.

Following Tyler's note and to agree, it's not available "yet". Alfred Remote is the result of a lot of time and effort on Andrew's part and certainly couldn't be considered a "rushed release". Software is an iterative process. Every software package has updates, fixes, and new feature additions. If any software product was withheld until every possible feature, every fix, every bug, every idea was implemented, we'd never see any of them. That being said, this is only the beginning for Alfred Remote. Andrew has lots of other ideas planned.

The clipboard feature would be helpful if you were doing this manually. To automate it though you would need to be familiar with AppleScript as this would require a little UI scripting. 
 
The clipboard feature is useful for copying multiple things and then having a UI to view previously copied text and being able to paste multiple past items. As mentioned though, this is a manual step.

If you are a Powerpack member, then the way to do this would be with a workflow. In Alfred's preferences, click the Workflows tab, then click the + icon in the bottom of the list panel on the left. In the menu that appears, click the "Blank Workflow" option. Set the name and other such properties for your custom workflow. Next, in the editor area on the right, click the + in the top right corner. Select to add a Trigger->Hotkey then set the properties for the hotkey. Next, click the + in the top right again and select Actions->Run Script. From here, you can configure what you want to run. You can leave the language set to bash and enter commands to run the script the exact same way you would if you were at a Terminal. Alternatively, you could set the language to Python and enter your code here directly. Once you are done setting up the Run Script, save it and position your mouse over the hotkey item. A little tab should appear on the right side. Click the tab and drag it to the Run Script to connect them. After that, you should be all set. Let me know if you need any more assistance

An upcoming version of Alfred will provide support to Airmail 2. 

Alfred using Cmd+Down you can begin typing again to filter them. Now, this isn't the same as performing an actual search so it wouldn't traverse multiple levels. It would simply allow you to filter what is visible within that folder. Is that what you are looking for? Also, you can use wildcards when filtering them as well so, *.xlsx would filter and show Excel files

Alfred could do something things like this with AppleScript. As long as it's form fields you are filling or other items that you can reliably tab through to, AppleScript should be able to help some here. Clicking items that don't have a tab index wouldn't be possible though. All this would be done by simulating keypresses and such. So for instance, you click the first field, press a hotkey or something to activate a workflow that runs Applescript to fill in that field, press tab, fill in the next, press tab, etc, etc.

Well, there isn't a built in way to do this but the snippets are stored in a file that could be shared. The only down side of this though would be that, if they have any fo their own setup, it would overwrite those. The file is a sqlite database so, if you know how to tinker with sqlite you could get around that. Otherwise, if it's not a big deal for the user to lose their own snippets, then you could find the snippets.alfdb file where your preferences are located.. Alfred 2.alfredpreferences/clipboard/snippets.alfdb

You can actually, from the Web Search preferences, double click on the "lucky" keyword and edit it from there

Stuff like this is a lot easier done with External Triggers now days.
 
For instance... you have a keyword that goes to an external trigger. That triggers ties to a script filter that shows the list of all boards. Selecting that passes data to run script that, based on what you select, hits another external trigger to another script filter. This time to show the lists for that board or.. if you hit a previous link at some point, go to the previous external trigger. That would be my recommendation

Another way to do this would be to use External Triggers and a Script Filter. Do whatever you need then use an Output->Run Script, to call an External Trigger. The External Trigger is connected to a Script Filter with 2 options, a Yes and a No, or a Description (with valid=false) and a Yes and No. Then just proceed based on what they select. Personally, I would prefer this over the AppleScript dialogs

Updated 3/18:
NOTE: Set your location again so a default weather unit gets set initially, then change it.
Removed saving to the Workflow Data folder and actually save IN the workflow folder now. Should fix issue a few users are seeing and also allows syncing weather location.
 
Download

To expand on what Chase responded...
 
This is set up to be a result action. So, that being said, find any folder in Alfred via the regular search method or via the file navigation, press the right arrow to display the result actions, and select Add to Favorites.

Formerly called Favorite Folders, now allows you to set any file, folder, or application as a favorite.
 
A user requested this under the help and questions forum and i really liked the idea of it. I threw it together really quick for them but thought I would share with you guys as well. Not sure if something like this has been made already or not but, here is my rendition of it.
 

 
The idea is to have a list of items that you access often, saved in a list and easily accessible. Results are actionable, can be opened by pressing Enter, browsed in Alfred by pressing Cmd+Enter, or removed from the Favorites List with Ctrl+Enter.
 
Download

Follow up.. talked to a buddy and the hotkey is coming so at least it can be faked until Mailbox team adds AppleScript support. I emailed them and suggested it already

The keyword to search within a file is "in" and not "find in" unless you have edited the keyword for this function. This does require that Spotlight can read the text content of the file. 

I've been trying out Alfred on Yosemite since Yosemite was launched and have found that most, if not all, functionality works just as expected. In Yosemite DP1 there were a few issues but this was related to Yosemite and not to Alfred. DP2 seems to have resolved them.

I've not seen this but that doesn't mean much. I'm not sure how scriptable that part would be (interacting with that save dialog). It could be totally easy, I've just never seen it done. Perhaps someone else knows of a way to do this. I'll look at it though and see if I come up with something

If you wanted to get really fancy...
 
You could... Let hazel pick up the file, then Hazel would use AppleScript to.. tell application "Alfred 2" to search "<full path to file>"
That would bring up Alfred in file browser with that file selected, then you would have the option to run any action on it. To continue though, you could have a custom "move and open" action. Then, save the file name in a temp place, use external triggers to hit a next step in the workflow that is a file filter that would only show folders so you could search for the folder to move to, when you press enter, it moves to that folder, then opens the file. 
 
Ya know... if you wanted to get fancy.. hehe

Please see this newer thread for a more up-to-date list of libraries that support Alfred 3 and beyond.
 
Since the introduction of Alfred 2, there have been several extremely useful utility classes and other helpers crop up that simplify a lot of the tedious, common tasks associated with creating workflows. These utilities are developed and maintained by community members, not by the Alfred team. All support requests for these utilities should be directed to the original author.
 
If you have another utility class that needs to be included in this list, send me a message or email (david@alfredapp.com) with information about it (name, description, short list of features, link to post or download page) and I will make sure that it gets added to the list.
 
Special thanks to all the developers for their hard work and for sharing their work with us.
 
 
Python
 
Alfred-Workflow (by deanishe)
 
A state-of-the-art Python library for Workflow developers. Support for Alfred 2 and 3.

The library is simple to install, has no external dependencies, is very well-documented and maintained, and boasts an eye-wateringly high feature-to-size ratio at just 140 KB.

Main features
Catches, logs and notifies users (and developers) of errors in Workflows. No more confusing, silent failure. Super-simple, yet powerful data caching (e.g. from a web service) and storage. Easy-to-use storage of Workflow settings. Keychain access for secure storage (and cross-machine syncing) of sensitive data, like passwords and API keys. Tunable and understandable Alfred-like fuzzy search (e.g. got matches Game of Thrones as well as Baby Got Back. Or not: that's up to you.) Now with solid support for multi-word queries. Extremely lightweight, but full-featured, HTTP library with Requests-like interface, but just 12 KB instead of > 2 MB. Convenient access to standard OS X icons, for high-quality, familiar icons without adding size to the library. Also available via proper English. Pre-configured, built-in logging to enable simpler Workflow debugging. Painlessly run (update) scripts in the background without blocking your workflow, so you can still show "old" results while fetching new ones. Supports Alfred's new (version 2.3) modifier-specific subtitles. Simple support for 3rd-party libraries your Workflow relies on. "Magic" arguments to make developing/debugging Workflows so much easier, especially when helping less technically-inclined users. With "magic" arguments, you and your Workflow's users can open the Workflow's log file in Console.app, its cache and data directories in Finder, and its root directory in Finder orTerminal from the comfort of Alfred's query box. You can also delete the cache/data/settings if something is corrupted. Your workflow can update itself via GitHub releases. Accent-folding, so you can search non-ASCII text (e.g. voilà will be matched by voila) Functions to support migrating settings/data from older versions of your workflow. Well supported and kept up-to-date with Alfred's features as they are added. Alfred 3-only features
Workflow variables Advanced modifiers Alfred 3-only updates  
And as you can see from the above links, there is extensive documentation, including a two-part tutorial on building a Workflow from scratch.

Examples

Here are a few examples of how you can do some pretty cools stuff in just a few lines of code.
A simple Workflow I made to search Packal in ~90 lines of code. A simple Workflow to search your recent Pinboard posts in ~50 lines of code. A polished, user-friendly, wicked-fast Workflow to search your recent Pinboard posts in ~200 lines of code. Remember, each of these Workflows also has—for free—full error-catching and -logging support, and the ability to open its log file (which contains all errors) via Alfred's query box. No need to ask users to grub around in ~/Library or flounder in Terminal here. This is not the Workflow library 2014 deserves, but it's the one it needs  
 
Alp (developed by phyllisstein)
alp is a Python module for developing Alfred workflows that bridges the gaps between Python and OS X and Python and Alfred, making the process of creating a workflow quick and easy. As it's essentially a collection of shortcuts for common and repetitive tasks, developers will find that working with alp results in less and more efficient code and a generally more sane workflow development experience. A painstaking guide to its various features, bells, and whistles is available in the README at the Github repository.
 
Features:
Simplified generation of feedback XML. Shortcuts for bundle ID, storage paths, settings, and arbitrary plist and JSON files. OS X interaction features, including the sending of additional notifications, interaction with the Keychain, and interaction with Spotlight. Internet interaction features, including bundled modules for making and caching HTTP requests, parsing markup data, and sending e-mail. The ability to remove unneeded modules for a svelte workflow bundle.  
Alfred-Python (developed by JinnLynn)
alfred-python is a full-featured python module that helps building Alfed workflow quick and easy.
  Features: Simple feedback XML generation Provides functions for storing or retrieving cache data Workflow configuration management Includes an easy way to download remote file Easily get bundle id, query arguments, etc. More code example can be found on my own workflows.  
 
 
PHP
Workflows (developed by David Ferguson)
Workflows is a PHP library for building Alfred 2 workflows using PHP. Installation is quick and easy. Just drop in the Workflows.php class file, import it into your code, and initialize it. Full documentation, with usage examples can be found on David's blog.
 
Features:
Simple XML generation Read/writing files as plain text, json, etc. Read/write plist values Find local files Provide access to commonly used paths (home, cache, current, data storage, etc) Easy HTTP/cURL requests  
 
Haskell
AlfredLibraryInHaskell (developed by raguay.customct)
This is a Haskell library for creating Alfred workflows.
 
 
 
AppleScript
qWorkflow (developed by ursanrazvan)
qWorkflow is an AppleScript library for creating workflows with Alfred 2. This library provides an object-oriented approach for working with plist settings files, reading and writing data to files, generating Alfred feedback results, requesting remote data, parsing JSON data, and more.
 
Features:
object-oriented approach to write less & more readable code heavily documented with code samples internal workflow introspection (finding the bundle ID, cache & storage paths) generate Alfred-compatible XML feedback with ease saving & retrieving workflow-related settings (with support for default settings file) remote data requests, as well as JSON support sending notifications through the Notification Center various internal utilities that improve AppleScript (string and date manipulation, file system utilities) More info & example workflows created with this support library can be found on the project's github repo
 
 
 
Go
 
goAlfred (Developed by raguay.customct) 
This go library is used to create workflows for Alfred 2 easier in the go language from Google (http://golang.org/). It will automatically create your cache and data directories. It also creates the xml listing for the feedback system. Examples included.
 
Installation and Usage
You install the library with:go get github.com/raguay/goAlfred # (You might have to use sudo). Any program that you want to use the library, just place this line in it: import "github.com/raguay/goAlfred"
 
Functions
The accessible function calls are:
 
goAlfred.BundleId() - This will get your Bundle Id for your workflow.
goAlfred.Cache() - This function returns the location of your cache directory.
goAlfred.Home() - This function returns the location of your home directory.
goAlfred.Data() - This function returns the location of your workflow's data directory.
goAlfred.Path() - This function returns the location of your workflow's directory.
goAlfred.Error() - Returns the last error received.
AddResult( uid string, arg string, title string, sub string, icon string, valid string, auto string, rtype string) - This function allows you to build up the xml string for returning to Alfred.
AddResultSimilar(instring string, uid string, arg string, title string, sub string, icon string, valid string, auto string, rtype string) - This function allows you to build up the xml string for returning to Alfred only if the title is similar to the instring given.
goAlfred.SetDefaultString(title string) - This function sets a different default message if no results have been added.
goAlfred.GetXML() - This function returns the XML string that needs to be given to Alfred. 
 
 
 
 
Bash
BashWorkflowHandler (developed by _mk_)
 
Features:
create feedback xml save/read preferences volatile and non-volatile get workflow's cache dir get workflow's data dir get workflow's bundle id Usage examples can be found in the README at the GitHub repo.
 
 
Bash Workflow Framework (developed by djc)
BASH workflow framework which makes it simple to create a workflow which allows you to display feedback within Alfred after selecting a result, getting around the issue that "Script Filters are the only way to pass feedback to Alfred." Built to create easy reference workflows, or any other kind of workflow which does not want to leave Alfred immediately on selection of a result.
Features:
- Two modes for two different kinds of data: static and dynamic.
- Creation of a static workflow only requires modification of a CSV-like file.
- Static mode handles searching on query for you.
- Dynamic workflow can be created using a BASH library ARF+.
- Both modes allow for result and field-specific icons, validities, arguments, and autocomplete attributes.

Extensive documentation in the README, and examples are included with download. Two methods of installation can be found on the github page.
 
 
 
Ruby
Alfred2-Ruby-Template (developed by zhauwu)
A template for Ruby-based Alfred 2 workflow development.
 
Features:
Use standard bundler to easily package, manage, and update ruby gems in the workflow. Friendly exception and debug output to the Mac OS X Console Automate rescue feedback items to Alfred when something goes wrong. Automate saving and loading cached feedback  
Alfredo (developed by Dennis Paagman)
Alfredo is simple ruby gem that makes it easy to create workflows and items to it. You can get started with only 4 lines of code.   Features:
Generates valid Workflow XML Add items with one line of code Supports all Alfred 2 workflow features  
 
 
Swift
 
AlfredSwiftLibrary (developed by raguay.customct)
 
 
 
 
General
Alleyoop (developed by phyllisstein)
Alleyoop is a meta-workflow that implements a system for updating other workflows. Users can make use of its features by downloading the workflow module and entering the query oop, which searches for compatible workflows and checks for available updates. Developers can implement Alleyoop compatibility with two simple, human-readable JSON files, described in the original post: one stored on a remote server, one placed in the workflow's folder.
 
Alfred Dependency Downloader Framework (developer by Shawn Rice)
Do you want to have versioned libraries and utilities live side-by-side? Do you want to make your workflows smaller but keep or expand the functionality with helper apps? Do you want to make sure that everything works regardless of whether Gatekeeper is active on other users' computers? Then you might consider implementing the Alfred Bundler* dependency framework in your workflows. If you want to see a _very_ basic implementation, then download an example workflow from Packal and open it up to see the workflow's anatomy. The libraries / utilities mentioned below are just pre-defined assets that you can load with no additional work. You can actually use this framework for any asset** by including a small JSON file with your workflow. Take a look at the documentation page on Github or the original post for more information.

You should see this same result if you were to try and move an item from an internal drive to an external in OSX as well. This is the default behavior. You could however make a workflow that would do just as you mention.. copy to the external and delete the source.