Documentation

Connect Henneth to the stack you already run.

Five first-party integrations cover the edge, identity, productivity, and incident-response surfaces most of our customers run. Configure once and Lens, Prism, and Playbooks all light up.

Overview

Henneth is built to plug into infrastructure you already operate, not to replace it. The integrations below cover the four surfaces we touch most often: the CDN edge (Cloudflare, Akamai), identity and document access (Google Suite), and the channels your team already uses to act on what we surface (Slack, Microsoft Teams).

Every integration installs the same way: enable it from the connector library in app.henneth.ai, complete the OAuth or token exchange, and Lens, Prism, and Playbooks become aware of the connection automatically.

Edge · CDN

Cloudflare

Serve Prism feeds at the edge, route agent traffic, and ship logs into Lens.

Edge · CDN

Akamai

Property Manager rules, EdgeWorkers, and DataStream 2 hooked into Lens visibility.

Identity · Docs

Google Suite

SSO via Workspace, Drive sources for Playbooks, scheduled exports to Sheets.

Channels

Slack

Real-time Lens alerts, Playbook approvals in-channel, slash commands.

Channels

Microsoft Teams

Adaptive-card alerts, channel-scoped approvals, Power Automate triggers.

Authentication

All integrations authenticate through the Henneth OAuth broker. You will not need to manage refresh tokens by hand, the broker handles rotation and exposes a stable token reference your Playbooks can call.

# list active integrations for the current workspace
curl "https://api.henneth.ai/v1/integrations" \
  -H "Authorization: Bearer $HENNETH_API_KEY"

Cloudflare

/docs/integrations/cloudflare

CDNEdge functionsLogsBot management

The Cloudflare integration lets you serve Prism feeds from Cloudflare’s edge, route AI-agent traffic with Workers, and stream Cloudflare Logs into Lens for end-to-end attribution.

What it does

Publishes your Prism JSONL feed as an edge route at /.well-known/agent-commerce.json, cached close to the agent.
Provisions a Cloudflare Worker that identifies known agent user-agents and tags requests with an x-henneth-agent header.
Streams Logpush events into Lens so visibility scores can be cross-referenced with real agent traffic.
Reads bot-management classifications to separate verified agent crawls from scrapers.

Install

From the integration library, click Connect Cloudflare. You’ll be redirected to Cloudflare for OAuth and asked to grant scoped access to the zones you want to expose.

# required Cloudflare permissions
zone:read
worker:edit
logpush:edit
bot_management:read

Worker template

Henneth provisions the worker for you, but the source is open and forkable:

export default {
  async fetch(req, env) {
    const ua = req.headers.get("user-agent") || "";
    const isAgent = /GPTBot|ClaudeBot|PerplexityBot|Google-Extended/i.test(ua);
    if (isAgent) {
      const res = await fetch(req);
      const next = new Response(res.body, res);
      next.headers.set("x-henneth-agent", "true");
      return next;
    }
    return fetch(req);
  }
};

Tip. Combine with Cloudflare’s Cache Rules to give agents a longer TTL on product pages, lower latency means higher inclusion in time-bounded responses.

Akamai

/docs/integrations/akamai

CDNEdgeWorkersDataStream 2Bot Manager

For enterprise customers running Akamai, Henneth ships a Property Manager rule template, an EdgeWorker for agent identification, and a DataStream 2 destination that pipes logs directly into Lens.

What it does

Installs a Property Manager rule set that identifies agent traffic by user-agent and ASN.
Deploys an EdgeWorker bundle that adds the x-henneth-agent trust header at the edge.
Configures DataStream 2 to push logs into Henneth’s ingest endpoint with sub-minute latency.
Reads Bot Manager scoring so you can isolate confirmed-agent traffic from impersonators.

Install

Akamai uses API client credentials rather than OAuth. Generate an API client in Identity & Access Manager with the scopes below, then paste the four-tuple into the Henneth connector form.

# required Akamai API scopes
Property Manager (PAPI)        : read-write
EdgeWorkers                    : read-write
DataStream Configuration       : read-write
Bot Manager                    : read-only

DataStream destination

The integration auto-creates a stream targeting:

https://ingest.henneth.ai/v1/edge/akamai/{workspace_id}

