Previously, sending real-time updates from third-party services to Conductor was back-breaking. And after tons of scrums and brainstorming sessions, we are finally launching the Webhook integration for Conductor.
With the latest version of Conductor, you can now seamlessly integrate Conductor with other third-party services, such as Stripe, Zendesk, Slack, Twitter, and much more, using Webhooks.
Webhook is a callback function based on HTTP that accelerates the connection between the Conductor and other third-party systems. It paves the way to receive data from other applications to Conductor.
You can leverage Webhook to create integration patterns for Conductor workflows. It can be used to create workflows that act on events occurring outside the Conductor. In addition, we’ve added an option to trigger other workflows based on the events received from Webhook. You can enable this while creating the Webhook so that once the Webhook event comes, this workflow gets triggered automatically, thus helping to streamline more processes.
While creating the workflows, you can identify the Webhook task type as ‘WAIT_FOR_WEBHOOK’.
We currently support Webhook integration for GitHub, Slack, Twilio, Stripe, Pagerduty, Zendesk, Twitter, Facebook, and Sendgrid. Apart from that, we’ve included an option called Custom that allows you to integrate Conductor with any third-party systems.
For example, suppose the external system is GitHub, and the requested action is replying with the comment "We’ll get back to you soon!" on every issue creation. In that case, once an issue is created in your GitHub repository, the workflow gets completed successfully.
Wanna know in detail about the configuration steps? Have a look at our documentation on Integrating Conductor with other systems using Webhook.
I can’t wait to see what you build!
Do try out our new add-on, and you can always reach us at our Slack channel for any queries! We’re always happy to help.
Senior Technical Writer