How we used the PipelineDeals.com API to integrate sales information

As a new (and already satisfied) user of PipelineDeals.com, I ventured into using its API soon enough. QuickSchools.com, the SaaS school management system that we’re selling, generates sales leads from quite a few channels, and I want all our sales lead contacts to be tracked on PipelineDeals.com. ┬áHere are some of those different channels:

  • They can fill out a “contact us” form.
  • They can sign up for a demo account.
  • They can start a 30-day free trial.
  • They can chat with us via live chat feature.
  • They can call us.
  • They can email us.

Having a holistic view of those leads would certainly help us sell better. I don’t want to lose a sale simply because we didn’t have our processes in order. I also want to see how we perform across those various channels so that we can know what we’re doing right and what we’re doing wrong.

For some of these leads, I want the data to be automatically inserted into our PipelineDeals.com system. PipelineDeals.com offers 2 integration options:

  • You can import leads using a Web-2-leads feature. Simply create a web form, and when it is submitted to PipelineDeals.com, it will create a lead. However, I wanted to send the data from our Java application, so this didn’t work.
  • You can import leads (and much more) using a REST API. Now, if you’ve used a REST API before, you’ll know it’s pretty simple. And this was no exception. Within a couple of hours, I had the data from our Java system sending leads information to our PipelineDeals.com database. In fact, it took so long because I spent some time creating an effective framework within our application for calling such REST APIs.

But unfortunately, the PipelineDeals.com API is not comprehensive. It misses certain key abilities. For example, I can’t seem to change the tags for the leads. And it’s hard to make my voice heard that I want such things, because most of the votes on the PipelineDeals.com UserVoice forum is for user features, not for API enhancements. Oh well. In any case, it’s just about workable for my purposes.