カレンダー変更を予約可能時間へ同期

Google Calendar の変更に合わせて Calendly を更新し、実際の会議には一切触れません。

Zeroの接続先:

課題

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.

Zeroによる解決方法

ステップ1：ツールを接続する

Calendar

必須

Google Calendar. Supplies native event-change triggers, busy intervals, and ownership context.

接続

Calendly

必須

Calendly. Supplies booking windows and receives safe updates to workflow-owned availability holds.

接続

ステップ2：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.

ステップ3：さらに活用する

Add travel-specific buffers

Protect setup and transit time around recognized travel events.

@Zero add 90-minute buffers around flights and 30-minute buffers around offsite meetings. Own only the placeholders you create.

試してみる

Run a read-only audit

Inspect current drift before enabling writes.

@Zero audit the next 14 days for Calendly gaps that conflict with Calendar. Report only.

試してみる

Protect recurring focus windows

Define explicit protected time instead of relying on event titles.

@Zero preserve my recurring Friday focus block as unavailable even when other events move.

試してみる

より良い結果のためのヒント

●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.