← Change platform

Selected path Telegram bot

Set up Scrum Master 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

    Scrum Master

    USERNAME

    AgentBarnScrumBot

    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

    Runs sprint ceremonies, tracks blockers, and keeps the team on cadence in Slack.

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 Scrum Master, 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 @AgentBarnScrumBot 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_Scrum_Master

    Shown in Agent Barn.

    HUMAN NAME

    Milo

    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 Scrum Master.

  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 scheduled ceremony, configured work-item change, or stand-up window.

    1. Collect updates. Ask for stand-up updates or read configured project activity.

    2. Track blockers. Identify pending work and blockers from the available context.

    3. Prepare summary. Create a concise update for the team’s agreed cadence.

    4. Keep moving. Post reminders and the sprint summary in Slack.

  6. 03.6

    Apply the recipe requirements and review rule.

    Template

    Ceremony cadence, question format, and summary structure.

    Skills

    Jira access for the relevant project or sprint information.

    Policies

    The Slack channels and direct-message rules for the team.

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/AgentBarnScrumBot 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 Scrum Master.

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

REQUIRED

Jira

atlassian

Read sprint, issue, assignee, status, and blocker information for the configured team.

Credential
An Atlassian account email, site URL, and scoped or non-scoped API token.
Access
Projects and boards: read · Issues and sprint state: read · Comments or updates: omit unless the team explicitly enables them
  1. Select the board, project, and active sprint sources.
  2. Keep write actions disabled for the initial coordination pilot.
  3. Validate summaries against the board before automating reminders.
  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_Scrum_Master, 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.

  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.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 @AgentBarnScrumBot.

  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 scheduled ceremony, configured work-item change, or stand-up window.

  8. 08

    The result follows Collect updates → Track blockers → Prepare summary → Keep moving.

  9. 09

    The review rule is applied: Keep the agent focused on coordination and summaries; the team retains ownership of commitments, priorities, and delivery decisions.

RECIPE PATH COMPLETE

Scrum Master is ready for a controlled pilot.

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

Return to recipes →