Webhooks are "user-defined HTTP callbacks". They are usually triggered by some event, such as pushing code to a repository, a comment being posted to a blog, or clicking the thumbs-up button on a social media app. When that event occurs, the source site makes an HTTP request to the URL configured for the webhook. Users can configure them to cause events on one site to invoke behavior on another.
In today's highly connected world, no one system can function optimally alone. Achieving a task in your day to day business processes almost always involves more than one system. Take this case:
- A customer needs to buy a book online, so they pay using a credit card, which
- needs to communicate with payment systems, which
- needs to communicate with other systems like the bank, and the bank in turn
- needs to communicate to the customer using an SMS text message stating there was a purchase made with that specific credit card.
This is just one basic example within millions of daily events and actions done using webhooks.
You can use webhooks to empower your business process using integrations between Pipefy and your systems.
Currently, Pipefy offers webhooks that touch different domains: User Management Webhooks and Card/Table Record Management Webhooks. As the name suggests, these webhooks trigger alerts to your endpoints when certain actions occur with users and cards/table-records, respectively