calendly 'event type not found' - the rep deleted the event type the agent books into

TL;DR

Book atomically or not at all: check free/busy, create the event, and store the event id in one guarded sequence. Every booking the agent makes must carry a timezone, a location or link, and a stored id so it can be found, moved, or cancelled later.

The query

calendly 'event type not found'  -  the rep deleted the event type the agent books into

Use this when

• meetings booked at wrong times, double-booked, missing links, or never synced
• calendar access revoked or event types deleted under the agent

Not for

• email scheduling and send-time windows (see the timezone skill)
• sequence enrollment logic (see the state skill)

Steps

Step 1: Check free/busy immediately before creating

Query availability in the same flow as the booking, seconds before the create call, not minutes. Availability snapshots go stale fast when two agents book against one calendar.

**Expected: the create call follows the availability check with no other writes between.

Step 2: Create with timezone, location, and a stored id

Every event gets an explicit IANA timezone, a location or video link, and its provider event id stored on the lead record. An invite without a timezone is a missed meeting; an event without a stored id cannot be cancelled.

**Expected: new events have timezone + location set and the id persisted.

Step 3: Guard the create against double-booking

Use an idempotency key or a conditional create: if an event id already exists for this lead and purpose, update it instead of creating another. Two agents booking one slot need the same guard as two senders.

**Expected: re-running the booking step updates the existing event; no duplicates.

Step 4: Handle the human side of the failure

For no-shows, trigger the no-show follow-up branch instead of letting the sequence run as if the meeting happened. For wrong-time bookings, send one correction with the right time in the lead's zone.

**Expected: no-show and wrong-time branches exist and fire; sequences do not assume attendance.

Step 5: Reconcile on a schedule

Poll the calendar provider for events in the booking window and compare against your records. Revoked access, deleted event types, and expired webhooks all surface here first.

**Expected: a daily reconciliation catches orphaned or missing events before the rep does.

Why it happens

Booking bugs are distributed-systems bugs: two writers, stale reads, and ids that were never stored. The agent treats the calendar like a local function call, but it is a shared remote system with races.

Edge cases

• 'Tomorrow at 2' without a timezone is ambiguous; always resolve to an absolute timestamp.
• Revoked calendar access looks like an auth error, not a booking error; check grants first.
• Deleted event types break the booking path silently; monitor the event-type list.

Finding this skill

This skill was written for sales-outreach (SDR) agents hitting the failure above. Search Vectle for the exact error text or symptom to find it and related skills.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstR9NWIwq3n-3OT4IRyN7Vw