kagi

@kagi, I don't know if you've read all the posts above, but @Andrew added the possibility to pop the "open with" action directly with the latest beta update (called "Jump to" in the "Action in Alfred" workflow object). So, if you want to use it right away you can do it!
 
Here is an updated version of my workflow I gave you, but with this new feature: https://d.pr/f/Qb4Pn2

I actually already have a ticket for the Action in Alfred workflow action to pre-select an action, but I ran out of time in 4.5. This will be in Alfred in the future though, then you'll be able to connect a hotkey to it

Yes, that would be great! In the meantime, here is my workaround: https://d.pr/f/6uP48n
 
In short, the workflow simply connect a HotKey workflow object (that work on the selection) to a "Run Script" that contains the script:
on run argv tell application id "com.runningwithcrayons.Alfred" to action argv tell application "System Events" to keystroke "open with" & return end run  

While I'm at it... here is another feature request for the Universal Actions!
 
It would be great to be able to programmatically run a Universal Action, I mean, without popping the actions list. This way, we could create hotkeys that directly trig an action.
 
One example, one file action that I'm using a lot is the "Open with..." and I think it would be great to be able to assign a hotkey that would directly activate this action so I would directly get the list of applications to open the file with instead of needing to select the action first (or doing it with a script that automates typing).
 
The way I'm thinking of implementing it would be to add a "directly run action" parameter inside the "Action in Alfred" workflow action and where we could get the list of available actions from a drop-down menu. In short, like the "Workflow Triggers" button inside the "Call External" object.
 
With that, it is already possible to connect another object after the "Action in Alfred". However it is run directly when the UI pop at the moment. I think it could be an option to make it blocks until the user has selected an action so we can run something after sequentially (maybe having a parameter to specify if we want to run in parallel or sequentially would be useful). This way (and with the possibility to directly run an action) we could chain multiple actions together to make it easy to build workflows with small parts from different workflows and that chain together in the order that we want. I mean, we could do something like: User select a piece of text then run a workflow that do [ "Action: Extract URLs from Text..." > "Run Script: That filter to a specific kind of URL" > "Action: Save as Snippet" ]
 
This could be used as an alternative to the "Call External" object, but where the workflow that is called doesn't need to know the caller and calling it with a specific "Call External" object to return the result since the "Action in Alfred" object will encapsulate the input and output of the workflow.

From everyone replies, I think we all always want more extensibility  
 
@Andrew, I had a play on my side and actually I'm able to get what I want (with the pre-processing of the input) by calling the Universal Actions from a workflow triggered by a Hotkey (so, like I did before, but now I can get a universal actions list instead of a specific workflow when actioned with a string). Right now, I set a condition that if there's no input then I run my script to try to get the file or the URL from the front application and then pop the Universal Actions with the found value or run another workflow if there's still nothing found.
 
So, I would say that I'm good with my request  It would be great to make it faster to have it natively inside Alfred, but I think the workflow object makes it customizable quite well.
 
I don't know if you are trying to build something in this regards during the last days, but if so I'm sure it's going to be great and if not then I'm good with my setup!
 
To get back to @nyc2cal, yes maybe some extra usability options could be great. I also found that with the "Workflow Keyword Inputs" and "Workflow Script Filters" ticked I have a very long list of actions, so I unchecked them at the moment and find it better. However, I think it would be great to be able to configure it more than to set it to all or nothing since there's some workflow I could benefit having there. So, what I'm thinking is maybe it could be great to add an option to the Keyword and Script Filters objects to specify if we want it to appear in the Universal Actions list or not. With that, in the Universal Actions preference, instead of having toggles, it could be a drop-down menu for those 2 types (Keywords + Script Filters) to specify if we want "all of them", "manually activated inside workflows" or "none". I know we can add the Universal Action trigger inside a workflow for that, but I'm wondering how we could disable/activate it when imported from a downloaded workflow (actually, this is something that I think would be great to add to every workflow objects: being able to disable/bypass it so we could tidy our list of actions that appears in Alfred)
 
With that, what I've been thinking that would be great is to add an option to the Universal Action trigger to make it active or not only in specific applications. I think it would be great to add the same "Related Apps" section as the Hotkey trigger so this could be a way to tidy our list and it could be a way to create specific actions list per application (some kind of a command palette) and this could be a way to create and share workflows that "augment" each other to build a list for a specific application.
 
Those are simply some ideas since I think we will get used to filter our list with our input like we always did with the File Actions or the standard Alfred input field, but maybe this can spark you some ideas 
 
One other point, not sure if it's a bug or not, but I've been thinking that some kind of a tagging feature could be great and be used to filter a list to items tagged with the same tag. So, what I've thought was to append the same text to the action titles that I wanted to group (ex: "Copy as Plain Text                     [ @text ]" ; with many spaces to try to hide the tag in the action list, just tried inside a workflow and actually the tag doesn't get hidden since Alfred truncate the middle of the string and not the end), but whenever I modify the text and press Enter then the string revert to the default one. I never tried to change the Default Actions titles so maybe it has always been this way, but I'm questioning why are we able to get a text input field if it's not to modify the title then?
 
