Bottom Line: This AppleScript Action for Quicksilver sends iMessages through on your Mac without having to bring it into the foreground.

Version 2 of the script here.

I love using to text from OSX — much faster than trying to type on my mobile devices, and it syncs up all my conversations. It even prevents my phone from notifying me of new texts if I’ve already seen them on my Mac — a lot of thought has gone into it. That said, it’s not always 100% reliable. For example, I have to check it fairly often for the little red explanation mark next to an outgoing text that signifies it not being sent properly. That’s a bummer, but you can just click the icon and resend… as long as you’ve noticed it wasn’t sent.

The other day I was clicking around in AppleScript Editor and noticed that has its own AppleScript dictionary — pretty cool! I was able to use this with Quicksilver’s excellent AppleScript support to write a quick-and-dirty Quicksilver action to send texts through Messages. At this point, I’d say it’s functional but not great.

To “install” it:

  1. Save the action to ~/Library/Application Support/Quicksilver/Actions.
  2. Open the script in AppleScript Editor and replace the AppleID property at the top with your own. Compile and save.
  3. Relaunch Quicksilver cmd ctrl q to have it reindex the actions folder.

Note that the script will be an eligible (second pane) action only if it detects a string in the first pane.

Update Apr 26, 2013 thanks to @p_j_r: The script has been updated to now accept the text content in the first and the recipient in the third pane. This is much better, as it allows other scripts to return text content (e.g. a URL, text grabbed from an application) to the first pane. Previously you would have had to copy that to the clipboard and replace it with the contact, then paste into the third pane. This may add some confusion, however, as contacts will now be selectable in both the first and third panes, and it will not work if you select them in the first pane. If you have ideas on how I could add some kind of switch to allow either way, that would be great, but since both the message content and iMessage phone number or email address are both strings, I’m not sure how AppleScript could reliably distinguish which was which.

So to use it, I select a contact in Quicksilver’s first third pane, then use the right arrow button to enter the contact’s info and select their iMessage email address or phone number. Note that the contact themselves will not work, you have to either select (or type in) an iMessage email address or phone number. For me, this works pretty well because I’ve been diligent about changing my friends’ phone type to “iPhone” if they have one, so I can just enter a contact’s name, right arrow, type in “iph” and it selects the right one.

Update Jun 19, 2013: I’ve made a second version of this script that allows you to make a “phonebook” that avoids the need to “arrow in” to contacts. Read more here.

Update 20220710: Minor updates for the modern AppleScript terminology, still seems to work.

In the second pane, select “Send with Messages” as the action, then in the third first pane hit period “.” to enter text mode and type in your message. Hit enter and it should send! If is not running it will launch, if it is running, the message will send in the background without interrupting what you’re doing.

^^ Going to leave this mostly as is (except the two strikeouts) because the info is still mostly correct. Just reread the paragraphs in reverse order if you’re confused. First pane: text. Second pane: YourActionName.scpt. Third pane: Contact name -> iMessage number / address.

There are a few pending issues that I wish worked better, but may or may not be fixable without writing an actual Quicksilver plugin. Considering I don’t know any C, that might be an issue.

  • I would really like to put the message in the first pane and the recipient in the third to make it much quicker to return something like a URL to Quicksilver and message it to a friend. However, I can’t seem to get contacts as a valid indirect (3rd pane) object type, so this would break my “arrow into a contact” trick, and you’d have to manually type the phone number / email into the third pane.
  • I’d like to be able to index iMessage-able numbers — even if I had to do it manually — that indexed a number to a name, so I could just type in the name and not have to arrow into the contact and select the number.
  • Because it sends without bringing into the foreground (which is kind of the point), I won’t see any message failure notifications unless I check manually. Scroll down below the script to see a workaround I’m curious about here.
  • I wish I didn’t have to hit the “period” to enter text mode in the 3rd pane. Some plugins have QS automatically enter text mode when text input is required, but I don’t know if this feature is available to AppleScript actions.

Here’s the script:

Okay, the workaround I mentioned above. If you open up the AppleScript dictionary, you’ll notice it has a section of Events Handlers. Sure enough, you can open, go to “Alerts,” and there are a whole series of events that you can have trigger scripts. If you check the “Run an AppleScript script:” alert, you can have it open the scripts folder at ~/Library/Scripts/Messages/. You can write and store scripts such as this there to have them run when certain events occur (logging in, sending a message, etc.):

I was thinking one could potentially use this to help ensure that messages are sent without errors. For example, at the end of the “Send with Messages” script above, add a command to run a second script that delays 30 seconds, then pops up a dialog box notifying you that there was an error. Then, in the events handler script, have it try to cancel the first script. Theoretically, I would hope this would make it so that the dialog only popped up if the message was not successfully. Unfortunately, this would only work for messages send with the script above, and it wouldn’t work if the handler script runs on failed messages as well as successful ones… Just a thought.

Anyway, if anyone has ideas on improving these, feel free — all posted as GitHub Gists, so have at it!