Skip to content

Sensors ​

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. Connecting your first one? The Getting Started page walks Slack or Google Meet end to end.

Dashboard and API

The dashboard lists these under Corvus → Sensors. Create one with Add sensor, or with POST /api/sensors.

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 source 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 match what the Add sensor form renders.

Choosing between overlapping sources ​

Google Meet and Google Drive both ingest Gemini meeting notes, and what either captures is governed by your Workspace's note-taking policy rather than by source config. If you are setting up meeting capture, read Choosing a meeting-capture path before you pick — it compares the two, covers the per-organizer My Drive gap, and makes a recommendation.

Available sensors ​

These sensor types are available today — you can create them from Add sensor or with POST /api/sensors. They're grouped by what you're trying to ingest.

Engineering & delivery ​

SensorIngestsCredential type
GitHubIssues, PRs, commits, reviews, commentsgithub_token
GitLabMerge requests, issues, commits, commentsgitlab_token
BitbucketPRs, issues, commits, reviews (Cloud only)bitbucket_access_token
JenkinsCI/CD build results (webhook)none — server-issued token
Azure DevOpsWork items, repositories, PRs & reviews, pipeline builds (Services or on-prem Server)azure_devops_credentials
PagerDutyIncidents, services, and on-call shiftspagerduty_api_key

Meetings & conversations ​

SensorIngestsCredential type
Google MeetMeeting transcripts & participantsgoogle_service_account_json
Zoom TranscriptsCloud-recording transcripts & participantszoom_s2s_oauth
FirefliesMeeting transcripts, AI summaries & action itemsfireflies_api_key
GranolaAI meeting notes, transcripts, decisions & action itemsgranola_api_key
Otter.aiMeeting conversations, transcripts, decisions & assigned action itemsotter_api_key
SlackChannel messages & threadsslack_bot_token
Microsoft TeamsChannel messages & threads (GCC-High / DoD too); meeting transcripts on commercial tenants onlymicrosoft_graph
Google ChatSpace messages, thread replies & memberships (group chats / DMs opt-in)google_service_account_json
Google CalendarScheduled events, attendees & recurrencegoogle_service_account_json
Outlook CalendarScheduled meetings across org membersmicrosoft_graph
OutlookMail threads across org membersmicrosoft_graph
GongSales call transcripts & participantsgong_access_key
GmailMailbox messages, threads & senders/recipientsgoogle_service_account_json

Documents & knowledge ​

SensorIngestsCredential type
Google DriveDocs, Sheets, Slides, and file comments in a foldergoogle_service_account_json
ConfluenceWiki pages & comments (Cloud)jira_api_token
Confluence Data CenterWiki pages & comments (self-hosted)atlassian_dc_pat
NotionWiki pages & commentsnotion_token
AirtableRecords & comments in a baseairtable_pat
FigmaDesign files, comment threads, and version historyfigma_access_token
LucidLucidchart diagrams & Lucidspark boards, with their shape textlucid_credentials
SharePoint / OneDriveDocuments in SharePoint & OneDrive librariesmicrosoft_graph
OneNoteNotebooks, sections & pages a signed-in account can openmicrosoft_graph_delegated
BoxFiles, folders, comments & collaboratorsbox_client_credentials
DropboxFiles, folders & shared-folder members in a Dropbox teamdropbox_team_oauth
Amazon S3Documents, exports & reports in a bucket prefixaws_access_key
Local File WatcherDocuments, exports & reports in a mounted directorynone — operator-mounted volume

Work tracking ​

SensorIngestsCredential type
JiraIssues & changelog activity (Cloud)jira_api_token
Jira Data CenterIssues & comments (self-hosted)atlassian_dc_pat
LinearIssues & comments (Cloud)linear_api_key
AsanaTasks & comments (Cloud)asana_pat
Monday.comBoard items & updates (Cloud)monday_api_token
ServiceNowIncidents, problems, changes, requested items, KB articles & approvals (cloud, government, or self-hosted)servicenow_credentials

Business & CRM ​

SensorIngestsCredential type
shell-crmCompanies, contacts, deals, and related activity, including who-knows-whoshellcrm_api_key
HubSpotCRM objects + notes, emails, calls & meetingshubspot_access_token
IntercomCompanies, contacts, and customer conversationsintercom_access_token
SalesforceCRM objects + notes, emails, calls, meetings & taskssalesforce_connected_app
ZendeskSupport tickets, comments, and customer organizationszendesk_api_token
ZoomInfoFirmographic and job-title enrichment of the Organizations and People other sensors created (no bulk import)zoominfo_pki

HR & People ​

SensorIngestsCredential type
GreenhouseJobs, candidates, applications, interviews, scorecards, and offersgreenhouse_harvest_api_key
LeverPostings and opportunities (candidates in pipeline)lever_api_key
Microsoft Entra IDOrg chart — people, departments, groups, and who reports to whom from the Microsoft directorymicrosoft_graph
WorkdayWorkers and supervisory organizations — org chart and role contextworkday_api_client
BambooHROrg chart, team structure, and role context from the employee directorybamboohr_api_key
RipplingOrg chart — companies, departments, teams, and workersrippling_api_token
GustoOrg chart — company, departments, employees, and contractorsgusto_api_client
OktaIdentity backbone — users, groups, group membership, and reporting linesokta_service_app or okta_api_token

Corveil-native ​

AI Chat (MCP usage capture) is a push-only source. There is no poll loop and nothing to create: the ontology MCP server records a sensor_event synchronously whenever a user calls a tool. The row is seeded for the org (ai_chat) and does not appear in Add sensor.

Custom ​

SensorIngestsCredential type
WebhookCustom JSON events (inbound webhook)none — server-issued token

Credential reuse across sources ​

Several sources share one credential, so a tenant that has connected one needs no second app registration for its siblings:

  • microsoft_graph backs Microsoft Teams, SharePoint / OneDrive, Outlook Calendar, Outlook, and Microsoft Entra ID. Adding Outlook to a tenant that already runs Teams, SharePoint, or Calendar only needs Mail.Read on the existing app registration; adding Entra ID needs User.Read.All and GroupMember.Read.All. OneNote is the exception: Microsoft no longer accepts app-only tokens for OneNote, so it uses its own microsoft_graph_delegated sign-in, on a dedicated app registration (see its setup guide for why).
  • google_service_account_json backs Google Meet, Google Drive, Google Calendar, Gmail, and Google Chat — Gmail reuses the existing domain-wide delegation grant, adding gmail.readonly; Google Chat adds the three chat.*.readonly scopes.
  • jira_api_token backs both Jira and Confluence on the same Atlassian Cloud site.
  • atlassian_dc_pat backs both Jira Data Center and Confluence Data Center. Cloud API tokens and Data Center PATs are not interchangeable.

Building your own ​

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