Archive for the 'Developers' Category

Improved Beanstalk Integration in Torch Project Management

Friday, July 3rd, 2009

In May we released integration with Beanstalk. This allows users of both Torch and Beanstalk to create time entries, check-off events/tasks and categorize the message without leaving the subversion commit process. Now, thanks to the folks at Beanstalk, we've enhanced this feature to allow direct access to changed files. Here is a sample message created through a Beanstalk commit:

Revision Change in Torch

If you click on "View" button next to a particular file it will take you directly to that file in Beanstalk:

View in Beanstalk

How to setup Beanstalk integration >

Torch’s API

Friday, May 22nd, 2009

Torch Project Management now has an API. Using only XML, you can now interact with messages, events, time, categories and projects. Probably the coolest ability (compared to Heap's Simple API), is that you can combine multiple requests into a single XML blob you send to Torch. The documentation page is up here:

I've also included sample PHP code. If you have any questions, please contact support.

Beanstalk Integration with Torch Project Management (for Developers)

Sunday, May 17th, 2009

Using Beanstalk's web hooks, Torch can now receive commit information.

What You Can Do:

The commit messages are posted to the appropriate project. You can also checkoff tasks/events (more than one if you wish) as well as categorize the message. If the project is for a client, you can also include time entries. Here is an example of a commit message:

Versions Commit Window

This results in:

commit message in torch

Setting Up the Integration:

First get the integration URL; this is under the "Integration" sub section of the "Help" tab:


NOTE: Part of the URL is blocked out because it contains the project token, however, you must copy the entire URL.

This URL is unique for each project you decide to integrate, so make sure you are on the right project before you copy the URL.

In Beanstalk, select the appropriate repository then select the "Setup" tab. Select the "Integration" sub section then "Web hooks":


Click on "Activate", then follow the onscreen instructions:



Ben’s Personal Blog

Thursday, January 15th, 2009

Because so many people subscribe to the company blog for updates to Heap and Torch, I've been reluctant to post about side topics. So, I started to start a personal blog.

Right now, I have an example of how to use Heap's Simple API, a discussion of the new iMovie and the Peek. This is pretty representative of what I want to cover: basically anything that is connected in a way to the use of web apps.

The company weblog will continue to be the place for updates.

The JavaScript Add-On API for Heap CRM

Wednesday, June 25th, 2008

The Add-On API is quite simply the most important feature enhancement we have ever released for Heap CRM. With it (and knowledge of JavaScript), any developer can create new features and functions for Heap.

An Add-On can interact with Heap data, store their own data and interact with other websites. In short, they can do everything they need to do directly from JavaScript.

Developers can learn more here. Admin users of all three lines of Heap CRM can install Add-Ons from the Settings->Account screen. Once installed each Add-On will appear as a tab within Heap.

vCards over RSS – a Proposed System

Sunday, March 30th, 2008

"vCards over RSS" is a proposed system to allow automatic updates of contact information.

The Problem:

While contact data can be exported from web applications, in forms such as vCards and CSV, there is no mechanism to receive continual updates. Instead users are forced to either abandon their desktop address books or continually download vCard or CSV files.

Proposed Solution:

Using the existing RSS 2.0 standard, we can use enclosures (typically used for podcasts) to reference a vCard. This provides a number of advantages:

  1. The date and time the contact was updated is included in the feed, thus the downloading program will only download cards that have been updated
  2. Servers will only have to generate a small percentage of the cards as the downloading program will only ask for cards that are actually new or updated (compared to what is already in their internal database)
  3. RSS is already a well known standard that can easily be generated and parsed


<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0">
<title>People - All</title>
<lastBuildDate>Mon, 31 Mar 2008 00:37:07 +0000</lastBuildDate>
<title>John Miles - Apple</title>
<enclosure url=";token=[REMOVED]&amp;loginid=1" type="text/x-vCard" />
<pubDate>Sun, 23 Mar 2008 15:10:45 -0700</pubDate>
<title>Jane Winkle - Cisco</title>
<enclosure url=";token=[REMOVED]&amp;loginid=1" type="text/x-vCard" />
<pubDate>Wed, 26 Mar 2008 08:44:05 -0700</pubDate>
<title>Barbara Tora - USA Today</title>
<enclosure url=";token=[REMOVED]&amp;loginid=1" type="text/x-vCard" />
<pubDate>Sat, 1 Mar 2008 14:00:18 -0700</pubDate>


There is nothing in this idea that the majority of developers don't already know how to do. In fact it isn't really a new standard, just a new use of an existing one. To show our commitment, Heap CRM already supports vCards over RSS. This means any desktop application that understands this system will immediately have potential customers from Heap CRM Hosted, OnSite and Enterprise.