A PM drops a Figma link into #design-review at 2pm on a Tuesday. Three people click it, two leave comments inside Figma, one types feedback directly in the Slack thread. By end of day there are four comment threads - two in Figma, one in Slack, one in a follow-up DM - and nobody has a complete picture of what was decided.
That is not a discipline problem. It is a structural one, and it happens on almost every team that uses the Figma Slack integration without thinking carefully about what the integration actually does.
What the Figma Slack integration actually does - and doesn't
The Figma integration for Slack lets you stay on top of updates to files, projects, and teams. With it connected, you get a single feed of Figma comments you've been mentioned in, timely feedback from teammates and stakeholders, and channel-level subscriptions for specific projects.
That sounds like a lot. In practice, it is narrower. The integration is free on all Figma plans, but it does not give Slack users edit access to your designs - it only sends notifications and renders link previews. What it cannot do: summarise the comment thread, flag which feedback is blocking, track whether anything was resolved, or write a decision back into the channel when a designer marks a comment as resolved in Figma.
Figma notifications in Slack come in two types: default notifications and channel subscriptions. Default notifications appear in your Figma app channel and include comments you've been mentioned in and invitations to files. With channel subscriptions, you can customise Slack channels to receive notifications on specific files, projects, and teams - covering comments, mentions, branching updates, new files, and new projects.
Here is the number almost no one knows: notifications from comments are grouped and sent every 30 minutes. Teams that schedule async design review rounds and expect near-real-time pings are working with a built-in half-hour delay they have never accounted for. A two-hour review window can silently compress to 90 minutes of actual response time.
The other friction point is notification scope. In companies divided into teams where Figma projects correspond to each team, users currently cannot select which projects to receive notifications from, resulting in comment notifications - including via the Figma plugin for Slack - arriving from entirely unrelated projects. There is no per-project mute without removing yourself from the project entirely.
Where design feedback splits across Figma and Slack
The deeper problem is a split-brain feedback loop. Paste a Figma frame link into Slack and it drops the link and expands to show a preview, with the file name and thumbnail displayed below the message. That preview makes it easy for a PM or engineer to react directly in Slack - which is exactly where things go sideways.
Once someone types feedback in the Slack thread instead of inside Figma, the canonical comment record is broken. Decisions now live in two places. When there are multiple sources of truth that don't clearly map to each other, you pay a toggle tax - time, energy, and context lost switching between different artifacts. This can be expensive and exhausting.
Review day arrives and the feedback sounds maddeningly vague: "This isn't quite what we meant." The file changed hands. The reasoning behind it did not. That gap between the pixels and the intent behind them is where most design quality erodes - not in Figma, but in the handoff conversation that never got properly written down.
Sending Slack messages with individual design notes throughout the build is disruptive. A structured approach - where engineering builds to staging, the designer reviews and compiles all feedback into a single pass - beats twenty asynchronous messages. The integration as-built makes the disruptive pattern easier and the structured one harder.
Routing Figma feedback without losing the thread
A few practices actually help:
One channel per project, not one channel for all design. Create a dedicated design channel per project and route Figma notifications there instead of cluttering general channels. This keeps the notification stream meaningful rather than a firehose.
Paste frame links, not file links. Use Figma link previews to replace screenshots - paste a frame link and Slack renders a live thumbnail automatically. File-level links produce lower-fidelity previews and make it harder to anchor feedback to a specific screen.
@-mention inside Figma, not just in Slack. Mention specific teammates in Figma comments so the Slack notification tags the right person. A Slack message that says "check the login flow" without a frame link or @-mention in Figma creates a lookup task, not a review task.
Label feedback by urgency before posting. Separate blocking from non-blocking. Label feedback clearly: "This button state is wrong - blocking" vs. "I'd prefer 2px more spacing here - non-blocking, can batch." Engineers who can't tell what's urgent either do everything inefficiently or deprioritise everything suboptimally.
Pin the approved frame link. Pin important design updates in Slack so developers can find the latest approved version without searching.
None of these practices are enforced by the integration. They are norms a team has to decide and maintain.
Beagle in action#product-design, 3:47pmWhen the integration alone isn't enough
The Figma Slack integration solves one thing cleanly: it gets Figma comments into Slack so you don't have to keep Figma open to stay aware. What it does not solve is the post-review moment - writing up what was decided, who owns the next action, and whether the file is ready for handoff.
Design to dev handoff problems start before the handoff meeting. They start the moment a team treats a Figma file as the product, instead of treating it as one artifact in a larger transfer of intent. A Slack notification that a comment was left does nothing to transfer that intent.
The gap is predictable: designer marks comments resolved in Figma, developer reads resolved count as "approved to build," but the Slack thread where three people weighed in on the CTA copy never got reconciled with what the designer actually changed. A week later someone asks in #engineering why the button says "Continue" instead of "Next."
That summary step - the one that actually closes the loop - is exactly what the native integration leaves out. It takes a minute to write by hand. On a team running three active design projects, it happens inconsistently, which means it effectively doesn't happen.
Figma Slack integration design review: common questions
Does the Figma Slack integration work in real time?
No. Figma notifications from comments are grouped and sent every 30 minutes. Teams expecting immediate pings during a live review session will miss feedback within that window. For synchronous review sessions, open Figma directly; reserve the Slack integration for async rounds where a half-hour lag is acceptable.
Can you filter Figma Slack notifications by project?
Not with granular per-project toggles via the native integration. With channel subscriptions, you can customise which Slack channels receive notifications on specific files, projects, and teams, covering comments, mentions, branching updates, new files, and new projects. The workaround is routing each project's notifications to a dedicated channel rather than filtering at the user level.
Why does design feedback end up split between Figma and Slack?
Because the Figma link preview in Slack makes it trivially easy to react in the thread. When there are multiple sources of truth that don't clearly map to each other, you pay a toggle tax - time, energy, and context lost switching between different artifacts. The only reliable fix is a team norm: feedback on design decisions goes inside Figma as a comment; reactions and scheduling go in Slack.
What does the Figma Slack integration not support?
The integration is free on all Figma plans, but it does not give Slack users edit access to designs - it only sends notifications and renders link previews. It also does not: summarise resolved threads, notify Slack when a Figma comment is resolved, label feedback by priority, or write decision summaries. Those steps require a separate tool or a team norm.
How should a design team structure Slack channels for Figma work?
Create a dedicated design channel per project and route Figma notifications there instead of cluttering general channels.
Pair each project channel with a channel subscription scoped to that Figma project file. Keep a separate #design-general for process questions and tool discussion. This splits signal from noise without requiring anyone to manually filter.