Every 5–10 minutes
Post new Figma comments to Slack
Feedback left on your file shows up in a channel with the comment text and a link back to it.
- Runs
- Every 5–10 minutes
- Apps
- Figma
- AI
- Not needed
- Access
- file_comments:read
Send this to your assistant
Create a ClickRuntime automation: check my Figma file 'Checkout redesign' every 5 minutes and post each new comment to #design-feedback in Slack with who wrote it, the text and a link.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Figma comments are the quickest way to give design feedback, and also the easiest way to lose it. A developer asks about spacing at 3 p.m., the designer is in another file, and the question sits until the next time someone opens that frame. Meanwhile the sprint continues, the build uses a guess, and the answer arrives too late to prevent the rework. Waiting costs rework and missed sprint goals.
Every five to ten minutes, ClickRuntime fetches the comments on a file, compares them with the comment IDs it has stored, and posts anything new to Slack with the author, the comment text and a link back to the exact place on the canvas. Old comments are never repeated.
It is particularly useful for design teams working with developers or clients across time zones.
What you get out of it
Answer questions in minutes
A comment in Slack gets a reply while the person is still working on the task. Fast answers keep developers moving instead of waiting on a design decision. One quick answer can save a day of building the wrong thing. Chat becomes the one place where design feedback appears.
Stay in Slack instead of Figma
Designers who live in chat see feedback where they already work. They do not need email notifications or an open Figma tab to avoid missing something. Fewer missed notifications, and no extra tab to keep open.
Give clients visible responsiveness
When a client leaves a note on a prototype and gets an answer the same hour, trust in the process grows. Quick turnaround is often what clients remember about an agency. A single answer then serves several people at once, whoever happened to ask.
Share feedback with the whole team
A channel message lets teammates see comments about shared components. Duplicate questions are avoided because the answer is visible to everyone. That separation matters when notification volume is already high and important mail gets lost.
Avoid reading every email
Figma's own notification emails can pile up and get muted. A dedicated channel post per comment keeps the signal separate from the rest of your inbox. Your inbox stays calmer too.
How it works
What happens, step by step
Every 5 to 10 minutes, ClickRuntime checks your Figma file for comments.
It compares them with the ones it has already seen, so each comment is sent once.
Each new comment is posted to your Slack channel with who wrote it, what they said and a link straight to it.
Before it runs live
- Connect Figma
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Figma steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, report_fetched, state, notify, http, credentials
FILE_KEY = "a1B2c3D4e5F6g7" # your 'Checkout redesign' file
@on_trigger
def run(event):
comments = http.get(f"https://api.figma.com/v1/files/{FILE_KEY}/comments", headers={
"Authorization": "Bearer " + credentials.connection("figma", "main")}).json()["comments"]
seen = set(state.get("seen") or [])
new = [c for c in comments if c["id"] not in seen]
report_fetched(len(new))
if not new:
return {"summary": "No new comments"}
for c in sorted(new, key=lambda c: c["created_at"]):
notify.slack(f"{c['user']['handle']}: {c['message']}\nhttps://www.figma.com/design/{FILE_KEY}?comment-id={c['id']}", channel="#design-feedback")
state.set("seen", list(seen | {c["id"] for c in new}))
return {"posted": len(new)}FAQ
Common questions
Will it post replies as well as new threads?
How does it avoid sending the same comment twice?
Can I mute a noisy file?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Announce new versions of your design system
When someone saves a named version, the team sees its label and description without asking.
See how it worksGet told when a file is added to a Figma project
A new file in the project you watch is posted to Slack with its name and link.
See how it worksGet a morning list of open Figma comments
Each weekday you start with every unresolved comment on your files, grouped by file.
See how it worksKeep exploring
Set up “Post new Figma comments to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.