Integrations & Automations
Connect Guard to the messaging, routing, ticketing, and runbook tools your team already uses.
Filter
Browse integrations
Providers
Connected and available providers
Each provider below can receive Guard alerts, trigger automations, and appear in your investigation timeline.
No providers match this filter yet
Clear one of the URL filters or open the automation builder to start from the most useful route first.
Open automation builderExplain this route
Trust, privacy, and decision boundaries
See what proof Guard has collected, what stays on your device, and why Guard is asking for your attention.
Proof & provenance
Every provider card should point back to active Guard investigations, automation history, and the exact linked work that justifies the connection.
- 100% local by default
- First-party canary fixtures
- Receipts on your device
What stays local versus what syncs
Local Guard can still review and enforce alone. This route exists to connect that local evidence to the external tools and shared operators that keep work moving.
- Agent discovery and tool snapshots
- Local diffs against your last approved state
- Receipt sync to Guard Cloud
- Curated advisory and revocation feeds
How Guard decides on this route
Integration routes should only ask for attention when shared handoff, connection health, or routing coverage is actually blocking triage.
- Prompts should appear only after real drift, queue pressure, or policy mismatch.
- Local protection stays useful on its own before cloud coordination is added.
- Every CTA should land on the exact queue or detail view that explains the state.