Shared Fluent Search Task Projects to boost your productivity!
Download Fluent Search - Download
You can find here Task projects shared by the community that can do various things.
Each Task project has its own folder, with an explanation.
To import a Task project, simply download the .yaml file and drag and drop it into Fluent Search Tasks window.
Feel free to open a pull request for adding new Task projects or refering to a different GitHub page in a README.md file.
Using Tasks you can extend and automate Fluent Search functionality.
Using Tasks you can automate all of Fluent Search features easily by chaining triggers and operations.
Operation is a way to trigger any Fluent Search functionality. It can do anything, like opening a file, invoking a search result, and more.
Operations can be connected to each other and will execute in sequential order - only after the last operation is executed.
Each operation has its own settings and may produce an output (more about that below).
A Trigger is a special kind of Operation that initiates the execution of the Operations chain.
A Trigger can invoke when a user inputs a search, or when a hotkey is pressed.
A Task project is a set of "operations" that are connected to each other, when one of the Triggers is activated, then all cool stuff begins.
Here is a very simple example -
The triggers here are two hotkeys, Ctrl+Alt+M and Ctrl+Alt+Y, when invoked the next operation (connected through line) will trigger.
In this case, it's either the YouTube or YouTube Music apps.
Each operation is configured through settings in its editor window.
For example, here the operation is a search (which is also a trigger), the settings are, as expected, search-related settings.
For this Trigger, you can configure it to trigger when the user invokes a specific search, depending on the search text, tag, and more.
Operations may have an output, when they do you will have the "Output" tab in the editor window.
The output can be transformed into Variables, variables are a set of objects that can be accessed through the entire operation chain.
For example, here the outputs for search are the search text and the search tag.
Configuring a variable value is done through text, the most simple variable value would be "" which would mean it just tasks the result of the operation.
For more advanced cases you can get nested values, as for the search trigger, the result is split into two variables "searchText", which is value is "result.SearchedText" and "searchTag"'s value is "result.SearchedTag".
Variables values are configured through text, but this text is actually based on C#, so any valid C# based syntax should work.
For example, "{searchText.First()}" would get the first letter of the searchText.