Sync monitoring

When to use: OutboundSync-emitted Sync Monitoring Webhooks — sync.failed / sync.recovered, deliveries, replay, register an endpoint, rotate a signing secret. Not for SEP → OutboundSync Sources paste URLs (use Preflight). Product how-to: OutboundSync webhooks.

What it does

sync-monitoring calls /api/v1/webhooks and /api/v1/events to diagnose Sync Monitoring health. Default is read-only. Creating, updating, deleting, rotating secrets, testing, or replaying requires an explicit confirmation of a one-line plan (method, path, effect). Vague asks like “set up webhooks” are not confirmation.

Requires an account-scoped API key for /webhooks* routes. Mutations also need the write scope. Prefer API for vocabulary/bootstrap and Preflight for launch Sources wiring.

Try saying this

Ops wants alerts when sync breaks

You

❯ Are my OutboundSync Sync Monitoring webhooks delivering sync.failed events?

Agent ◆ Skill · sync-monitoring

I’ll diagnose /webhooks and /events read-only first. If we need to register or replay, I’ll propose one plan line and wait for your confirmation before any write.

What you’ll get

• Mode: diagnose, mutate-proposed, or mutate-done
• Endpoint, event, and delivery summaries
• A Next list — and a stop-for-confirm plan when a write is needed
• Signing secret shown once on create/rotate (store immediately; never re-logged)

Get started

1. Account-scoped $OUTBOUNDSYNC_API_KEY (Creating API keys). Ask support for write if you need mutations.
2. Install:

npx skills add outboundsync/skills --skill sync-monitoring -g

Security and confirm protocol: skills/sync-monitoring/ · SECURITY.md.