Highrise API and tagging

Colin A. Bartlett — Mon, 18 Feb 2008 13:28:00 -0500

Like many, I was disappointed that the Highrise API does not support tagging of people. However, I found a way to easily add the capability to the 37signals-supplied Ruby wrapper class, even if it is unsupported. I added a #tag! instance method to the Person class and used a call directly to the site, not through the API.

class Person < Subject
  ...
  def tag!(tag_name)
    `curl -s -d 'name=#{tag_name}' #{ENV['HIGHRISE_URL']}parties/#{id}/tags`
  end
end

The output is a bunch of javascript to update the page to reflect the change, but one can safely ignore this. The tag is added and everything works great. Not sure how well this would work on Windows, as the curl command-line program is likely unavailable.

We use this method in our latest project to add appropriate tags to people as they are created. It helps us segment people added to Highrise for the project from the rest of our contacts in Highrise.

Voicemail integration with Highrise

Colin A. Bartlett — Fri, 01 Feb 2008 07:23:00 -0500

I’ve often had trouble keeping track of my voicemail messages. Even though they get emailed to me, the emails don’t have any info about who the messages are from and I have no way of keeping track of if I’ve responded or if there’s an action item.

So I wrote a simple little Rails app to help me integrate my voicemail message into Highrise, the 37signals product which I’ve been trying, and liking, in recent weeks. Their provided REST web service API and accompanying Ruby wrapper made the whole thing way too easy. I have two models:

Person
Voicemail

The Person model holds a cached list of the names and Highrise ID’s of the people in my Highrise account. I can update this through a simple link in the app anytime I need.

The voicemails get into the app by a simple little “pipe to program” I added on the mail server. Something like this:

curl -u username:password --data-binary @- http://address.of.app/import

When an email message is received at the voicemail alias, the entire email is POSTed to the address above where it’s consumed with a tiny controller action like like:

Voicemail.import(request.raw_post)

The ‘import’ class method simply uses TMail to parse the message, pull off the attached WAV file, save it to the file system, and create a new Voicemail record.

The rest of the interface is simple CRUD stuff: A list of new voicemails that have come in with a link to delete and a link to save for each one. When I ‘save’ it, I choose a Person from a drop down of all my Highrise contacts and enter a very short 1 line description of what they called about. A note is instantly posted to the Person’s Highrise history with the time of the voicemail, the 1-line description, and a link to listen to the voicemail. If 37signals provided file upload capability through the API, I might just upload the file to Highrise. Or I might not since the WAV’s would eat up my storage space.

I hope to expand this a bit in the near future with a nice interface—perhaps autocomplete instead of a drop down for choosing the Person. And I think I’ll add a way to optionally create a Task in Highrise related to the Note. It would be nice if Highrise color-coded the categories applied to tasks; that way, I could categorize all the voicemail follow-up tasks and color code them so they stood out in my task list. I’ll have to submit that as a feature request.

Update

Here’s a screenshot, per Jason’s request. Click for a full sized version. As you can see, the interface is very modest.

Since the original posting, I changed a couple things:

I’ve linked the person’s name to their Highrise page
The little note icon on the left takes you to the note in Highrise that was created for this voicemail

has_many :thoughts: Tag 37signals

Highrise API and tagging

Voicemail integration with Highrise

Update