The Power of the Webhook

Back in the Pardot days, we wanted a way to accept data from a third-party form or application directly into the app, so we came up with the form handler. Basically, it’s the receiving end of a form submission without the front end form fields to go with it. Over time, this practice of sending and receiving data via a specific URLs became popular and is widely know as a webhook.

Wikipedia has a more technical definition:

Webhooks are “user-defined HTTP callbacks”. They are usually triggered by some event, such as pushing code to a repository or a comment being posted to a blog. When that event occurs, the source site makes an HTTP request to the URI configured for the webhook. Users can configure them to cause events on one site to invoke behaviour on another.

Now, webhooks make it easy to share data and trigger features across thousands of SaaS apps, and they don’t have to have formal integrations. The more apps that implement webhooks — both to send and receive data — the more the incumbent apps that aren’t SaaS 2.0 lose their ecosystem integration moat.

Look for webhooks to continue to grow in importance over time.

What else? What are some more thoughts on the power of webhooks?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.