On a schedule

Get a morning list of open Figma comments

Each weekday you start with every unresolved comment on your files, grouped by file.

Runs: On a schedule
Apps: Figma
AI: Not needed
Access: file_comments:read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 9am, email me all unresolved comments on my Figma files 'Checkout redesign' and 'Mobile app', grouped by file with links.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Design reviews in Figma happen in comments: a developer asks whether the button needs a hover state, a product manager flags a mismatch with the brief, a stakeholder adds a note on the pricing page. Comments are marked resolved when handled, but unresolved ones scatter across several files and nobody opens them all. Items get forgotten, then show up in a release as a bug that was pointed out three weeks earlier.

Each morning, ClickRuntime walks through the files you list, fetches each file's comments, keeps those that have not been resolved, and emails them grouped by file with the author, the text and a link to the exact spot. It shows what is still open today. A short list beats a vague sense that something is still open.

Design leads and solo designers with several active files get the most from the daily count.

What you get out of it

Close the loop on every review note
A visible daily list means a developer's question gets an answer instead of being buried. Resolving comments promptly keeps handoffs from stalling at the last step. That is far cheaper than fixing a shipped screen after launch.
Avoid rework from forgotten feedback
Feedback ignored in a file can become a bug in production. Seeing it listed every day reduces the chance that a requested change is missed until the work has been built.
See the workload before standup
Grouping by file shows where the pending feedback is concentrated. A lead can assign the heaviest file to the right person at the morning meeting instead of finding out on Friday.
Keep stakeholders accountable
When a manager adds a comment and it stays unresolved, it appears each morning. People notice open requests tied to their files, and the review process moves instead of waiting for someone to look.
Reduce time hunting through files
One email replaces opening each file and scrolling the comments panel. Even with four active files, that saves a few minutes daily and removes the tedious checking designers dislike. Fewer clicks also mean the habit actually survives busy weeks.

How it works

What happens, step by step

Every weekday at 9am, ClickRuntime reads the comments on each Figma file on your list.
It keeps only the ones nobody has resolved yet.
You get one email grouped by file, with who wrote each comment, what it says and a link.

Before it runs live

Connect Figma

What you get

RunsOn a schedule

Get a morning list of open Figma commentstoday, 9:00Succeeded

Email · 6 unresolved Figma commentsCheckout redesign (4 open) - Priya: Button label should say "Pay now" https://www.figma.com/design/a1B2c3D4e5F6g7?comment-id=1234567

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

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

Run it at a different time, more or less often, or only on weekdays
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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

daily_digest_of_unresolved_comments.pyexample

from clickruntime import on_trigger, notify, http, credentials

FILES = {"Checkout redesign": "a1B2c3D4e5F6g7", "Mobile app": "h8I9j0K1l2M3n4"}

@on_trigger
def run(event):
    headers = {"Authorization": "Bearer " + credentials.connection("figma", "main")}
    sections, total = [], 0
    for name, key in FILES.items():
        comments = http.get(f"https://api.figma.com/v1/files/{key}/comments", headers=headers).json()["comments"]
        open_ = [c for c in comments if not c.get("resolved_at") and not c.get("parent_id")]
        total += len(open_)
        lines = [f"- {c['user']['handle']}: {c['message'][:150]}\n  https://www.figma.com/design/{key}?comment-id={c['id']}" for c in open_]
        sections.append(f"{name} ({len(open_)} open)\n" + "\n".join(lines))
    notify.email_me(f"{total} unresolved Figma comments", "\n\n".join(sections))
    return {"unresolved": total}

FAQ

Common questions

Which files does it check?

The ones you list, by file key. Figma does not offer a single call for all comments in a team, so you name the files that matter, and you can add or remove them at any time as projects start and end.

Does a reply to a comment count as unresolved?

Replies belong to a thread, and the thread's resolved status decides whether it appears. If the original comment is open, the thread is listed. Once someone marks the thread resolved in Figma, it drops from the next morning's email. Ask the file owner if a link is denied.

Do I need edit access to the files?

Reading comments only needs access to view the file, using the Figma token connected to ClickRuntime. The token is stored as a secret. Files that the token owner cannot open will not return comments. Ask the file owner for access.

What permissions does it need?

file_comments:read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule