andrewning

Thank you; I will try that! Just spent a good chunk of time doing this manually. 
 
Edit: And it works! I must have missed an update. This is literally the best day ever. 

Two options:
1) the file action doesn't actually execute the crossref command, so you can always hit the HOME button and add a 'gs' before hitting enter.  It purposely doesn't try to automatically execute the command so that you can change the search type, and because the file action uses some heuristics and may not necessarily grab all the right keywords that you want.
2) Open up pdf2doi.py in the workflow and in line 54 replace 'ref' with 'gsref'.  Of course this will get overwritten with app updates.  If this becomes an issue I could add an option where the default search for the file action would be loaded from a config file or something.

Reference Importer: search for an article/book from a variety of sources and import the corresponding reference data (BibTex, PDF) into BibDesk, copy BibTeX to clipboard, go to the landing page for the article, or copy a formatted reference. Also supports reference lookup from a PDF file. (This workflow was formerly known as "Citation Search" and "AIAA Search")
 
(follow link to GitHub for a more detailed README and download)
 
Update 5/22/2013: added conversion of non-latin characters to proper LaTeX.  also removed default cite-key so that BibDesk can populate citekey with user defined style.
Update 5/28/2013: fix due to slight change of crossref.org API
Update 12/4/2013: major update including improved parsing, getting PDFs in addition to BibTeX, Google Books, Google Scholar, reverse PDF lookup.  more details in comments below and in README
Update 12/6/2013: improvement to DOI parsing from PDF text
Update 3/15/2014: minor fixes and improvements
Update 4/2/2014: unicode fix
Update 4/3/2014: another unicode fix, this one for google books

small improvement for pulling out the DOI of a PDF automatically

Interesting.  I didn't even know about that hidden "Trigger behavior" for the modifier keys in Alfred.  I just use the default "Simulate modifier keys released", but I tried all three options and all three triggers (right arrow, function, or control) worked fine for me for any of the trigger behaviors.  In any case, I'll leave the default as is, but your comment will be helpful for those who run into the same issue.  Also thanks again for the suggestion of adding the file action option.  I've actually started using that quite a bit lately to quickly email someone the file I'm currently working on.

Go To Current File Assign a keyboard shortcut to quickly go to the file (in Terminal, Finder, iTerm, or Alfred's File Action Window) for the file in the frontmost app.  For example, while working on a presentation in Keynote a quick keyboard shortcut can take you to the corresponding directory in Finder or Terminal.  Tested to work on most popular applications. 
 
(link goes to GitHub for README and downloads)

Reference Importer: search for an article/book from a variety of sources and import the corresponding reference data (BibTex, PDF) into BibDesk, copy BibTeX to clipboard, go to the landing page for the article, or copy a formatted reference. Also supports reference lookup from a PDF file. (This workflow was formerly known as "Citation Search" and "AIAA Search")
 
(follow link to GitHub for a more detailed README and download)
 
Update 5/22/2013: added conversion of non-latin characters to proper LaTeX.  also removed default cite-key so that BibDesk can populate citekey with user defined style.
Update 5/28/2013: fix due to slight change of crossref.org API
Update 12/4/2013: major update including improved parsing, getting PDFs in addition to BibTeX, Google Books, Google Scholar, reverse PDF lookup.  more details in comments below and in README
Update 12/6/2013: improvement to DOI parsing from PDF text
Update 3/15/2014: minor fixes and improvements
Update 4/2/2014: unicode fix
Update 4/3/2014: another unicode fix, this one for google books

Reference Importer: search for an article/book from a variety of sources and import the corresponding reference data (BibTex, PDF) into BibDesk, copy BibTeX to clipboard, go to the landing page for the article, or copy a formatted reference. Also supports reference lookup from a PDF file. (This workflow was formerly known as "Citation Search" and "AIAA Search")
 
(follow link to GitHub for a more detailed README and download)
 
Update 5/22/2013: added conversion of non-latin characters to proper LaTeX.  also removed default cite-key so that BibDesk can populate citekey with user defined style.
Update 5/28/2013: fix due to slight change of crossref.org API
Update 12/4/2013: major update including improved parsing, getting PDFs in addition to BibTeX, Google Books, Google Scholar, reverse PDF lookup.  more details in comments below and in README
Update 12/6/2013: improvement to DOI parsing from PDF text
Update 3/15/2014: minor fixes and improvements
Update 4/2/2014: unicode fix
Update 4/3/2014: another unicode fix, this one for google books

I've made more than one workflow where I wanted the ability to copy some text to the clipboard *or* open a URL in the browser (using an action modifier to trigger the URL case).  In both cases, I start with a script filter, but what I want to copy to the clipboard is not the actual URL, but some different data.  My script filter would like to send two pieces of information, and this is no problem to do just by concatenating them and adding a custom delimiter.  The problem is that "Open URL" can only be an action and not an output.  So because only one {query} is allowed, and "Open URL" has no parsing abilities (other than adding some static portions of the URL), I must past only the URL data through the query.  This means that I cannot pass the rest of the data to the clipboard copy portion of the workflow.  If only passing the URL, I'd basically need to duplicate the same code in the script filter.  Of course it's not hard to write your own script to open a URL in the default browser (which is what I've done), but if "Open URL" could be an output (and not just an action) then it would actual be useful for these use cases.
 
Example below is essentially what I'd prefer to do, instead I replace "Open URL" with a "Run Script" than handles the parsing and open URL functionality.  I'd still need the "Run Script" anyway to parse the two-part query, but it could reuse the exact same script from the top "Run Script".  Then I'd connect to "Open URL" on the far right if it was an output option.