In this article, you'll learn about the Webhooks app and how to add it to your Flows.
What is Webhooks App?
Webhooks app is a System App that makes your Flows adaptable. When added to a Flow, the Webhooks app brings a Trigger from the applications that don't support native triggers. The difference between a simple Trigger and the Incoming Webhook Trigger is that a simple Trigger is associated with one event in an application only. However, in case of the Webhooks app, the incoming webhook trigger provides a URL that can be pasted in any third-party app. When an event occurs in any of the third-party apps, it can send data to the webhook URL. Similarly, an Incoming Webhook trigger can bring data for different events occurring in the same app.
Let's assume that we have to design a Flow using which we can bring Triggers from different applications. For example, "Create a contact in App X when a subscriber is added in App A, a contact information is added in App B, and a new customer sends a message in App C." In this case, the Trigger is not associated with one application. We can provide a URL to all three applications, i.e., App A, App B, and App C. Whenever the specified event occurs in the mentioned apps, they'll send a trigger on the incoming webhook URL. As a result, a contact will be created in App X.
Similarly, an Incoming Webhooks URL can receive a trigger for different events occurring in the same application. For example, "Update the list of contacts in App A when a new contact is created in App B, a contact is updated in App B, and a contact is deleted in App B."
If any of the mentioned events occur in App B, a trigger would be sent by App B and as a result the list of contacts would get updated in App A.
Adding a Webhook App to a Flow
Let's see how you can add the Webhooks App to your Flow.
Step 1: Go to Flows and click on 'Create a Flow.'
Step 2: Search and select Webhooks from the App Connector selection screen in the Flow Builder.
Step 3: Next, select the Incoming Webhook Trigger for this App.
Step 4: You can either click Continue to move on to the next steps or add a condition to your step by clicking +Add Condition. If you add a condition, the step will execute when the condition is true.
When you add a condition, you will see the above screen. The If condition has two operands with one operator in the middle.
You can provide any values for the operands or add tags by clicking on the '+' sign. The operators are the same as the simple independent If conditions you can add in your Flows.
Step 5: You can test the Webhook to see if it's working properly by clicking on the Test button.
Step 6: The Flow will be automatically saved when you start the test. Here, you will be provided with Integry's webhook URL that you can copy and paste in your application. You then have to carry out the relevant operation on your app that will notify Integry about the Trigger.
After a successful test, you will see the above screen. You can click on the Trigger section to expand the test result.
The result contains the payload that Integry receives at the webhook URL when the Trigger event occurs in the third-party application. In addition, a timestamp for when the Webhooks Trigger is received will also be displayed in the test result, shown above.
Incoming Webhooks Trigger Support in SDK
Let's add the Webhook Flow to an SDK Deployment and see how it impacts integration creation.
After saving and publishing a Flow, add it to an SDK Deployment, shown above.
Click on 'Save Embed' to save your changes and click on 'Preview' to see the sample of how your SDK will look like, when embedded inside an app.
Click on your Flow to create the integration.
Connect your account where you want to perform the action. In this example, our Flow is, "Create a subscriber in Mailchimp if a contact is created in app A."
In the above example, App A will send the trigger to Integry's webhook URL to initiate the integration.
Configure your application and click 'Save' to save and enable your integration. Ideally, the end-user will see a callback URL at this point that they have to paste in the trigger application. However, in case of SDK Flow configuration, the callback URL will be passed programmatically to the trigger application.