Create the Telegram bot.
Use Telegram's verified BotFather account. The display name is editable later; the username is the permanent public handle.
- 01.1
Open the verified @BotFather account.
Open t.me/BotFather ↗, confirm the verification badge, and send
/start.
Send /newbotto begin. - 01.2
Send
/newbotand choose the identity.DISPLAY NAMEGeneral Purpose
USERNAMEAgentBarnAssistantBotThe 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. - 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.

1 // Start creation. 2 // Display name. 3 // Username ending in bot. 4 // Copy the token. - 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.
SUGGESTEDA flexible starting template for a broad range of configured Slack tasks.
Connect the bot token.
Enter the token from BotFather in the Telegram credential.
- 02.1
Open the Telegram bot-token credential.
Choose the Telegram integration for General Purpose, then select its Bot token field.
- 02.2
Paste the bot token.
A Telegram token resembles
123456:ABC-DEF…. Paste the complete value into the Bot token field.SOURCE@BotFatherFIELDBot tokenACTIONPaste and save - 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
@AgentBarnAssistantBotor the bot you selected in BotFather.
Configure the Telegram agent.
Set the identity, model, approval behavior, and response style before connecting external skills.
- 03.1IDENTITY
Name the teammate.
OPERATIONAL NAME AgentBarn_General
Shown in Agent Barn.
HUMAN NAME Aria
Easy to recognize in conversation.
- 03.2MODEL
Select the model.
Use the model available for this agent and test it with a representative task from General Purpose.
- 03.3COMMAND APPROVAL
Choose when commands need confirmation.

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.
- 03.4VERBOSITY
Choose the response detail.

Available response-detail options. SHOW EACH STEP Verbose
Explains progress while working.
FINAL ANSWER Concise
Returns the result without step narration.
- 03.5
Configure the recipe trigger and workflow.
Trigger: A request arrives in an allowed Slack channel or direct message.
- 03.6
Apply the recipe requirements and review rule.
TemplateThe selected model, role, restrictions, and instructions.
SkillsOnly the capabilities needed for the intended workflow.
PoliciesExplicit channel allowlists and direct-message behavior.
Choose where the agent can respond.
Set Telegram delivery and Agent Barn chat rules together.
- 04.1
Start private chats.
Each user opens
t.me/AgentBarnAssistantBotand presses Start. Telegram bots cannot initiate a private conversation, so every permitted user must do this first. - 04.2
Choose the channel-access rule.

Choose Allowlist or Open. SELECTED CHATS Allowlist
Respond only in chats you add.
ALL REACHABLE CHATS Open
Respond anywhere the bot is present.
- 04.3
Choose the direct-message rule.

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.
- 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.
- 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.
Connect the skills for General Purpose.
This section is generated from the integrations required by the selected recipe.
Selected skills only
Add only the platforms required by the role you define for this agent.
- Credential
- A dedicated, least-privilege credential for each selected platform.
- Access
- No default integrations · Grant read before write where possible · Add one capability at a time and test it
- Write the role and success criteria before selecting tools.
- Connect the minimum useful skill set.
- Re-run representative tests whenever a new integration is added.
Select the skills this agent can use.
Select one or more skills to show their connection instructions.
Connect Jira.
- Copy the Atlassian site URL.
Use the site origin through
.atlassian.net. Do not include a project path.
Copy the site origin. - Open the API token manager.
Open Profile → Account settings → Security → Create and manage API tokens.

Account settings 
API token manager - Create the matching token type.
Choose standard or scoped, then select the same Authentication Type in Agent Barn. For a scoped token, include only the Jira API scopes required by the role.

Choose standard or scoped. - Complete the Jira credential.SITE URL
Atlassian site origin.
AUTHENTICATION TYPEMatch the token type.
EMAILAtlassian account email.
API TOKENCopied token value.
Grant only the Jira project and issue actions required by the general-purpose role.
- Validate the Jira boundary.
Test one permitted project and confirm a project outside the configured boundary remains unavailable.
Connect Confluence.
- Copy the Atlassian site URL.
Use the site origin through
.atlassian.net. Do not include a space or page path.
Copy the site origin. - Open Atlassian API tokens.
Open Profile → Account settings → Security → Create and manage API tokens.

