# Integrations

Source: https://docs.ops0.com/docs/settings/integrations

Connect cloud providers, version control, observability, and alerting systems to ops0. Integrations let `brew.ops0.ai` discover resources, run deployments, sync code, and send operational signals into the tools your teams already use.

![ops0 Integrations settings page showing connected providers](https://docs.ops0.com/images/settings-integrations.png)

## Accessing Integrations

### Go to Settings
Navigate to **Settings** from the main sidebar.

### Open Integrations
Select **Integrations** to view connected providers, statuses, and available setup flows.

---

## Integration Categories

- [Cloud](#cloud-integrations): AWS, GCP, Azure, and Oracle Cloud for deployments and discovery.

- [Git](#git-integrations): GitHub and GitLab for repository sync, pull requests, and version-control workflows.

- [Observability](https://docs.ops0.com/docs/settings/integrations/observability): Route logs, plans, and policy output into your observability stack.

- [Alerts](https://docs.ops0.com/docs/settings/integrations/alerts): Send delivery, approval, and incident alerts into collaboration channels.

---

## Integration Status Badges

Every integration card shows a real-time status badge:

| Status | Meaning |
|--------|---------|
| **Connected** | Active and working |
| **Syncing** | A sync operation is currently running |
| **Pending** | Created but not yet verified |
| **Partial** | Some operations work, others fail (e.g. discovery succeeds but deployment fails due to missing permissions) |
| **Error** | Last operation failed — hover the badge to see the error message |

Click any **Error** badge for the full error detail and suggested resolution steps.

---

## Shared Fields

Most integrations expose a common management surface in ops0:

| Field | Description |
|-------|-------------|
| **Name** | Human-readable label for the integration |
| **Type** | Provider or category, such as AWS, GitHub, or Slack |
| **Status** | Connection health (see status badges above) |
| **Created** | When the integration was added |
| **Last Used** | The most recent time ops0 used the integration |

---

## Cloud Integrations

Cloud integrations provide provider-specific credentials and trust relationships so ops0 can discover resources, run deployments, and scope access correctly.

- [Aws](https://docs.ops0.com/docs/settings/integrations/aws): Role-based access for deployments and discovery.

- [Gcp](https://docs.ops0.com/docs/settings/integrations/gcp): Project and service-account access for resource operations.

- [Azure](https://docs.ops0.com/docs/settings/integrations/azure): Subscription access through a service principal.

- [Oracle](https://docs.ops0.com/docs/settings/integrations/oracle): OCI API credentials and compartment-level scope.

**Provider-Specific Setup**

Each cloud provider has its own setup page because authentication models, required fields, and permission boundaries differ significantly.

---

## Git Integrations

Git integrations connect ops0 projects to source-control providers for syncing IaC code, opening pull or merge requests, and managing repository access.

- [Github](https://docs.ops0.com/docs/settings/integrations/github): Authorize repositories and connect pull-request workflows.

- [Gitlab](https://docs.ops0.com/docs/settings/integrations/gitlab): Connect GitLab repositories and merge-request automation.

---

## Observability

Observability integrations send execution output and policy context into logging and monitoring systems.

- [Observability Guide](https://docs.ops0.com/docs/settings/integrations/observability): Overview, supported provider details, data types, and troubleshooting.

- [OpenObserve](https://docs.ops0.com/docs/settings/integrations/openobserve): Legacy alias path retained for compatibility.

---

## Alerts

Alerts integrations deliver deployment notifications, approval requests, policy findings, and incident signals into collaboration tools.

- [Alerts Guide](https://docs.ops0.com/docs/settings/integrations/alerts): Configure channels, alert types, and workspace authorization.

- [Slack](https://docs.ops0.com/docs/settings/integrations/alerts#slack): Current supported alerts provider.

---

## Lifecycle Actions

After an integration is added, the operational lifecycle is broadly the same regardless of provider:

### Test Connection
Run a connectivity check to verify that credentials, scope, and network access are valid.

### Edit Configuration
Update names, endpoints, regions, channels, or provider-specific settings as requirements change.

### Rotate Credentials
Replace keys, secrets, tokens, or app access when your rotation policy requires it.

### Review Usage
Confirm which projects, workflows, or scans rely on the integration before changing or deleting it.

### Delete Safely
Remove the integration only after checking for affected projects, workflows, or automation.

---

## Naming Guidance

Use explicit names so teams can distinguish integrations quickly:

| Good Example | Why It Works |
|--------------|--------------|
| `aws-production-us-east-1` | Captures provider, environment, and region |
| `gcp-analytics-prod` | Makes project purpose obvious |
| `github-platform-org` | Identifies account or org scope |
| `slack-deploy-alerts` | Indicates the alerting use case |

---

## Related

- [Connect Your Cloud](https://docs.ops0.com/docs/getting-started/connect-cloud): Set up your first cloud provider connection.

- [Settings](https://docs.ops0.com/docs/settings): Return to the settings hub for admin and organization controls.