---
title: "Documentation Agent recipe for Slack and Telegram | Agent Barn"
canonical: "https://agentbarn.dev/recipes/documentation-agent/platform"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Turns merged pull requests and linked Jira work into Confluence updates, changelog entries, and a weekly digest. Set it up on Slack or Telegram with Agent Barn."
tags: [Knowledge operations, AI agents, workflow automation]
categories: [Recipes]
---

# Documentation Agent recipe for Slack and Telegram

A documentation-focused teammate that connects approved engineering changes and their Jira context to useful, traceable updates for the wider team.

## Choose a platform

### Slack

**Shared with the engineering team.** Posts documentation updates and the weekly digest into a channel, so reviewers can catch a wrong page or a missed change in the thread.

Choose when several people read, correct, or act on the documentation the agent produces.

### Telegram

**Owned by one maintainer.** Sends the same updates to a single chat, so one person confirms what gets written to Confluence.

Choose when one maintainer owns the docs and no one else needs to see each update.

## Recipe overview

- Category: Knowledge operations
- Tools: GitHub or Bitbucket + Jira + Confluence + Slack
- Trigger: A pull request is merged or a scheduled digest is due.

## Workflow

1. **Detect change:** Read the merged pull request and linked Jira context.
2. **Draft update:** Prepare a Confluence update or changelog entry.
3. **Check scope:** Keep the update within configured sources and policies.
4. **Share digest:** Post the prepared summary to the allowed Slack channel.

## Initial setup

1. **Template:** Documentation agent instructions and output format.
2. **Skills:** GitHub or Bitbucket plus Jira and Confluence access.
3. **Channels:** A permitted Slack channel for digests and questions.

## Integrations

### GitHub or Bitbucket

Read merged pull requests, diffs, labels, and linked engineering context.

- Requirement: choose-one
- Credential: A GitHub App or Bitbucket access token scoped to the repositories this recipe documents.

#### Permissions

- Repository metadata: read
- Pull requests and diffs: read
- Comments: write only if the workflow posts review notes

#### Setup

1. Choose the provider that owns the source repositories.
2. Limit installation or token access to the repositories in scope.
3. Subscribe only to merged pull-request events and any explicitly required update events.

### Jira and Confluence

Read linked Jira work and create or update documentation and changelog content in approved Confluence spaces.

- Requirement: required
- Credential: One Atlassian account email and site URL, with an API credential verified for the required Jira and Confluence operations.

#### Permissions

- Jira projects and linked issues: read
- Confluence target spaces: view
- Confluence pages: add or update where required
- Comments: add only if the recipe uses review comments

#### Setup

1. Identify the Jira projects referenced by the source repositories.
2. Identify the destination Confluence spaces and page hierarchy.
3. Use an account whose Jira and Confluence access is limited to those locations.
4. Validate Jira reads and Confluence writes in non-production test locations.

## Human review

Review generated documentation before treating it as the final record of a product or engineering decision.