Description The built-in CheckAvailabilityCal node is calling an invalid Cal.com v2 endpoint, which results in consistent 404 errors even when all required parameters are correctly provided. This is not caused by date extraction, timezone, or flow logic. The issue is reproducible with valid inputs and appears to be an outdated or incorrect Cal API integration in Retell. Steps to Reproduce Use the CheckAvailabilityCal node with a valid eventTypeId Provide a valid date in YYYY-MM-DD format Ensure timezone is set (e.g. Europe/Copenhagen) Run the flow Actual Result The node sends the following request: GET /v2/event-types/{eventTypeId}/availability?date=YYYY-MM-DD&timezone=Europe/Copenhagen This request returns: 404 Not Found Expected Result Availability should be fetched successfully from Cal.com using the correct v2 endpoint: GET /v2/slots with required query parameters: eventTypeId start end timeZone and required headers: Authorization: Bearer cal-api-version: 2024-09-04 Evidence Flow logs confirm: booking_date is correctly populated (e.g. 2024-06-14) The 404 persists despite valid input Error response explicitly states: Cannot GET /v2/event-types/{eventTypeId}/availability Impact The CheckAvailabilityCal node is currently unusable with Cal.com v2 and prevents any availability-based booking flows from functioning. Conclusion This is an integration bug on Retell’s side. The node appears to rely on a deprecated or non-existent Cal.com endpoint and should be updated to use the correct v2 /slots API. @User

if its returning a 404 it means your event type isnt valid