> 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/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/confluence.md).

# Confluence Integration

Automate Confluence postmortem pages and knowledge base updates directly from AI SRE runbook actions.

Integrate Confluence with AI SRE runbooks to automate documentation and knowledge base updates during incident response.

### Use cases <a href="#use-cases" id="use-cases"></a>

Use the Confluence integration to keep incident documentation current:

* Create incident postmortem pages
* Update runbook documentation
* Add incident notes to knowledge base
* Track incident history in Confluence
* Generate incident reports

***

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Confluence account with page creation permissions
* Confluence API token
* Space permissions for the spaces you need to update

***

### Configure the Confluence integration <a href="#configure-the-confluence-integration" id="configure-the-confluence-integration"></a>

Connect AI SRE to your Confluence site with an API token:

1. Go to **Project Settings**, then **Third-Party Integrations for AI SRE**.

   ![Third-Party Integrations for AI SRE](https://2800896578-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwfoiKanOBqsfhP1BJKpx%2Fuploads%2Fgit-blob-37244248e40f71fcc0afc129e4539f65551812dc%2Fthird-party-integrations-connectors.png?alt=media)
2. Select the connector you want to use or create a new one.
3. Provide your Confluence credentials:
   * **Site URL:** Your Confluence site URL (e.g., `https://yoursite.atlassian.net/wiki`)
   * **Email:** Your Atlassian account email
   * **API Token:** Generate from Atlassian account settings
4. Test the connection.
5. Save the integration.

***

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

#### Post content to Confluence <a href="#post-content-to-confluence" id="post-content-to-confluence"></a>

Create a new page or update an existing page in Confluence with specified content.

**Required fields:**

* Space Key: Confluence space identifier where the page will be created or updated
* Page Title: Title of the Confluence page
* Content: Page content in Confluence storage format (HTML)

**Optional fields:**

* Page ID: ID of existing page to update. If not provided, a new page will be created

**Outputs:**

* Page ID: ID of the created or updated page
* Page URL: URL to access the page
* Version: Version number of the page

***

### Use Confluence actions in runbooks <a href="#use-confluence-actions-in-runbooks" id="use-confluence-actions-in-runbooks"></a>

Confluence actions are configured through the runbook action form in the UI:

1. **In your runbook**, click **New Step**, then **Action**.

   ![New Step Menu](https://2800896578-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwfoiKanOBqsfhP1BJKpx%2Fuploads%2Fgit-blob-d6dffd9114e1a1085c8d3178fe25d3a125df1d23%2Frunbook-new-step-menu.png?alt=media)
2. In the **Select Action** dialog, go to the **Communication** category.
3. Select **Post Content to Confluence** from the available actions.

   ![Select Action Dialog](https://2800896578-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwfoiKanOBqsfhP1BJKpx%2Fuploads%2Fgit-blob-5980a6d1b48301e019bb7d9734e07fb22616679e%2Frunbook-select-action-dialog.png?alt=media)
4. Fill in the form fields using the **Data Picker** to insert dynamic values like `incident.severity`, `incident.title`, etc.

***

### Available Mustache variables <a href="#available-mustache-variables" id="available-mustache-variables"></a>

Use these variables to map AI SRE incident data to Confluence fields:

| Variable                   | Description                   | Example Value                           |
| -------------------------- | ----------------------------- | --------------------------------------- |
| `{{Activity.title}}`       | Incident title                | `API Gateway Outage`                    |
| `{{Activity.summary}}`     | Incident summary              | `Payment API returning 500 errors`      |
| `{{Activity.severity}}`    | Incident severity             | `0`, `1`, `2`, `3`, `4`                 |
| `{{Activity.status}}`      | Incident status               | `Detected`, `Investigating`, `Resolved` |
| `{{Activity.service}}`     | Affected service name         | `payment-service`                       |
| `{{Activity.environment}}` | Environment                   | `production`, `staging`                 |
| `{{Activity.owner}}`       | Incident owner email          | `jane.doe@company.com`                  |
| `{{Activity.created_at}}`  | Incident creation timestamp   | `2026-05-06T20:30:00Z`                  |
| `{{Activity.resolved_at}}` | Incident resolution timestamp | `2026-05-06T21:15:00Z`                  |
| `{{Activity.url}}`         | Incident URL in AI SRE        | `https://app.harness.io/...`            |
| `{{Activity.short_id}}`    | Human-readable ID             | `INC-123`                               |

***

### Example runbook actions <a href="#example-runbook-actions" id="example-runbook-actions"></a>

#### Create an incident postmortem page <a href="#create-an-incident-postmortem-page" id="create-an-incident-postmortem-page"></a>

**Use case:** Automatically create a Confluence page template for incident postmortem documentation.

**Runbook configuration:**

1. In the runbook editor, add a **Post Content to Confluence** action.
2. Configure the form fields:
   * **Space Key:** `INCIDENTS`
   * **Page Title:** `Postmortem - {{Activity.title}}`
   * **Content** (using Confluence storage format HTML):

     ```html
     <h1>Incident Postmortem: {{Activity.short_id}}</h1>

     <h2>Summary</h2>
     <p><strong>Title:</strong> {{Activity.title}}</p>
     <p><strong>Severity:</strong> SEV{{Activity.severity}}</p>
     <p><strong>Duration:</strong>
       {{Activity.created_at}} - {{Activity.resolved_at}}
     </p>
     <p><strong>Service:</strong> {{Activity.service}}</p>
     <p>
       <strong>Environment:</strong> {{Activity.environment}}
     </p>

     <h2>Timeline</h2>
     <p><em>To be filled during postmortem</em></p>

     <h2>Root Cause</h2>
     <p><em>To be determined</em></p>

     <h2>Action Items</h2>
     <p><em>List action items here</em></p>

     <h2>Links</h2>
     <p>
       <a href="{{Activity.url}}">Incident in AI SRE</a>
     </p>
     ```
   * **Page ID:** Leave blank to create a new page

**Result:** New Confluence page created in `INCIDENTS` space with title `Postmortem - API Gateway Outage`, containing incident details and postmortem template sections.

#### Update existing runbook documentation <a href="#update-existing-runbook-documentation" id="update-existing-runbook-documentation"></a>

**Use case:** Update an existing runbook documentation page with recent incident information.

**Runbook configuration:**

1. In the runbook editor, add a **Post Content to Confluence** action.
2. Configure the form fields:
   * **Space Key:** `ENGINEERING`
   * **Page Title:** `Runbook Documentation`
   * **Content** (append incident entry):

     ```html
     <h2>Recent Incidents</h2>
     <ul>
       <li>
         {{Activity.short_id}} - {{Activity.title}} -
         SEV{{Activity.severity}} - {{Activity.created_at}}
       </li>
     </ul>
     ```
   * **Page ID:** Enter the Confluence page ID to update

**Result:** Existing Confluence page updated with the latest incident entry. Because a Page ID was provided, the existing page is updated rather than creating a new one.

***

### Confluence wiki markup reference <a href="#confluence-wiki-markup-reference" id="confluence-wiki-markup-reference"></a>

#### Headers <a href="#headers" id="headers"></a>

```
h1. Heading 1
h2. Heading 2
h3. Heading 3
```

#### Lists <a href="#lists" id="lists"></a>

```
* Bullet point
# Numbered list <a href="#numbered-list" id="numbered-list"></a>
```

#### Links <a href="#links" id="links"></a>

```
[Link text|https://example.com]
[Link to page|Page Title]
```

#### Text styles <a href="#text-styles" id="text-styles"></a>

```
*bold*
_italic_
{{monospace}}
{code}code block{code}
```

***

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

Protect your Confluence integration with these safeguards:

* Use API tokens instead of passwords
* Limit space access to only what is needed
* Rotate API tokens regularly
* Use read-only access when possible
* Audit integration usage regularly

***

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

* [Configure Runbook Actions](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/create-runbook.md): Add Confluence actions to runbooks.
* [Runbook Best Practices](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/best-practices.md): Review automation patterns.

{% @harness-feedback/feedback %}