← Change platform

Selected path Telegram bot

Set up Documentation Agent in Telegram.

Create the bot, configure the agent, connect the recipe's skills, and verify the complete Telegram path.

01
TELEGRAM // BOTFATHER

Create the Telegram bot.

Use Telegram's verified BotFather account. The display name is editable later; the username is the permanent public handle.

Open BotFather
  1. 01.1

    Open the verified @BotFather account.

    Open t.me/BotFather ↗, confirm the verification badge, and send /start.

    Telegram BotFather command list with the newbot command highlighted
    Send /newbot to begin.
  2. 01.2

    Send /newbot and choose the identity.

    DISPLAY NAME

    Documentation Agent

    USERNAME

    AgentBarnDocumentationBot

    The username must be 5–32 characters, use Latin letters, numbers, or underscores, and end in bot. Choose it carefully because BotFather does not let you change it later.

  3. 01.3

    Copy the generated token.

    BotFather returns the bot link and an HTTP API token. Copy it for the next step. The token is fully blurred in this reference.

    Telegram BotFather bot creation conversation with the complete bot token blurred
    1 // Start creation. 2 // Display name. 3 // Username ending in bot. 4 // Copy the token.
  4. 01.4

    Add the bot description.

    In BotFather, set the description or about text to the recipe summary below so users know what the bot does before they start it.

    SUGGESTED

    Turns merged pull requests and linked Jira work into Confluence updates, changelog entries, and a weekly digest.

02
AGENT BARN // CREDENTIAL

Connect the bot token.

Enter the token from BotFather in the Telegram credential.

  1. 02.1

    Open the Telegram bot-token credential.

    Choose the Telegram integration for Documentation Agent, then select its Bot token field.

  2. 02.2

    Paste the bot token.

    A Telegram token resembles 123456:ABC-DEF…. Paste the complete value into the Bot token field.

    SOURCE@BotFather
    FIELDBot token
    ACTIONPaste and save
  3. 02.3

    Save and verify the bot identity.

    Agent Barn should resolve the bot username returned by Telegram. Stop if the resolved username differs from @AgentBarnDocumentationBot or the bot you selected in BotFather.

03
AGENT BARN // AGENT SETTINGS

Configure the Telegram agent.

Set the identity, model, approval behavior, and response style before connecting external skills.

  1. 03.1
    IDENTITY

    Name the teammate.

    OPERATIONAL NAME

    AgentBarn_Recipe

    Shown in Agent Barn.

    HUMAN NAME

    Aria

    Easy to recognize in conversation.

  2. 03.2
    MODEL

    Select the model.

    Use the model available for this agent and test it with a representative task from Documentation Agent.

  3. 03.3
    COMMAND APPROVAL

    Choose when commands need confirmation.

    Command approval options: Auto, Manual, and Off
    Available command approval options.
    START HERE

    Auto

    Runs low-risk commands automatically.

    CONFIRM EACH COMMAND

    Manual

    Asks before every command.

    NO PROMPTS

    Off

    Runs without approval prompts.

  4. 03.4
    VERBOSITY

    Choose the response detail.

    Verbosity options: Verbose and Concise
    Available response-detail options.
    SHOW EACH STEP

    Verbose

    Explains progress while working.

    FINAL ANSWER

    Concise

    Returns the result without step narration.

  5. 03.5

    Configure the recipe trigger and workflow.

    Trigger: A pull request is merged or a scheduled digest is due.

    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.

  6. 03.6

    Apply the recipe requirements and review rule.

    Template

    Documentation agent instructions and output format.

    Skills

    GitHub or Bitbucket plus Jira and Confluence access.

    Channels

    A permitted Slack channel for digests and questions.

04
TELEGRAM // CHAT ACCESS

Choose where the agent can respond.

Set Telegram delivery and Agent Barn chat rules together.

  1. 04.1

    Start private chats.

    Each user opens t.me/AgentBarnDocumentationBot and presses Start. Telegram bots cannot initiate a private conversation, so every permitted user must do this first.

  2. 04.2

    Choose the channel-access rule.

    Channel access options: Allowlist and Open
    Choose Allowlist or Open.
    SELECTED CHATS

    Allowlist

    Respond only in chats you add.

    ALL REACHABLE CHATS

    Open

    Respond anywhere the bot is present.

  3. 04.3

    Choose the direct-message rule.

    Direct message options: Off, Allowlist, and Open
    Choose Off, Allowlist, or Open.
    NO PRIVATE CHATS

    Off

    Ignore direct messages.

    SELECTED PEOPLE

    Allowlist

    Reply only to approved users.

    ANY USER

    Open

    Reply to anyone who starts the bot.

  4. 04.4

    Choose Group Privacy in BotFather.

    COMMANDS AND REPLIES

    Keep enabled

    Best when users address the bot directly.

    EVERY GROUP MESSAGE

    Turn off

    Use only when the recipe must read the full group conversation.

    To change it, open /mybots → select the bot → Bot Settings → Group Privacy. Add the bot to the group again after changing this setting.

  5. 04.5

    Add the intended chats.

    Add the bot to each permitted group, then add every permitted user or group to the Agent Barn allowlist when Allowlist is selected. Grant group administrator access only when the configured workflow requires messages that Group Privacy would otherwise hide.

05
AGENT BARN // RECIPE SKILLS

Connect the skills for Documentation Agent.

This section is generated from the integrations required by the selected recipe.