Logs are HMAC-signed using a secret rotated every 24 hours by the Henneth broker. No manual key management required.

Note. If your contract restricts EdgeWorker deployments, the Property Manager rule set works standalone, you’ll lose the per-request trust header but keep log ingestion.

Google Suite

/docs/integrations/google-suite

SSODriveSheetsCalendar

Google Workspace integration covers three things: single sign-on for your team, Drive as a Playbook source, and scheduled exports of Lens reports to Google Sheets.

What it does

SSO via SAML or OIDC. Map Workspace groups to Henneth roles. Provision and de-provision through SCIM.
Drive as a source. Playbooks can read from Drive folders, watch for new files, and write reports back to a target folder.
Sheets export. Schedule any Lens table or playbook output to land in a Sheet on a daily, weekly, or monthly cadence.
Calendar. Optional, surface scheduled Playbook runs as Workspace calendar events for your marketing team.

Install

Workspace admins install Henneth from the Google Workspace Marketplace. The OAuth consent screen lists every scope; expand each to see the exact endpoints we call.

# requested OAuth scopes (all read-only unless noted)
openid email profile
https://www.googleapis.com/auth/drive.file        # scoped, write
https://www.googleapis.com/auth/spreadsheets      # write
https://www.googleapis.com/auth/admin.directory.user.readonly
https://www.googleapis.com/auth/calendar.events   # optional

Drive scope. We use drive.file, not full drive, Henneth can only read files explicitly shared with the integration or created by it.

Slack

/docs/integrations/slack

AlertsApprovalsSlash commandsDM digest

Slack is the most-used Henneth output. Lens insights, playbook approvals, and digest summaries all flow through it.

What it does

Posts Lens insights as block-kit messages with one-click actions (open in app, dismiss, snooze).
Sends Playbook approval requests with diff preview and approve / reject buttons. Approvals are signed and audit-logged.
Adds the /henneth slash command for ad-hoc visibility queries from any channel.
Delivers a daily DM digest to subscribed users at their local 08:00.

Install

Workspace admin installs from the connector library. Single-channel installs are supported, Henneth only posts to channels it’s explicitly invited to.

# Slack OAuth scopes
chat:write
chat:write.public
commands
users:read
users:read.email
im:write       # for digest DMs

Channel routing

Map Lens alert types to specific channels under Settings → Integrations → Slack → Routing. A typical setup:

competitive_move    → #marketing-radar
sentiment_drop      → #brand-pr
playbook_approval   → #content-ops
weekly_digest       → DM (head of digital, CMO)

Microsoft Teams

/docs/integrations/microsoft-teams

Adaptive cardsApprovalsPower AutomateSSO

The Teams integration mirrors the Slack one, with Microsoft-native primitives: adaptive cards instead of block-kit, Power Automate triggers instead of slash commands, Entra ID for identity.

What it does

Posts Lens insights as adaptive cards with inline actions and source citations.
Sends approvals as actionable cards. Approver clicks are validated against Entra ID identity.
Exposes a Power Automate connector with a dozen pre-built triggers (rank-change, sentiment-drop, new-prompt-cluster).
Inherits SSO from Entra ID when Google Workspace isn’t in use.

Install

Install from the Teams App Store or sideload the manifest from app.henneth.ai → Integrations → Teams → Manifest. Tenant admin consent is required for the directory-read and channel-post scopes.

# Microsoft Graph delegated permissions
ChannelMessage.Send
Team.ReadBasic.All
User.Read
User.ReadBasic.All
Directory.Read.All        # tenant admin consent

Power Automate trigger

Use the “When a Henneth event occurs” trigger to chain Lens signals into your existing Power Automate flows, e.g. open a ticket in ServiceNow when sentiment drops more than ten points week-over-week.

# trigger payload (abridged)
{
  "event": "sentiment_drop",
  "brand": "defacto",
  "agent": "perplexity",
  "delta_pts": -11.4,
  "sources": ["reddit.com/...", "trustpilot.com/..."],
  "detected_at": "2026-04-18T14:22:09Z"
}

More integrations on the roadmap, HubSpot, Snowflake, and Datadog next. Need something not listed? Talk to us.