Open the API token manager. - Create and copy the token.
Choose the token type used in Agent Barn, add a recognizable name and expiration, create it, and copy the value.

Name · expiration · create 
Copy the value. - Complete the Confluence credential.SITE URL
Atlassian site origin.
AUTHENTICATION TYPEMatch the token type.
EMAILAtlassian account email.
API TOKENCopied token value.
The same saved Atlassian credential can connect Jira and Confluence when the account and token cover both products.
- Validate the Confluence boundary.
Test one permitted space and confirm a space outside the configured boundary remains unavailable.
Connect GitHub with a Classic PAT.
- Open Personal access tokens.
Open github.com/settings/tokens ↗, choose Tokens (classic) → Generate new token, then add a note and expiration.
- Select the scopes.REPO
Repository access.
READ:ORGOrganization membership.
READ:USERUser profile data.
- Generate and copy the token.

The token is blurred; use the copy control. - Complete the GitHub credential.
Copy Owner / Org from the value before the slash and add every repository the agent may use.

Owner / Org appears before the slash. - Validate the GitHub boundary.
Test one permitted repository and confirm a repository outside the configured list remains unavailable.
Connect Bitbucket.
- Record the workspace ID.
Open the workspace. In
bitbucket.org/agentbarn/workspace/overview,agentbarnis the workspace ID. - Create a Bitbucket-scoped API token.
Open Profile → Account settings → Security → Create and manage API tokens. Choose Create API token with scopes, select Bitbucket, and continue to permissions.
- Select access.USER
Read the account.
WORKSPACERead the workspace.
REPOSITORYRead repository content.
PULL REQUESTSRead; add write only when the role posts comments.
- Complete the Bitbucket credential.WORKSPACE
Workspace ID.
REPOSITORIESPermitted repository names.
EMAILAtlassian account email.
API TOKENBitbucket-scoped value.
- Validate the Bitbucket boundary.
Test one permitted repository and confirm a repository outside the configured list remains unavailable.
Connect Gmail with Google OAuth.
- Click Authenticate with Google.
Choose the mailbox that the agent should read.
- Review and approve read-only access.
Approve
gmail.readonly. No manual key is required.
Google OAuth · gmail.readonly - Use a custom Google client only when required.
Keep the optional custom-client fields closed unless the workspace must supply and manage its own Google OAuth application.
- Set mailbox boundaries.
Choose the labels, folders, senders, recipients, and message types this general-purpose agent may inspect.
- Test the connection.
Confirm one included message is available and one excluded message remains outside the agent’s results.
- Define the role before selecting skills.
Write the tasks, inputs, outputs, and prohibited actions first.
- Test one skill at a time.
Connect the minimum access required, run a representative task, and confirm resources outside the selected boundary remain unavailable.
- Review every selected skill.
Confirm each connection uses the intended account and resources, then remove anything the defined role does not need.
Verify the Telegram recipe.
Test the bot, chat rules, and connected integrations together.
- 01
The token connects to
@AgentBarnAssistantBot. - 02
A permitted private chat or group receives a response.
- 03
A chat outside the selected access rule receives no response.
- 04
Group Privacy matches the recipe's message needs.
- 05
Each required skill completes one representative action.
- 06
The approval mode and response detail are correct.
- 07
The configured trigger runs: A request arrives in an allowed Slack channel or direct message.
- 08
The result follows Receive request → Apply role → Use skills → Return answer.
- 09
The review rule is applied: Start with the narrowest useful scope and add tools only when the workflow genuinely needs them.
General Purpose is ready for a controlled pilot.
Start with a narrow audience and reversible work, then widen access after observing representative tasks.
Return to recipes →