# Post unresolved Figma comments to Slack every weekday

> Every weekday afternoon, we send designers a Slack recap of every open Figma comment they still need to address, grouped by file with deep links.

- Workflow type: code
- Services: Figma, Slack Bot
- Categories: Product
- Published: 2026-07-17

## What it does

- Reads every Figma file on a list you configure and pulls the open comments left on each one
- Groups the results by file with the commenter, a preview of the message, how old it is, and a deep link that jumps straight to the pinned spot
- Posts one tidy Slack message to the channel you pick so designers see outstanding feedback before they log off
- If every file is clean, sends a single "No open comments today" note instead of skipping the run

## What you'll need

- A Figma account with access to the files you want checked
- A Slack workspace and the channel where the digest should land
- The list of Figma file URLs (or file keys) you want the digest to cover

## Prompt

Every weekday at 5pm, post a plain digest of unresolved Figma comments to Slack so designers see outstanding feedback before they log off. Use a cron trigger.

Configuration inputs the workflow should accept: the list of Figma file keys or URLs to check, the Slack channel to post the digest to, and the cron schedule (default: weekdays at 5pm in the workspace timezone).

For each Figma file in the configured list, call Figma's Get Comments operation and walk the pagination. Figma returns pagination.next_page as a ready-to-fetch URL on comment endpoints, so follow next_page until it is null so no comments are missed. After all pages are collected, filter each file's results to comments where resolved_at is null.

Group the surviving comments by file. For each file, render a section with the file name as a bold header (Slack mrkdwn, so *File name*) linking to the file, followed by a bullet list. Each bullet shows the commenter's handle (user.handle), a one-line preview of the comment message (first ~80 characters on a single line, ellipsized if truncated), the age of the comment in whole days computed from created_at, and a deep-link into the file at the pinned node. The deep-link format is https://www.figma.com/design/{file_key}/?node-id={hyphenated-node-id} — Figma's API returns node ids with colons (e.g. 1:2) and the URL expects hyphens (e.g. 1-2), so convert colons to hyphens before building the URL. If a comment has no pinned node, link to the file root.

Send the whole digest as ONE Slack Bot Send a Message to the configured channel — not one message per file. If a file has zero unresolved comments, omit that file from the digest entirely. If every configured file is clean, send a single "No open comments today" message instead of sending nothing.

Cap the digest at ~50 comments total across all files to keep the Slack message readable. If the combined count exceeds the cap, truncate the tail and append an "and 12 more" overflow line (with the real remaining count) at the bottom of the message so nothing is silently dropped.

This is a deterministic template — same operations, same format, every run — so build it as a code workflow, not an agent. The only two integrations involved are Figma (Get Comments) and Slack Bot (Send a Message).

## How to customize

- Change the schedule (time of day, days of the week, or timezone)
- Add or remove files from the watch list at any time
- Point the digest at a different Slack channel or a private thread

## FAQ

### Does this only include comments I made?

No. It pulls every open comment on each file, no matter who wrote it, so the whole design team sees what is still outstanding.

### Will resolved comments show up?

No. The digest filters to comments that still need attention and skips anything that has been marked resolved.

### What happens if a file has no open comments?

Files with a clean slate are left out of the digest so the message stays short. If every file is clean, you get a single "No open comments today" note instead of nothing.

### Can I point this at FigJam or Slides files?

This is built for Figma Design files. FigJam boards and Slides decks use a different comment surface and are not part of the standard digest.

### What if a file has dozens of open comments?

The digest caps the message at around 50 comments to keep it readable, and adds an "and X more" overflow line at the bottom so nothing is silently dropped.

Use this prompt in General Input: https://www.generalinput.com/prompts/post-unresolved-figma-comments-to-slack-every-weekday