De cambios de calendario a bloques de disponibilidad
Zero mantiene Calendly alineado con Google Calendar sin mover ni eliminar reuniones reales.
Zero conecta:

Cuál es el problema
A meeting moves, a customer cancels, or a travel block changes, but the booking tool keeps yesterday's availability. Zero responds to the calendar event, recomputes only the affected window, and updates the placeholders it owns. The guardrail is explicit: it never edits a real meeting or guesses that a private block is disposable.
Cómo lo resuelve Zero
Paso 1: Conecta tus herramientas
Paso 2: Pregúntale a Zero
@Zero when a Google Calendar event is created, updated, or cancelled, recompute the affected Calendly availability window. Update only placeholder holds created by this workflow. Never move or delete a real meeting, booking, or unowned private event.
A calendar change triggers a focused check
Zero inspects the changed event and only the adjacent availability window instead of rebuilding the entire calendar.
Zero computes the true gaps and ownership
Busy intervals, buffers, booking windows, and ownership markers determine what may safely change.
Zero reconciles its own placeholders
Every update is logged; unowned blocks, private events, and real meetings remain untouched.
Paso 3: Llévalo más lejos
Consejos para mejores resultados
Start in audit-only mode before allowing placeholder updates.
Use an explicit ownership marker on every block the workflow creates.
Default ambiguous events to preserved, not movable.