One last thing, it is already mentioned at the bottom of the Default Actions list that some actions will only show depending on context, maybe those contexts aware settings could be editable and could be added to the Universal Action trigger?

It occurs to me that Quicksilver's Radial Menu Actions UI would be a pretty sweet solution here... i.e. make a selection (or not), tap your Universal Action hotkey and a menu system like this could appear on top of the selection (obviously modernized):
 

 
 

There you go. This should work.

For all fellow ClickUp users - let me know in case of questions or if you have ideas to improve this workflow!
 
 
ClickUp 2.0 Alfred Workflow
This workflow allows you to use Alfred to quickly add tasks and search tasks within ClickUp 2.0.
Note: This is the first public release - bugs may be numerous. Let me know if you find any!
Installation & Requirements
For this workflow you need
ClickUp 2.0 (will not work with 1.0) Alfred 4 with a Powerpack license To install, download the latest release and open the .alfredworkflow file.
Configuration
Before being able to connect to ClickUp, certain parameters need to be configured. Configuration can be initiated via the cu:config command in Alfred, or by simply typing cu when starting the workflow for the first time. See ClickUp Terminology for an explanation of terms.
The following parameters are required:
ClickUp API key: API token generated in ClickUp (either a public token or a private SSO token). Allows us to connect to your ClickUp account. Example: pk_12345_sdhu2348... Can be retrieved from ClickUp app > Profile Icon (bottom left) > Apps > Generate API key Note: Treat this key as your password. It will be stored in the MacOS Keychain. Id for ClickUp Workspace: Id of the Workspace your tasks reside in. Example: 2181159 Id for ClickUp Space: Id of the Space that defines your available Labels and Priorities. Example: 2288348 Id for default ClickUp List: Id of the List you want new tasks to be added to by default. Example: 4696187 Default Tag: Name of the tag you want to attach to all new tasks (this is only required for the cul command). Example: to_review Note: Your ClickUp user account must be authorized for the specified workspace, space, folder and list.
The following parameters are optional:
Id for ClickUp Folder: Id of the Folder your List is part of. Example: 2844542 Default Due Date: If no Due date is specified when creating a task (via @), this Due date is used. Example: h2 Hierarchy Levels to limit Search Results: When searching (cus, cul) you can limit the tasks returned by Space, Folder, List or a combination of those. For example, limiting by space,folder would use the Id for ClickUp Space and Id for ClickUp Folder to limit the search results by. If you do not provide a value, all tasks for your Workspace will be returned. Show Notification: Whether to show a notification after creating a task. You can validate all parameters via cu:config validate. This should be your first step if anything does not work.
Usage & Commands
Creating Tasks

Tasks can be created by providing a title and optional commands.
cu <Title> [:<Description>] [#<Tag>] [@<Due Date>] [!<Priority>] [+<List>] Press Enter to create the task. Press ? + Enter to open the created task in ClickUp (web) Commands let you add additional information to your task:
Commands are added via one-character shortcuts : Description of a task (max. 1 possible) # Tag of a task (N possible). A list of available tags will be provided and can be filtered by typing e.g. #myLa. Additional tags are specified via another command shortcut, e.g. cu Task #Tag1 #Tag2. If you have specified a default tag, it will always be added. Tags may contain spaces. To create a new tag, simply type its name and press Space. Tags are cached for 10 minutes. @ Due date of a task (max. 1 possible). m<number> Task is due in <number> minutes h<number> Task is due in <number> hours d<number> Task is due in <number> days w<number> Task is due in <number> weeks ! Priority of a task (max. 1 possible). A list of available priorities will be provided and can be filtered by typing e.g. !1 or !Urge. If not specified, priority is Normal. !1 Task has priority of Urgent !2 Task has priority of High !3 Task has priority of Normal !4 Task has priority of Low + List a task is assigned to (max. 1 possible). A list of available lists (ha) will be provided and can be filtered by typing e.g. +myLi. If you do not specify a List, your default will be used. Lists are cached for 2 hours. Commands are optional Commands are separated by space Commands can be in any sequence If no Due date or List is specified via a command, default values are used (see Configuration) Caveat: If you want to use @, ! or + in either title or content, do not use a space before. Otherwise the character will be identified as a command signifier. Examples
cu Clean the kitchen :Before my wife gets angry #Housework @h4 !1 cu Clean the kitchen #Housework #Wife +Personal Searching Tasks
You can search through all of your tasks within your ClickUp workspace. All open tasks matching your search term will be returned. The search uses fuzzy matching, so Test will find Test Task and Ted rest. You can use cus [<status>] to filter tasks by status, e.g. cus [Open].
cus <search terms> Press Enter to open the task in ClickUp (web). Press ? + Enter to close the selected task (Status = Closed). Listing Created Tasks
You can list all of your tasks created via Alfred. This might be convenient if you created tasks in a hurry and want to go through them later in detail.
cul Press Enter to open the task in ClickUp (web). Press ? + Enter to close the selected task (Status = Closed). Note: This only works if you defined a default tag via cu:config defaultTag as the tasks are filtered by this tag.