Connect Telegram to Botstar
When something happens in Telegram, Notis takes the next step in Botstar. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Telegram to Botstar
Carry Telegram support context into BotStar
When a Telegram message asks for help, update the active BotStar live chat profile with the relevant context so an agent can continue without asking the founder to repeat themselves.
Pass a Telegram support choice to BotStar
Use a tapped Telegram inline button as a clear signal to send the selected response data from an open BotStar webview back to its chatbot.
Refresh BotStar context when Telegram details change
When someone edits a Telegram message with corrected support details, update the active BotStar live chat profile with the revised context.
Use Telegram follow-up context with BotStar webview input
When a Telegram message supplies a requested follow-up detail, retrieve the relevant parameter from the BotStar webview so the chatbot flow can be interpreted with its existing context.
Retrieve BotStar app identity on a Telegram setup request
When a Telegram message requests a BotStar setup or troubleshooting check, retrieve the BotStar application ID needed when initializing or reinitializing its live chat widget.
Open BotStar live chat after a Telegram button request
Use a Telegram inline button as a clear request to open a BotStar live chat widget that has already been bootstrapped in livechat or popup mode.
Refresh BotStar widget after a Telegram configuration request
When a Telegram message requests a live chat configuration refresh, reinitialize the BotStar widget with the provided data to reset or update its configuration.
Retrieve BotStar app IDs for a published setup notice
When a Telegram channel publishes a BotStar widget setup notice, retrieve the app ID needed to initialize or reinitialize the live chat widget.
Refresh BotStar after a channel configuration update
When an authorized Telegram channel publishes a relevant widget configuration update, reinitialize the BotStar live chat widget with the provided data.
Supported Triggers and Actions
Notis builds workflows that link Telegram to Botstar. A trigger fires from one place; an action lands in another.
Telegram triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BotStar Application IDs
Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Livechat boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Close BotStar Livechat Widget
Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Livechat open
Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Livechat update
Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
Get BotStar Webview Parameter
Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Telegram and Botstar
Connect any two apps with Notis in the middle.
Telegram and Botstar, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botstar.