A designer marks three frames Ready for Dev at 4pm on a Tuesday. The engineering lead, who lives in Slack, hears nothing. They find out the next morning when the designer pings them manually. That two-frame, one-ping handoff is the most common design-to-engineering delay that no tool dashboard will ever measure.
This is the gap at the center of the Figma Slack integration. It handles a lot well. It just stops short of the moment that most directly affects shipping speed.
What the Figma Slack integration actually does
You can subscribe Slack channels to updates on specific Figma files, folders, and teams, and customize the frequency of notifications for each subscription. In practice, that covers two things most teams care about: someone leaves a comment, or someone mentions you directly in the file. Both land as a notification in your personal Figma app channel in Slack.
Figma admins who use the integration receive seat request notifications in Slack and can approve requests directly from Slack. That's a convenience, but it's not where the workflow friction is.
The friction is in what the integration does not send.
Teams using Figma's Slack integration have requested that public Slack channels be notified when a frame is marked Ready for Dev - but right now the integration only notifies about comments and mentions.
Developers are auto-subscribed to status notifications once they've viewed a file in Dev Mode, and receive an email notification when a design's status is changed to "Ready for dev." An email. In 2025.
The Figma community thread asking for Slack channel notifications on Ready for Dev status was opened in April 2025. As of August 2025, the feature still doesn't exist.
The webhook gap that trips up resolved comments
There's a second, less-discussed limitation.
The FILE_COMMENT webhook payload includes the comment text
, which makes it possible to route new Figma comments into a Slack thread. Teams build this, sometimes via Zapier, sometimes via a small webhook receiver they host themselves.
The problem:
the FILE_COMMENT webhook event does not trigger when a comment is resolved.
So the Slack thread that started when a PM dropped feedback on a login screen has no automatic close signal. Someone has to manually update the Slack thread, or it just drifts - one of those "is this still relevant?" artifacts that clutters #design-feedback by Thursday.
This is where the integration's architecture bites you. Comment creation is observable from outside Figma. Comment resolution is not. A teammate watching the channel can't tell whether the open thread represents live feedback or something the designer already fixed two versions ago.
What good Figma-to-Slack routing looks like
The DEV_MODE_STATUS_UPDATE webhook event does exist in Figma's API. It is triggered when the Dev Mode status of a layer changes, and can be used to track when layers are marked Ready for Dev, Completed, or when a status is cleared - including any change message the designer added.
That's enough payload to build a useful Slack message: the file name, the frame name, the designer's note, and a deep link into Dev Mode. Figma's Webhooks V2 API lets developers set up secure HTTPS endpoints that listen for real-time triggers including file updates, new comments, and library publications - with patterns for timing-safe passcode verification and idempotency to prevent duplicate event processing.
The practical path for teams today:
- Via Zapier or Make: catch
FILE_COMMENTevents and post to a channel; no code required, but you miss resolved-comment signals and Ready for Dev events - Via Figma webhook receiver + Slack API: handle
DEV_MODE_STATUS_UPDATEandFILE_COMMENTdirectly; gives you the most signal but requires a small hosted endpoint - Via a teammate in Slack: a tool like Beagle can watch for a pinged link or a message like "just marked checkout flow ready for dev" and post a structured update to #engineering-handoff with the Dev Mode link - no webhook infrastructure needed
The last path is the one most teams end up on by default, because standing up a webhook receiver for a 10-person design team rarely clears the cost-benefit bar.
Beagle in action#design-handoff, 4:03pmThe Microsoft Teams problem is worse
Figma's Slack plugin covers design teams on Slack, but there is no Teams equivalent.
Figma's internal notification system - the inbox bell and email digests - is the only alternative, and neither is suitable for time-sensitive design reviews or handoff signals.
Designers and developers reviewing files are often on Slack. Product managers tracking project status may be on Teams. Stakeholders and clients reviewing designs almost certainly have no Figma account at all.
The community thread requesting a native Teams integration has been open since March 2021 and has over 3,800 views. The workaround - routing Figma webhook events through a middleware like SyncRivo to reach both Slack and Teams - requires engineering time most design-led teams don't have on hand.
What teams actually do right now
Most product teams settle on a hybrid that is neither clean nor broken enough to justify fixing:
- A #design channel where designers paste Figma links manually when something is ready
- A pinned message convention ("🟢 = ready, 🟡 = in review") that works until someone forgets
- A weekly design-eng sync that exists largely to catch the signals the async tools missed
Individual Slack messages with design notes throughout the build - disruptive, and a structured single review session would be faster
The underlying issue is that Figma's event model and Slack's messaging model don't meet in the middle without something routing between them. The Figma Slack integration covers roughly 60% of the surface: comment mention in, no status change out, no resolved comment signal.
Teams with an active Figma admin and a developer who doesn't mind maintaining a webhook receiver can close that gap. Everyone else is pasting links into Slack and hoping the right person sees them.
Figma Slack integration design handoff: common questions
Does Figma send a Slack notification when a designer marks something Ready for Dev?
No - not as a channel notification. Figma sends an email to developers who have previously opened the file in Dev Mode. The native Slack integration only covers comments and mentions. To get a Slack message on a Ready for Dev status change, you need to handle the DEV_MODE_STATUS_UPDATE webhook event yourself or use middleware.
Can I get Figma comments posted automatically in a Slack channel?
Yes, via the FILE_COMMENT webhook or through Zapier. The webhook fires when a new comment is posted and includes the comment text. The limitation is that Figma's API does not fire a webhook when a comment is resolved, so you can post new comments to Slack but cannot automatically mark them resolved there.
Does Figma have a Microsoft Teams integration?
No native integration exists. Figma's notification system for external messaging platforms is Slack-only. Teams users receive email notifications or must route Figma webhook events through middleware to reach a Teams channel.
What Figma webhook events are available for building a Slack integration?
Figma's Webhooks V2 API supports FILE_COMMENT, FILE_UPDATE, FILE_VERSION_UPDATE, LIBRARY_PUBLISH, and DEV_MODE_STATUS_UPDATE. The DEV_MODE_STATUS_UPDATE event fires on Ready for Dev and Completed status changes. There is no webhook event for comment resolution.
Why do design-engineering handoffs still rely on manual Slack pings?
Because the tools that cover each side - Figma for design, Slack for communication - have a partial integration. Figma fires on comments; Slack receives them. But the handoff signal (Ready for Dev) and the resolution signal (comment closed) both fall outside what the native integration handles, so teams fill the gap with manual messages.