Integrations
Adoe works with the tools you already run. Nothing to migrate. Each integration below shows what adoe does with it, and whether it is available today.
Setup: "Dashboard" means you connect it yourself in adoe's Integrations page. "With our team" means we set it up with you during onboarding.
Alert sources
Where alerts come from. Each workspace gets private webhook addresses for these tools.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| Grafana | Receives alerts by webhook, including Prometheus Alertmanager payloads. Checks Grafana every 5 minutes for any alert it missed. | Available | Dashboard |
| PagerDuty | Receives incidents by webhook, with an optional signature check. Resolves linked alerts when the PagerDuty incident resolves. Links each incident back to the check that raised it. | Available | Dashboard |
| Sensu | Receives check events by webhook. Syncs your check definitions every 12 hours, so adoe knows what each check watches. | Available | Dashboard |
| Splunk | Receives saved-search alerts by webhook. Syncs your alert definitions every 12 hours. | Available | Dashboard |
| Uptime.com | Receives alerts by webhook and checks for new ones every 8 hours. Marks the alert as handled in Uptime.com when adoe resolves it. | Available | Dashboard |
| Railway | Receives deploy, volume, CPU and memory events. | Available | Dashboard |
| Datadog | Receive Datadog monitor alerts. | Planned | — |
| Opsgenie | Receive Opsgenie alerts. | Planned | — |
Evidence and context
What adoe reads to investigate. Read access is enough for all of these.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| Grafana | Reads metrics during investigation and to verify fixes. Prometheus data is read through Grafana. | Available | Dashboard |
| Splunk | Reads log events around the alert. | Available | Dashboard |
| GitHub | Finds the alert's definition in your code, and reads recent commits and pull requests. Imports SOPs from a repository, and opens pull requests for new SOPs. | Available | Dashboard and with our team |
| Bitbucket | Finds the alert's definition in your code. | Available | With our team |
| Semaphore | Reads recent deploys, to spot changes before the alert. | Available | With our team |
| AWS | Lists your resources across 10 types, reads CloudTrail to see who changed what, and reads CloudWatch metrics. Uses a role in your own account. | Available | Dashboard |
| Confluence | Imports your written procedures as SOP drafts, for an admin to approve. | Available | Dashboard |
| Kubernetes | Read cluster state through the Kubernetes API. Today, adoe lists EKS clusters through AWS. | Planned | — |
Runbooks and actions
How fixes run. Your SOP picks the runbook, and a person approves it first, unless you choose otherwise for that SOP.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| GitHub Actions | Runs a workflow as a runbook, with the alert's details as inputs. | Available | With our team |
| AWS Systems Manager | Runs an SSM document as a runbook. | Available | With our team |
| SSH | Runs a command on a host, directly or through a bastion host. | Available | With our team |
| Scripts | Runs approved commands. Chained commands, redirects and background jobs are blocked. | Available | With our team |
| Built-in AWS actions | Reboots or starts an EC2 instance, or forces a new ECS deployment, through the role in your account. Always with approval. | Available | Dashboard |
| Sensu and Grafana silences | Silences a noisy check while a person looks at it. Always with approval. | Available | Dashboard |
| Azure, Google Cloud, Kubernetes | Run actions in these platforms. | Planned | — |
Chat and notifications
Where your team talks to adoe.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| Slack | Posts approval requests and updates in the alert's thread. Answers when you mention adoe there. Posts the weekly shadow report. | Available | Dashboard |
| PagerDuty updates | Add notes to PagerDuty incidents and resolve them from adoe. | Planned | — |
| Send escalations by email. | Planned | — | |
| Microsoft Teams | Approval requests and updates in Teams. | Planned | — |
Identity
How your team signs in, and how accounts are kept in sync.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| SAML 2.0 single sign-on | Sign in through your identity provider, such as Okta, Microsoft Entra ID or Google Workspace. Admins can require it. | Available | Dashboard |
| OpenID Connect sign-on | Sign in with any OpenID Connect provider. | Available | Dashboard |
| SCIM 2.0 | Creates, updates and removes users and groups from your identity provider. | Available | Dashboard |
AI assistants
Ask about your incidents from the assistant you already use. Access is read-only. It uses MCP, the Model Context Protocol: a standard way for AI assistants to use tools.
| Integration | What adoe does with it | Status | Setup |
|---|---|---|---|
| Claude | Read alerts, incidents, investigations and SOPs from Claude Code, Claude Desktop and claude.ai. | Beta | With our team |
| Cursor | The same read-only access from Cursor. | Beta | With our team |
Product names and logos belong to their owners and appear here only to show compatibility. Missing a tool you use? Tell us.
See adoe with your own stack
Book a technical demo. Bring your monitoring tool and one recent incident.