Integrations

Connect integrations in the console under Settings, Integrations (needs the integrations:read member scope to view, and integrations:manage to connect). Each integration page follows the same outline: what it does, requirements, how to connect, permissions, data handling, troubleshooting and known limitations.

Communication and tickets

SlackFindings alerts, notifications and conversations with AI engineers.JiraTurn findings into tickets and read your backlog.

Source control

GitHubRepositories, advisories, and the Nebula for GitHub app.GitLabProjects, issues, merge requests and code search.

Workspace suites

Google WorkspaceRead Gmail and Drive, and send Gmail with your consent.Microsoft 365Read Outlook mail and OneDrive or SharePoint files.

Data and tools

Recon providersShodan, VirusTotal, Censys and eleven more intelligence sources.Custom APIConnect any HTTPS API with an API key or basic authentication.MCP serversGive Nebula tools from Model Context Protocol servers.

How integrations use your credentials

• Credentials are write-only. Tokens and keys you enter are stored encrypted and never shown again; the console and API only report whether one is set.
• Requests go through a broker. Nebula calls a connected service through BreachLine’s integration proxy, which fixes the destination host, allows only a short list of request headers, never follows redirects, redacts credentials echoed in responses, caps responses at 2 MiB and times out after 30 seconds.
• Personal data stays personal. Mail and files from a personal OAuth connection (Google, Microsoft 365) can only be used by the member who connected them. Organization membership alone does not share another person’s mailbox.
• Use needs permission. Using a connected integration needs the integrations:use member scope.