Send BrowserAct findings to Telegram as a document
Keep useful browser research in a file you can find and share from Telegram.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Document
Send general files (documents) to a telegram chat using the bot api.
Why this helps
Important browser research is easy to lose among run logs or scattered notes.
- Keep run findings in a Telegram document
- Make useful results easier to share
- Avoid manually collecting browser output
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and Telegram once in the Notis portal.
- 2Create an automation by describing the result you want, either in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to organize returned BrowserAct findings into a document and send it to Telegram.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real run that returns findings suitable for a document.
Questions about this workflow
Does BrowserAct provide the document content automatically?
The automation can use information returned by the BrowserAct run. Any content not returned by the run must be supplied separately.
How does the webhook get called?
A webhook trigger starts when it receives an HTTP request. Arrange for the relevant BrowserAct workflow or surrounding process to call that webhook.
Can I send every run as a file?
You can describe that outcome in your instruction, provided the run returns content that can usefully be organized as a document.
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.