Sensor Guides

Sensors are how Corveil ingests activity from the tools your organization already uses. Each sensor polls (or receives webhooks from) an external system, normalizes events, and feeds them into the intelligence pipeline.

Every guide on this page follows the same shape:

1. What it ingests
2. Credential — which credential vault type to create
3. Config fields — the keys the sensor accepts
4. Provider-side setup — prerequisites on the source system
5. Wire-up — the POST /api/sensors payload
6. Verify — how to confirm it's working

The config and credential fields documented here are sourced from each sensor's registered spec (sensor.RegisterSpec in go/internal/sensor/*), so they match what the Add sensor form renders.

Available sensors

These sensor types are implemented and registered — you can create them today.

Sensor	Ingests	Credential type
GitHub	Issues, PRs, commits, reviews	github_token
Google Meet	Meeting transcripts & participants	google_service_account_json
Google Drive	Docs, Sheets, Slides in a folder	google_service_account_json
Slack	Channel messages & threads	slack_bot_token
Jira	Issues & changelog activity	jira_api_token
Jenkins	CI/CD build results (webhook)	none — server-issued token
shell-crm	Companies, deals, contacts, etc.	shellcrm_api_key

Always-on sensors

Two sensors need no connector setup because their source is Corveil itself:

• AI Gateway — ingests Corveil's own daily Insights summaries. No config, no credential; it reads this org's data through an internal handle.
• AI Chat (MCP usage capture) — a push-only sensor. There's no poll loop and nothing to configure: the ontology MCP server records a sensor_event synchronously whenever a user calls a tool.

Coming soon

These appear in the Sensors catalog as planned integrations but do not yet have a registered backend. They have no setup guide yet:

Zoom · Microsoft Teams · Gmail · Microsoft Outlook · OneDrive / SharePoint · Confluence / Notion · GitLab · Linear · PagerDuty / OpsGenie · Salesforce · HubSpot · Gong · Google Calendar · S3 / file-drop watch

Building your own

Any data source can feed Corveil through the Plugin SDK or a generic inbound webhook. See the plugin guide for the sensor lifecycle interface.