In our ongoing effort of making it as easy as possible to sell and support SugarCRM add-ons, we have a simple tool called "Webhooks" that will make it easy to integrate SugarOutfitters into your internal sales and support process. Webhooks will programmatically notify your sales, provisioning or support systems in real-time when things happen on SugarOutfitters with one of your add-ons: someone purchases your add-on, a customer creates a support case, someone leaves a review, etc. The list goes on.

Here’s how it works. When events occur on SugarOutfitters, we’ll send an HTTP request to a script you host at a designated web URL and tell you what happened. You’ll then be able to take action programmatically (via a script) however you like.

webhooks introduction

So how is this useful? Consider a few of these use cases:

1) You sell an add-on on SugarOutfitters that requires configuration on your side before the customer can use the add-on. Instead of waiting for New Sale emails to show up in your inbox (which you may check only ever few hours), simply enable Webhooks and listen for the New Sale event. Whenever the event occurs, you can script whatever it is that you manually had to do, satisfying the customer with a fast response time and great service as well as saving you time and manual work.

2) You sell an add-on on SugarOutfitters but you already have internal processes for handling support cases. Using Webhooks will allow you to push these cases into your internal customer support system faster and more accurately to better serve your customers how you’re already used to serving them. As updates to the case occur, you can update the cases appropriately. All you need to do is enable Webhooks and listen for the Case Created event and New Case Comment event. Whenever the events occurs, you can update your internal support system automatically.

3) Someone cancels a trial. Typically you would have no idea why. With a Webhook, you can have an email automatically sent which typically results in the customer responding with why they quit.

An example email that could be sent:

Hi there, thanks for giving XYZ a try. I see you just cancelled your trial. Do you have any questions about the integration? Was it not what you were hoping for? Thanks!

These are just a few of the many use cases. Nearly every interaction has an available Webhook to help you better service your customers and streamline your processes.

Ready to integrate Webhooks? Here’s what’s next:

Installing and Using Webhooks with Starter Code Complete List of Webhook Events and Data Sources How to Test Webhooks