Turn scheduled BrowserAct findings into a Telegram poll
Bring the next decision to your team with a poll grounded in browser findings you provide.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Poll
Send a native poll to a telegram chat using the bot api.
Why this helps
Useful research can stall when the team has to read results and coordinate a decision separately.
- Put a clear decision in front of a Telegram group
- Reduce back and forth after browser research
- Use a recurring schedule to prompt timely review
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and Telegram once in the Notis portal.
- 2Create an automation by describing the decision workflow, either in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to use BrowserAct findings supplied to it to draft a focused poll and send it to Telegram.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real set of findings and check that the poll options reflect the decision.
Questions about this workflow
Will the schedule run BrowserAct automatically?
The listed trigger is a Notis schedule. BrowserAct has no source trigger events listed here, so provide the BrowserAct findings to Notis through an available process before or during the scheduled run.
Can Notis know which findings are current?
Only if current findings are supplied to the automation. The schedule itself does not provide BrowserAct data or a baseline.
What makes a good poll instruction?
Describe the decision the team needs to make and ask Notis to create concise, distinct options grounded in the supplied findings.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BrowserAct to Telegram. A trigger fires from one place; an action lands in another.
BrowserAct triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
BrowserAct and Telegram, 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 Telegram.