Search the Community
Showing results for tags 'Fallback'.
Hello forum, What's the best practice for a workflow trigger (keyword or script filter) that uses an optional argument with a fallback value? Example 1 (I made this up): I want to more easily yell at people on the internet, so I have a workflow that turns text to caps. My clipboard is "foo". I call caps and expect my script to receive "foo". I call caps wasd and expect my script to receive "wasd". Example 2: Like example 1, but instead of the contents, I want to use hardcoded text. I call caps and expect my script to rece
Is it possible to remove a keyword that winds up being used in a fallback search? Since I’m probably not asking this question in the appropriate Alfred lingo, let me provide an example. Let’s say you have a file filter that uses the keyword “oo” when searching for OmniOutliner files. After searching for “oo searchterm” in Alfred, it doesn’t find anything relevant, and so you decide to use one of your fallback searches. For simplicity, let’s say you select the default Google search fallback. When run, Google searches for the following: “oo searchterm”. My q
From reading the documentation, it seems possible to add a workflow as a fallback result, but I seem to be missing something. In my case, I have created a nice little workflow that just takes whatever text I have entered, and appends it to a text file. Now, I can invoke this workflow by typing log <my text> which works fine. But I'd like to avoid having to enter 'log' - ideally I'd just enter the text, and select the 'log' action, just like I do with e.g. Google search. I thought I could set this up under Alfred Preferences -> Features ->