3 Things You Might Not Know about Declarative Webhooks

The Growing Salesforce Ecosystem

Of the 76,000+ Salesforce certified professionals, Administrators are growing at a rapid pace: 37% a year! For reference, that’s the 4th highest occupation rate growth in the United States. The fourth highest! At the same time, Salesforce implementations requiring at least one integration with an external application are on the rise.  Oftentimes these integrations require custom code just to send data out of Salesforce.  So why are there so few tools in the Salesforce AppExchange, solving for this frequent business issue, that are built specifically for Admins? That’s exactly the question the team behind Declarative Webhooks asked. And furthermore, why spend thousands of dollars on custom development or learning a new off-platform app when you could implement a 100% native, fully declarative, but extremely robust tool that any Admin can use?  

A Brief History of Omnivo Digital

After 6 years of running Omnivo Digital, a Certified Salesforce Partner, and a combined 30+ years experience with the platform, Adam Zuckerman, Jason Sun, and Lucian Ciobanu recognized multiple opportunities in the marketplace. The first one they wanted to tackle? Integrations.  After having implemented custom integrations for hundreds of Salesforce projects and having to write custom APEX code to support many, including relatively simple integrations, they thought, “Why do Admins have to search for external solutions or hire developers to resort to custom code when they want to connect Salesforce to third party apps?”,  “Why is there an Outbound Message feature in Salesforce that only supports SOAP and not REST, the more popular framework for integrations and exchanging data these days?”, and finally “Why are we having to write custom code for so many of our integrations?”

So, they took their extensive experience with Salesforce development and cross-platform integration and developed Declarative Webhooks to solve this problem.  

Here are 3 things you might not know about Declarative Webhooks. 

  • It has a fully declarative interface. True to its name, the Declarative Webhooks tool is one that any Admin can use to build integrations between Salesforce and external systems. The point-and-click experience is key to accessibility, low cost, and time-to-implement, all the things we value in the growing Salesforce ecosystem.
  • You can build JSON from parent-child relationships and apply filters using SOQL. Declarative Webhooks enables Admins to easily create Callout Templates and data structures using an intuitive JSON Builder. Admins can apply filters with an easy-to-use interface or with custom SOQL, if desired.  They can also map data from both related parent objects and child related lists (with filters on child records too!) in the JSON data structure. Additionally, users can use a response builder to trigger multiple response actions. Did I mention you can integrate with platforms no matter what kind of authorization  method their API requires?
  • You can implement a callout in a button, flow, process builder, or scheduled batch. No matter what requirements your business or users have, Declarative Webhooks can flex to meet them. Whether you want to automatically trigger a webhook with a flow or process builder, run them on a schedule, or give your users a button to make the callout themselves, the choice is at your fingertips. 

The Hook about Declarative Webhooks

So next time you have a use case where you need to integrate your Salesforce with an external application, before hitting the custom development panic button, give Declarative Webhooks a try!  With the free tier, you can create a callout template and up to 100 callouts per month to take the tool for a test drive. 

One thought on “3 Things You Might Not Know about Declarative Webhooks

Leave a Reply

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