Jump to content

Search the Community

Showing results for tags 'alfred4'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Categories

  • New Features
  • Other

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 6 results

  1. 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.
  2. Hi everybody! OK, I am desperate - I've spent the last two days trying to cobble together a tagging workflow and I am totally stuck... I would be extremely thankful if some of you Alfred-specialists around here could take a look at my issue. I kind of know my way around Applescript but everything else is a total mystery to me. So here it is: The Workflow uses "tag" (https://github.com/jdberry/tag/ - installed via homebrew, if that matters) to assign my custom tags to files selected in Finder. The workflow should work with a hotkey - be it via a "selection in macOS"-hotkey or by telling Finder to get the selection. It should work with multiple files. The tags will be specified inside the script (I will duplicate the script for the handful of tags that I use daily). Edit: nevermind, the bash script works now for some reason... I will never understand this stuff. I give up on the Applescript Cheers, Anna on alfred_script(q) set tagName to "paid" set text item delimiters to tab set filePaths to text items of q set text item delimiters to "" repeat with thisPath in filePaths set theFilePath to POSIX path of (thisPath as text) do shell script "/usr/local/bin/tag --add " & tagName & " " & theFilePath end repeat end alfred_script query="{query}" /usr/local/bin/tag --add paid {query} echo -n $query
  3. This workflow allows you to invoke AirDrop in Alfred by typing airdrop. Compared to hackish solutions that require AppleScript such as this and this, this simply executes airdrop.app directly, giving you the same experience as what you'd get when you type airdrop in Spotlight, e.g. it won't create duplicates if you already have one or more AirDrop windows or tabs opened, and lauching AirDrop won't bring all Finder windows to the front. I'm actually a bit curious about why Alfred couldn't find airdrop.app after I added /System/Library/CoreServices/Finder.app/Contents/Applications/ to search scope. Until that works in Alfred, this is probably the best solution. Download the workflow at Packal!
  4. Search Alfred Workflows Alfred Workflows help to search in Title, Keyword, Description of a workflow and open it in various actions. Requires Alfred 4! Github: https://github.com/Acidham/search-alfred-workflows Options ENTER - Shows a list of keywords in the workflow and starts the workflow with a keyword CMD - For addtional Actions: Copy path to Clipboard Open WF Folder in Terminal (cd ) Reveal in Finder Open in ForkLift (requires ForkLift installed) Config exclude_disabled: True - ignore disabled workflow in search terminal_path: EMPTY opens in macOS shell or path to custom terminal
  5. Good morning. I've been scratching my head on this one and haven't found much on the forum, which leads me to believe I may be going about this wrong as it feels quite "simple." 🙂 Appreciative for any feedback or guidance. Use Case: I want to be able to open any folder (repo) one level below my "GitHub" folder in both Atom and Terminal. The number of folders (repos) within the "GitHub" folder changes wildly as I add and remove repos. I created a Workflow using a File Filter that limits the search to type "folder" within the "GitHub" folder. I can successfully pass the {query} result (in this case, the folder location) to both Atom and Terminal and get the desired results within each of those Actions. The Question: When using the File Filter, it is also providing me all of the sub-folders within each of the folders (repos) within the "GitHub" folder. The ideal scenario would be just to display those folders directly beneath the GitHub folder, similar to how if I open Alfred and start with "/" I can essentially navigate folders. I found some fairly old (4+ year) posts around using Script Filters to attempt and accomplish, but they were incomplete and/or didn't seem to offer workable solutions. Again, appreciative for any suggestions or guidance. The current iteration of my workflow sames me tremendous time and keystrokes and I can typically remember enough of the repo (folder) name to filter it down quickly, however, the older I get, the less I can reliably count on my memory. 🙂 Thanks in advance for any help!
  6. Striking with a beautiful display font, creating a nice contrast to search results. Bold font is DIN Next LT https://gist.github.com/felixqueisler/e0268924a409275c6daec735aa79616b
×
×
  • Create New...