integrations · outbound

Connectors

Anomaly alerts pushed into the tools your team already uses — the evidence stays in Wytness; the alerting goes where your SOC looks.

at launch

Five connectors, one contract

Built medium-depth: robust enough for production, focused on the integrations your buyers actually ask about.

Push
Microsoft Sentinel
Push Wytness anomalies into your Log Analytics workspace via the Microsoft Sentinel Logs Ingestion API (customer-owned DCR + DCE + Entra OAuth2 token).
Setup guide
Push
Splunk
Push Wytness anomalies into your Splunk via the HTTP Event Collector (HEC) with newline-delimited JSON.
Setup guide
Push
ServiceNow
Push Wytness anomalies and findings into ServiceNow as incidents.
Setup guide
Push
Slack
Anomaly alerts in the channel your team already watches.
Setup guide
Push
Generic webhook
Outbound signed webhooks for anything else.
Setup guide

the roadmap

Asks we hear repeatedly

If you need one of these for a deal, the generic webhook gets you there today and we'll prioritise the native integration.

Q1 2027

Datadog

Q1 2027

PagerDuty

Q1 2027

Jira

Q1 2027

Microsoft Teams

Q1 2027

OpsGenie

in the product

One table, every destination

Connections live under Integrations → Connectors: per-connection health, alert filters, and a per-delivery log with status, HTTP code, and attempts.

app.wytness.ai · integrations › connectors
test-before-save on every connectionfailed deliveries are recorded, never silent

Can't find your tool?

Every Wytness anomaly alert can be pushed to a signed webhook. Failed deliveries retry with jittered exponential backoff for about 20 minutes and land in the delivery log either way. The payload format is publicly documented with a signature-verification example in Python — the same HMAC pattern works in any language.

Generic webhook connector

for your platform team

One setup contract

Network requirements, delivery semantics, retry behaviour, and every wizard field — in one page you can hand to the team doing the integration.

Read the setup guide

Connect to the tools your SOC already runs.

Your auditor cares about the evidence. Your SOC cares about their dashboard. Wytness writes to both.

Start recordingAsk a question

We set no cookies. Sign-in and preferences use essential first-party browser storage only — no tracking, advertising, or third-party analytics. Privacy Policy