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 NAMEEmail Reminder
USERNAMEAgentBarnReminderBotThe 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.
SUGGESTEDMonitors a mailbox, flags action-required messages, and posts priority pings to Slack.
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 Email Reminder, 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
@AgentBarnReminderBotor 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_Email
Shown in Agent Barn.
HUMAN NAME Nora
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 Email Reminder.
- 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 new message meets the configured mailbox and priority rules.
- 03.6
Apply the recipe requirements and review rule.
TemplatePriority rules, reminder tone, and escalation instructions.
OAuthRead-only Gmail access approved through Google sign-in.
ChannelsAllowed Slack channels or direct-message policies.
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/AgentBarnReminderBotand 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 Email Reminder.
This section is generated from the integrations required by the selected recipe.
Gmail
Read messages that match the configured mailbox and priority rules.
- Credential
- Google OAuth sign-in with gmail.readonly; no manual key is needed.
- Access
- Gmail OAuth: gmail.readonly · Modify, send, delete, contacts, and calendar: not requested
- Select Authenticate with Google and approve read-only Gmail access.
- Use a custom Google OAuth client only when the workspace requires its own application.
- Test with representative P1/P2 messages before enabling continuous monitoring.
- 05.1
Select the required skills.
Keep skills marked required. For a “choose one” card, select the provider your team uses.
- 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.
- 05.M1
Gmail // Authenticate with Google.
- Click Authenticate with Google.
- Choose the mailbox.
- Review the consent screen.
- Approve
gmail.readonly.

Gmail uses Google sign-in. - 05.M2
Gmail // Set mailbox filters.
Choose the labels, folders, senders, recipients, and priority rules that Email Reminder should monitor.
- 05.M3
Gmail // Keep the connection read-only.
Do not grant send, modify, or delete access. Use a custom Google OAuth client only when the workspace requires one.
- 05.M4
Gmail // Validate both sides of the filter.
Confirm one qualifying message creates a reminder and one excluded message does not appear in the agent's results.
- 05.Z
Test every connected skill.
Run one expected action for each selected integration before launch.
Verify the Telegram recipe.
Test the bot, chat rules, and connected integrations together.
- 01
The token connects to
@AgentBarnReminderBot. - 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 new message meets the configured mailbox and priority rules.
- 08
The result follows Watch inbox → Assess priority → Prepare ping → Follow up.
- 09
The review rule is applied: Use explicit mailbox filters and escalation rules; do not give an agent unrestricted access to sensitive mail.
Email Reminder is ready for a controlled pilot.
Start with a narrow audience and reversible work, then widen access after observing representative tasks.
Return to recipes →