Install your first evidence adapter

Kiket ships evidence adapters as installable extensions — kiket-extension.yaml at the repo root, normalization via the SDK, and ingress through /platform/* with scoped API keys.

Install Slack (catalog-hosted)

Open evidence sources

In the web app go to Settings → Evidence sources (or use Install in app from the public marketplace with ?install=kiket-ext-slack).

Install from the extension catalog

Under Extension catalog, choose Slack evidence adapter and click Install with Kiket runner (or configure push/pull transport). Copy the runner API key when shown — it is displayed once.

Register a Slack webhook source with POST /platform/event-sources (or the in-app wizard). Point Slack at POST /integrations/slack/webhook with X-Kiket-Organization-Id and X-Kiket-Event-Source-Key.

Verify ingestion

Post a test payload with kiket extension test or send a real message; confirm raw events normalize and appear on linked cases.

What adapters do

Ingress only — adapters call Kiket (or receive webhooks on Kiket ingress routes), not outbound issue webhooks from core.
Scoped keys — runner keys use raw-events:submit and raw-events:claim; org API keys use least-privilege scopes.
Explainable evidence — normalized types feed the scanner; findings link back to proof.

Shipped adapters

GitHub

PRs, reviews, CI, and deployment evidence.

Slack

Approval and discussion evidence.

Jira

Work-item lifecycle and comments.

ServiceNow

ITSM records and comments.

Generic webhook

Field-mapped JSON ingress.

Browse the public marketplace or Integrations overview.

Build or publish your own

kiket extension init — scaffold manifest + adapter.
kiket extension validate / kiket extension test — local checks.
kiket extension publish — list in your org catalog (optional gitUrl for pull installs).

See Extension adapters and Evidence adapters (API).