vitor

You’d have to use a Script Filter and parse them yourself. The task sends the paths along to the next object (e.g. connect them to a Send to Trash and do it to all). Listing them is a different thing. What you’re asking is equivalent to a File Filter with the scope set to a specific directory. You can’t have ⌘C, but you can have ⌘↩, or ⌥↩, or any combination of fn⇧⌃⌘⌥ with ↩. Connect a Copy to Clipboard Output and double-click the circle on the connection. In the palette to the right, tutorial 4 on Getting Started explains it.

It does not. Your connections, Keywords, Terminal Command, Open URLs and even the organisation of your Hotkeys will all remain in place. Plus, presumably you’ve added those shortcuts for your use as well. Alfred as always worked this way. Before importing a user can’t know if the Hotkeys the Workflow has will conflict with their own. Accepting random Hotkeys would likely lead to undesirable results.

By design, Alfred strips Hotkey values when the Workflow is imported. This is precisely so when adding a third-party Workflow, you won’t have your shortcuts overridden without a say. In other words, your keyboard shortcuts are unique to you, anyone importing the Workflow will add their own.

Connect a Keyword Input to a Launch Apps and Files Action. Alternatively, type p and scroll down until you see Apple Photos. Act on it (↩). Do that 2 or three times in a row, and it’ll become the top result. Then do the same for ph and Photoshop. Alfred naturally learns from these choices.

It doesn’t do it by design. Showing every file from the start has performance implications. That’s how the File Filter works. * will show everything, and *ext allows you to search for files with a specific extension. You can also use the File Types area in the File Filter to restrict the search to specific file types.

That’s the perfect use case for a File Picker User Configuration. Without changing anything in the Workflow itself, you can delete the Workflow Environment Variable and make this config: Which yields: Allowing to pick the coupon file though a macOS file dialog.

Great! Shouldn’t need the first one, though, as the second one already returns the URL upon closing the tab.

Thank you. A nice weekend to you as well.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Have you seen the annotated screenshot?

Temporarily create a new user account on your Mac, set up Alfred on it, and try again. Can you still reproduce the behaviour?

Welcome @nksunmoon, The Dispatch Key Combo is working normally, but it’s impossible to tell what’s wrong in your setup from a screenshot. How is your Launch Apps set up? How long is the delay (is it enough)? Have you tried doing it semi-manually—just have the Workflow up until the Launch Apps then press the ↩ yourself to ensure it works? Could you record your screen while running the Workflow, with the debugger open?

When asking about an existing Workflow, it’s best to use its own forum thread. While it may seem that starting a new thread could give your problem visibility, it fragments the discussion and makes it less likely the author and users of the workflow (the people who can help) will see it. I have moved the post to the correct thread. But not the correct version of the Workflow. Use @giovanni’s fork.

Git can indeed be hard to grasp at first. My advice would be to not fret about it and learn as you go. There are a few things you’ll need all the time, but most of its capabilities you’ll likely never use. See OneUpdater. If you have questions, I can help you make sure your setup is correct.

Welcome @vanwoods, Check if there’s a conflict with the Hotkey. To find Hotkeys in use by Workflows, go to Alfred Preferences → Workflows and click the (…) at the top (to the right of the Filter bar) followed by Show Hotkeys. For keyboard shortcut conflicts caused by other apps, ShortcutDetective (scroll down until you see the detective badge) may be of help.

As far as I gather, Airplay has to be initiated from the sending device (the iPad), you can’t “pull” from one. If you find a way it can be done, we can try to help you integrate it with Alfred.

See Snippets and Text Expansion Troubleshooting, especially the part on the speed of key events.

Welcome @jesused, Create a new Workflow and connect some input (like a Keyword) to a System Commands Action (Sleep Displays) which connects immediately to another (Lock). That way both will fire in succession, giving you what you want. Alternatively, just activate the regular Lock. When you do so, macOS turns off the display after about five seconds.

I understand the solution you’re pursuing. But like I said you’re making something which is a workaround, GUI automation which is likely to break on Ventura. Wouldn’t you rather a more robust solution which has a better chance of surviving through (at least) the next update? Furthermore, the command-line tool I linked you to seems to do exactly what you want, is maintained, relatively popular, and should allow you to switch sources with literally one line of code. So why pursue the long winded slow solution which is likely to break instead of switching to the quick robust solution which is likely to continue working?

@Saez I don’t understand the post reaction. I can try to guide you further, but I need specifics on what is tripping you up.

@glawrie Looks like you’re on an old version. The line from your error is quoted out in the version for download in the repo (meaning it doesn’t run).

@ninjasmurf Instead of a text field user configuration where uses need to type true or false, use a checkbox user configuration—those are made specifically for such cases. You won’t need to change anything else about the Workflow, the conditional will understand that as well.

If you don’t have a working solution yet, don’t get married to a specific language. In particular, you’re using GUI automation to control System Preferences, meaning the approach is likely to break once you update to macOS Ventura because the app is being revamped. There are Workflows to switch input sources as well as command-line tools which you can use and will likely continue to work with the update. The latter should be easier to work with too, since you’re likely to be able to switch to the specific sources you want with a single line in your Workflow.