Calendly API 404 "event type not found" when the agent creates interview slots against a deleted event type
Fixes Calendly 404s when a scheduling agent references a deleted event type. Use it when event-type lookups fail after calendar cleanups. Key trigger: the cached event-type UUID is absent from the live list.
TL;DR: List the live event types through the API, confirm the agent's cached UUID is gone, and point the agent at the replacement event type. Event types get deleted or archived by their owners; the agent's cached ID does not update itself.
Calendly API 404 "event type not found"- Call the Calendly event-types endpoint for the relevant user or organization to list current event types. Expected: a 200 response with the live list of event types and UUIDs.
- Compare the agent's stored UUID against that list. Expected: the stored UUID is absent, confirming deletion or archival.
- Update the agent's configuration to the replacement event type's UUID. Expected: the config references a UUID from the fresh list.
- Re-run the slot creation. Expected: the API returns the scheduled event instead of a 404.
Use this when
- Calendly returns 404 on event-type operations that used to work.
- Someone recently cleaned up or reorganized event types.
- The agent caches event-type IDs long-term.
Not for this skill when
- The 404 is on a scheduled event or invitee (different resource).
- The error is 401 (authentication).
- The invitee-facing booking link shows "not found" (check the public link instead).
Variant phrasings
- "Calendly event type deleted"
- "404 event_types Calendly"
- "Calendly interview slot event type missing"
- "event type UUID invalid Calendly"
Why it happens
Calendly event types are routinely deleted or archived during calendar cleanups, and scheduling agents store the UUID once at setup time. Nothing notifies the agent, so it keeps calling a resource that no longer exists.
Edge cases
- Archived event types may 404 the same as deleted ones; check both states.
- Personal and team event types have different owners; the API caller may not see another member's types.
- If the owner left the company, their event types may be orphaned; reassign ownership first.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_z2R8HBl1xZOuBITMWphOnw