CHOOSE ONE

GitHub or Bitbucket

source control

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

Credential
A GitHub App or Bitbucket access token scoped to the repositories this recipe documents.
Access
Repository metadata: read · Pull requests and diffs: read · Comments: write only if the workflow posts review notes
  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.
REQUIRED

Jira and Confluence

atlassian

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

Credential
One Atlassian account email and site URL, with an API credential verified for the required Jira and Confluence operations.
Access
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
  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.
  1. 05.1

    Select the required skills.

    Keep skills marked required. For a “choose one” card, select the provider your team uses.

  2. 05.2

    Choose the connection method.

    NEW CONNECTION

    Enter credentials

    Connect an account now.

    CONNECTED ACCOUNT

    Use shared credential

    Select an account already available in Agent Barn.

  3. 05.A1

    Atlassian // Copy the site URL.

    Use the site origin, such as https://aai-labs.atlassian.net. Do not include a Jira project or Confluence space path.

    Atlassian browser address showing the site origin
    Copy only the site origin.
  4. 05.A2

    Atlassian // Open API tokens.

    Open the profile menu, choose Account settings → Security → Create and manage API tokens.

    Atlassian profile menu with Account settings
    1 // Account settings.
    Atlassian Account navigation with Security selected
    2 // Security.
    Atlassian Security page API tokens section
    3 // Create and manage API tokens.
  5. 05.A3

    Atlassian // Choose the matching token type.

    Select a standard or scoped token, then choose the same Authentication Type in Agent Barn.

    Atlassian API Tokens page showing standard and scoped token actions
    Choose standard or scoped.
  6. 05.A4

    Atlassian // Create and copy the token.

    Name it AgentBarn_Recipe, choose an expiration date, create it, and copy it.

    Atlassian Create an API token dialog
    Name, expiration, Create.
    Atlassian Copy your API token dialog
    Copy the token.
  7. 05.A5

    Atlassian // Complete the credential.

    SITE URL

    Atlassian site origin.

    AUTHENTICATION TYPE

    Match the token type.

    EMAIL

    Atlassian account email.

    API TOKEN

    Paste the copied token.

    The same Atlassian credential can connect Jira and Confluence when the account can access both.

  8. 05.A6

    Atlassian // Validate the product boundary.

    Test one permitted Jira project or Confluence space for every connected product, then confirm a location outside the configured boundary remains unavailable.

  9. 05.S1

    Source control // Choose GitHub or Bitbucket.

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

  10. 05.G1

    GitHub // Create a Classic PAT.

    Open GitHub Personal access tokens ↗, select Tokens (classic) → Generate new token, add a note, and choose an expiration date.

  11. 05.G2

    GitHub // Select the scopes.

    REPO

    Repository access.

    READ:ORG

    Organization membership.

    READ:USER

    User profile data.

  12. 05.G3

    GitHub // Copy and enter the token.

    GitHub Classic PAT success row with the token blurred and copy control visible
    Copy the generated value; the token is blurred here.
    GitHub repository header showing owner and repository
    Owner / Org appears before the slash.
    PERSONAL ACCESS TOKEN

    Paste the copied value.

    OWNER / ORG

    Value before the slash.

    REPOSITORIES

    Add each permitted repository.

  13. 05.G4

    GitHub // Validate the repository boundary.

    The Classic PAT repo scope is broad. Test one repository in the configured list and confirm a repository outside the configured list remains unavailable.

  14. 05.B1

    Bitbucket // Record the workspace ID.

    In bitbucket.org/agentbarn/workspace/overview, agentbarn is the workspace ID.

  15. 05.B2

    Bitbucket // Create the API token.

    Open Account settings → Security → Create and manage API tokens. Choose Create API token with scopes, select Bitbucket, and add the required scopes.

    READ:USER

    Read the account.

    READ:WORKSPACE

    Read the workspace.

    READ:REPOSITORY

    Read repository content.

    READ:PULLREQUEST

    Read pull requests.

  16. 05.B3

    Bitbucket // Complete the credential.

    WORKSPACE

    Workspace ID.

    REPOSITORIES

    Permitted repository names.

    EMAIL

    Atlassian account email.

    API TOKEN

    Bitbucket-scoped token.

  17. 05.B4

    Bitbucket // Validate the repository boundary.

    Test one repository in the configured list and confirm a repository outside the configured list remains unavailable; verify pull-request write access only when this recipe posts review comments.

  18. 05.Z

    Test every connected skill.

    Run one expected action for each selected integration before launch.

06
LAUNCH // COMPLETE PATH

Verify the Telegram recipe.

Test the bot, chat rules, and connected integrations together.

  1. 01

    The token connects to @AgentBarnDocumentationBot.

  2. 02

    A permitted private chat or group receives a response.

  3. 03

    A chat outside the selected access rule receives no response.

  4. 04

    Group Privacy matches the recipe's message needs.

  5. 05

    Each required skill completes one representative action.

  6. 06

    The approval mode and response detail are correct.

  7. 07

    The configured trigger runs: A pull request is merged or a scheduled digest is due.

  8. 08

    The result follows Detect change → Draft update → Check scope → Share digest.

  9. 09

    The review rule is applied: Review generated documentation before treating it as the final record of a product or engineering decision.

RECIPE PATH COMPLETE

Documentation Agent is ready for a controlled pilot.

Start with a narrow audience and reversible work, then widen access after observing representative tasks.

Return to recipes →