Hand off Builder.io assets through Telegram
Put a useful asset in the right Telegram conversation as part of your existing Builder.io handoff.
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
Finding and forwarding an asset by hand adds another step between preparing content and getting it to collaborators.
- Reduce manual file forwarding during content handoffs.
- Keep the asset and its discussion in one Telegram chat.
- Include context supplied with the webhook in the handoff.
Setup
Build it in a few focused steps.
- 1Connect Builder.io and Telegram once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the handoff.
- 3In one instruction, ask Notis to send the supplied asset file or accessible document reference to your Telegram chat with a short context note.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real asset that the automation can access.
Questions about this workflow
Can this send any Builder.io asset by itself?
The webhook must supply the file or an accessible document reference that Notis can use. The workflow cannot assume access to asset data that is not provided.
Can I include a note with the document?
Yes. Ask Notis to include a short handoff note based on context supplied with the webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Builder.io to Telegram. A trigger fires from one place; an action lands in another.
Builder.io 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.
Builder.io 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.