Prerequisites
Before you begin, you need:- A Kai Affective Intelligence API key (issued per organisation at onboarding)
- Admin access to your host platform (WordPress, Slack, Teams, or custom)
- Nominated content sources to monitor (channels, comment threads, or survey streams)
Integration flow
Install
Admin installs the Kai connector from the platform marketplace or via manual package. A single API key is entered — this ties the connector to the organisation’s Kai account and sets the data scope.
Configure
Admin nominates which channels, comment threads, or content sources to monitor. Sets anonymisation floor (minimum group size before signals are surfaced), alert thresholds, Kai tone, and which signal layers to include.
Ingest
The connector pulls content from nominated sources, strips all identifiers, assigns pseudonymous uids (customer-side — Kai never sees real identities), and sends text batches to
POST /ingest. Raw text is never stored.Platform requirements
WordPress
WordPress
PHP 8.0+. WordPress 6.0+. Calls Kai API server-side. Renders dashboard in admin panel or shortcode-embeddable widget.
Slack
Slack
Slack App manifest with slash commands and Block Kit rendering. Scheduled Pulse digest posted to nominated channel.
Microsoft Teams
Microsoft Teams
Teams App with adaptive card rendering. Dashboard tab in Teams channel. Alert notifications via bot framework.
Custom / headless
Custom / headless
REST API with OpenAPI 3.0 spec. React component library for white-label embed. SDK: JavaScript / Python.
Next steps
Plugin architecture
Understand how content flows in and signals flow out.
Admin configuration
Configure cohorts, signal layers, and alert thresholds.
Authentication
Set up Bearer token authentication for API calls.
POST /ingest/batch
Send your first content batch for analysis.