Keep design feedback connected to the Figma file
Send feedback in Telegram and let Notis place a clear comment in the relevant Figma file, so the next review starts with the context intact.
Trigger
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.
Action
Add a comment to a file
Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.
Why this helps
Feedback scattered across busy chats is easy to forget when it is time to revise a design.
- Preserves feedback where design work happens.
- Reduces the effort of copying chat notes into a file.
- Keeps a review trail together with the design.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Figma to Notis once through the portal.
- 2Create an automation in the portal or tell Notis what outcome you want in plain language.
- 3In one instruction, ask Notis to turn incoming design feedback into a comment on the relevant Figma file.
- 4Choose the Telegram new message trigger and a channel for run reports.
- 5Test with one real feedback message and check the comment in Figma.
Questions about this workflow
Does every Telegram message become a Figma comment?
Describe in the instruction which messages are design feedback and how Notis should identify the relevant Figma file.
Can the comment point to a specific part of a design?
Ask Notis to include a comment region when the message provides enough location context; otherwise it can post a general file comment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Figma. A trigger fires from one place; an action lands in another.
Telegram triggers
Figma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a file
Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a reaction to a comment
Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
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.
Create a webhook
Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Create dev resources
Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Create, modify, or delete variables
Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Delete a comment
Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Delete a reaction
Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
Delete a webhook
Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.
Connect any two apps with Notis in the middle.
Telegram and Figma, 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 Figma.