> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/ai-sre/3.0/ai-sre-for-administrators/set-up-runbook-management/integrations/overview.md).

# Runbook Integrations Overview

Harness AI SRE runbooks can integrate with third-party tools to automate incident response workflows.

Most integrations on this page provide **automation**: they let a runbook act on an external tool during a response. The exception is xMatters, which is on-call schedule sync only and runs no runbook actions. Several of these tools also ingest data elsewhere in AI SRE. Go to [Set Up Integration Management](/ai-sre/ai-sre-for-administrators/set-up-integration-management/index.md) to review the full capability matrix.

### Available integrations <a href="#available-integrations" id="available-integrations"></a>

#### Collaboration tools <a href="#collaboration-tools" id="collaboration-tools"></a>

* [Slack](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/collaboration/slack.md): Send messages, create channels, manage incident communication
* [Microsoft Teams](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/collaboration/teams.md): Post messages, create teams, coordinate response
* [Google Chat](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/collaboration/google-chat.md): Send messages to spaces and threads
* [Zoom](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/collaboration/zoom.md): Create meetings, generate conference bridges

#### Incident management & on-call <a href="#incident-management-and-on-call" id="incident-management-and-on-call"></a>

* [PagerDuty](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/incident-management/pagerduty.md): Create incidents, trigger escalations, manage on-call
* [OpsGenie](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/incident-management/opsgenie.md): Create alerts, page teams, acknowledge incidents
* [xMatters](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/incident-management/xmatters.md): On-call synchronization only (no runbook actions)

#### Ticketing & documentation <a href="#ticketing-and-documentation" id="ticketing-and-documentation"></a>

* [Jira](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/jira.md): Create issues, add comments, track incident work
* [ServiceNow](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/servicenow.md): Create incidents, update records, manage ITSM workflows
* [Confluence](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/confluence.md): Create pages, update documentation, maintain knowledge base

#### Source control <a href="#source-control" id="source-control"></a>

* [GitHub](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/source-control/github.md): Create branches, pull requests, issues
* [Harness Pipelines](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/source-control/harness-pipelines.md): Trigger deployment pipelines, execute automation

These connectors ensure that actions performed by your runbooks are properly attributed to specific service accounts.

{% hint style="info" %}
Project-level connectors provide better accountability and access control compared to organization-level connectors.
{% endhint %}

***

### Why project connectors? <a href="#why-project-connectors" id="why-project-connectors"></a>

When executing runbook actions that interact with external tools (Zoom, GitHub, Jira), Harness AI SRE needs to authenticate as a specific user or service account. Project connectors ensure:

* Actions are performed using dedicated service accounts
* Activities can be properly tracked and audited
* Access permissions are scoped to project needs
* Integration credentials are managed at the project level

***

### Accessing project connectors <a href="#accessing-project-connectors" id="accessing-project-connectors"></a>

To configure project connectors:

1. Sign in to your Harness account
2. Go to your project
3. Go to **Project Settings**, then **Third-Party Integrations (AI SRE)**
4. Select the integration type you want to configure

***

### Configuring project connectors <a href="#configuring-project-connectors" id="configuring-project-connectors"></a>

#### Best practices <a href="#best-practices" id="best-practices"></a>

When setting up project connectors:

1. Create dedicated service accounts for runbook actions
2. Use project-specific service accounts rather than shared accounts
3. Document the purpose and ownership of each connector

#### Selecting or creating connectors <a href="#selecting-or-creating-connectors" id="selecting-or-creating-connectors"></a>

In **Project Settings**, then **Third-Party Integrations (AI SRE)**, you can either:

* Select an existing connector from the list if one is already configured with appropriate permissions
* Create a new connector if you need a dedicated service account for your project's runbook actions

#### Creating new connectors <a href="#creating-new-connectors" id="creating-new-connectors"></a>

Only follow these steps if you need to create a new connector. If an appropriate connector already exists, you can select it from the list.

**Zoom connector**

If you need a new Zoom connector:

1. Click **Add Zoom Connector**
2. Configure:
   * Name: A descriptive name for the service account's purpose
   * Authentication: OAuth (recommended)
   * Service Account: Dedicated Zoom account for runbook actions
3. Test the connection
4. Save the configuration

**GitHub connector**

If you need a new GitHub connector:

1. Click **Add GitHub Connector**
2. Configure:
   * Name: A descriptive name for the service account's purpose
   * Authentication: GitHub App or OAuth
   * Repository Access: Only repositories needed for runbook actions
3. Test the connection
4. Save the configuration

**Jira connector**

If you need a new Jira connector:

1. Click **Add Jira Connector**
2. Configure:
   * Name: A descriptive name for the service account's purpose
   * Authentication: API Token (recommended)
   * Project Access: Only projects needed for runbook actions
3. Test the connection
4. Save the configuration

***

### Using project connectors in runbooks <a href="#using-project-connectors-in-runbooks" id="using-project-connectors-in-runbooks"></a>

When creating runbook actions:

1. Add an integration action (Create Jira Issue, Schedule Zoom Meeting, etc.)
2. The project connector you configured will be automatically used
3. The action will be performed using the service account associated with the connector

{% hint style="info" %}
Always test runbook actions in a non-production environment to verify proper authentication and permissions.
{% endhint %}

***

### Next steps <a href="#next-steps" id="next-steps"></a>

* [Create a runbook](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/create-runbook.md): Start using these integrations.
* [Jira integration](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/jira.md): Configure Jira in detail.
* [Slack integration](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/collaboration/slack.md): Configure Slack in detail.