Developer meetup: Building Smarter Workflows with Orkes Conductor + Stripe (virtual)

Hey everyone, our next virtual Developer Meetup hosted by @jeff.bull , Orkes’ Developer Community Manager is coming up next week :fire:

Date: Tuesday, 4-15-25 @ 11am PST
Guests: Viren Baraiya (Co-founder & CTO, Orkes), and Cecil Phillip (Staff Developer Advocate, Stripe)
Topic: Building Smarter Workflows with Orkes Conductor + Stripe

REGISTER HERE :right_arrow: Building Smarter Workflows with Orkes Conductor + Stripe

Modern app development isn’t just about writing code—it’s about connecting services, handling failures, and delivering reliable user experiences at scale. This session dives into how combining Stripe’s robust payment APIs with Orkes Conductor’s powerful workflow orchestration can simplify complex integrations, reduce operational overhead, and boost resilience.

Key Takeaways

Streamline third-party integrations like Stripe using Conductor’s API orchestration to reduce coupling and simplify service-to-service communication.

Apply best practices for Stripe’s API design, including webhook handling, retries, and multi-step flows without embedding logic deep in your code.

Leverage built-in resilience patterns in Orkes Conductor to gracefully handle timeouts, service degradation, or failures—without rewriting your app.

Deliver higher reliability and scalability by moving error handling, retries, and throttling to the orchestration layer—reducing app complexity and boosting velocity.

The Watch Here link on the REGISTER HERE page points to some other webinar about Conductor OSS vs. Orkes Conductor, nothing at all to do with Stripe as far as I can tell. I looked for the video on the Orkes YouTube channel but could not find it there either.

Can you please fix that link to point to the right video, or better yet, just post the link to that video here? I use Stripe and am really interested to learn what you described here.

1 Like

Hey @paulzim sorry about that :pensive_face: I’ll get that fixed shortly.

@paulzim Found the issue. We had named the recording uploaded to YouTube something different than the original webinar title. Just fixed that, and I verified the watch now button does link to the correct video.