Connect a calendar system
Stores a pasted calendar key, such as a Cal.com one, once that product accepts it.
The key is checked first, with one read there. Refused: 400 CalendarKeyRefused. Product unreachable: 503 CalendarKeyCheckUnavailable, worth retrying. Either way nothing is saved and an existing connection stays.
A webhook is registered where the product supports it, so its cancellations reach Team Follow Up. If that fails the key is still saved and cancellations reads failed, with its reason in cancellationsError; pending is still trying, watched is registered.
A reconnect replaces the key. The old key’s webhook is removed first, or with the new key if that fails; one neither can remove stays in that account and what it sends is refused.
A system in beta can be connected only by Team Follow Up AI staff.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: projects:write.
Authorizations
Query Parameters
Body
The credential.
