Jump to content

Possible to refer to clipboard history item in a workflow?

Recommended Posts

I could not find answer to this question, apologies if it is obvious:


Is it possible in a workflow to refer to individual clipboard history item somehow? Like {clipboard-1}, or something?


I'd need to compose a workflow where I would combine several items in the history together. This would save me a lot of time. 

Link to comment

No. It supplements it. Alfred currently doesn't have any way to get to the clipboard history from any type of script, environment variable, etc. Therefore, if you need that kind of information you will have to have a supplementary piece of software to fill in the gap. I use Keyboard Maestro for that functionality, but CopyQ is free.


I have asked for it in the "Alfred Feature Suggestions" forum. 

Link to comment

I'm sorry. I thought I was using clipboard history, but I have <ctrl-c> tied to seven macros that copy into named clipboards and <ctrl-v> to seven macros that paste from the same named clipboards. Then I use these named clipboards in other scripts to build up text expansions using the named clipboards. So, it simulates a clipboard history, but doesn't really do it.


The only action for clipboard history is the "Set Clipboard to Past Clipboard x" where x is 1,2,3,.... Then paste from the clipboard. Therefore, you can make a macro that:


Insert text "this is clipboard 1: " by typing

Set Clipboard to Past Clipboard 1


Insert text "This is clipboard 2: " by typing

Set Clipboard to Past Clipboard 2



You would have to use the "Insert Text by typing" to not mess up the clipboard order. But remember, the "Set Clipboard to Past Clipboard 2" made the current clipboard to the second paste clipboard and removed that one from history, but what was the current clipboard is now the Past Clipboard 1. This does get confusing some.

Link to comment

Thank you for a thorough explanation! Although, I have to admit that it does get a bit too confusing.


So, I guess I'll will wait for Alfred developers to (maybe) include the proposed feature to the product - and continue manually copying and pasting 'til that :)

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...