Table of Contents

Share on:

Share on LinkedInShare on FacebookShare on Twitter
Playground Orkes

Ready to build reliable applications 10x faster?

ANNOUNCEMENTS

Introducing Webhook Integration for Conductor

Riza Farheen
Developer Advocate
November 17, 2022
3 min read

Previously, sending real-time updates from third-party services to Conductor was time-consuming. After many 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, Slack, Microsoft Teams, and much more, using Webhooks.

Now, what is a Webhook?

Webhook is a callback function based on HTTP that accelerates the connection between Conductor and other third-party systems. It allows the Conductor to receive data from other applications.

And what does this integration do?

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 support Webhook integration for GitHub, Slack, Stripe, and Microsoft Teams. We’ve also included an option called Custom that allows you to integrate Conductor with any third-party systems.

Here’s how you can configure this in Conductor!

  1. Create the workflow to receive the Webhook event.
  1. Create Webhook and verify the Webhook URL.
  1. Run the Workflow.
  1. Complete the requested action from the external system, and the workflow gets completed successfully.

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.

You can also configure Webhook such that the workflow is automatically triggered when events are received via Webhook.

Wanna know in detail about the configuration steps? Have a look at our documentation on 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.

Cheers!

Riza Farheen
Senior Technical Writer
Orkes Inc

Related Blogs

Introducing Candid Conversations: Exploring the Future of Workflow Orchestration and AI

Oct 25, 2024

Introducing Candid Conversations: Exploring the Future of Workflow Orchestration and AI