In this use case we will show how to publish a data integration orchestration in Adeptia ESB as a SOAP API and configure it in Salesforce as a webhook to push any new changes or records from Salesforce to a target application such as Support Center. In this use case we will create a new Case in Salesforce and once we save it, Salesforce would push that new Case into Support Center as a new Request through this webhook.
Adeptia takes the new Case record, maps it to Support Center addRequest REST API method and creates a new Request in that application.
Webhooks are used for API to API broker or synchronization services where an Event in the Source Application pushes the new changes as an outbound message to a Target Application. Advantages of using webhooks is that you don't need to rely on inefficient polling mechanism to poll for new changes in the source app. Webhooks allow the source application to push new data records into target application automatically. Adeptia ESB provides a framework where you can orchestrate the behavior of a webhook in terms of which applications you want to distribute the data once Salesforce pushes the new changes into this service.
Here's an orchestration in Adeptia ESB that is published as a webhook (soap service) and configured in Salesforce which we are using as a source app in this example.
Refer to the video on how to design and publish a SOAP API as a webhook in Salesforce. We will also show when we create or modify a Case in Salesforce and save, it automatically pushes the new data into Support Center API.
To checkout how to configure a webhook please use the Adeptia Migration Utility and deploy the attached working example in your local Adeptia instance.
Article is closed for comments.