How to Restrict Event Type 2 Availability Until Event Type 1 is Booked?

[babyinc78]

I'm setting up two event types in Cal.com, where:
Event Type 1: I book the scheduler.
I added a Redirect to a custom URL to Event Type 2 after a successful booking of Event Type 1.
Event Type 2: The scheduler books me.

The Redirect to Event Type 2 is working fine.
I need Event Type 2 to only be bookable AFTER Event Type 1 is scheduled.
Essentially, the second event should only be available at a later time than the first event.

What’s the best way to configure this in Cal.com

[dosubot[bot]]

Hey @babyinc78! How can I assist you today?

To achieve the desired setup where Event Type 2 is only bookable after Event Type 1 is scheduled, you can use webhooks to manage the availability dynamically. Here's a general approach:

1. Set Up Webhooks: Configure a webhook in Cal.com to trigger when Event Type 1 is booked. This can be done by setting up a webhook for the "BOOKING_CREATED" event for Event Type 1.

2. Custom Script: Use the webhook to trigger a custom script or service that updates the availability of Event Type 2. This script can use Cal.com's API to modify the availability settings of Event Type 2, making it bookable only after Event Type 1 is scheduled.

3. API Usage: Utilize the Cal.com API to update the availability of Event Type 2. You can use the PATCH method on the /api/v2/event-types/{eventTypeId} endpoint to adjust the availability settings based on the booking of Event Type 1 ^[1].

This approach allows you to programmatically control the availability of Event Type 2 based on the booking status of Event Type 1, ensuring that Event Type 2 is only available after Event Type 1 has been booked.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}