A designer marks three frames "Ready for dev" in Figma. The engineers working on those frames hear nothing in Slack. They find out an hour later when someone pastes a link in a thread and says "oh this has been ready since this morning."
That is the specific friction the Figma-Slack integration has not solved, and it is worth understanding why - because the gap is not obvious from the feature list.
What the Figma-Slack integration actually does
The integration is genuinely useful for what it does. 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 receive notifications on specific files, folders, and teams - covering comments, mentions, branching updates, new files, and new folders.
That list looks comprehensive until you notice what is missing: Dev Mode status changes.
Developers are auto-subscribed to status notifications once they've viewed a file in Dev Mode - but they receive an email notification when a design's status is changed to "Ready for dev." Not a Slack message. Not a channel post. An email.
For a team that lives in Slack, email is where notifications go to be ignored. There is also a batching behavior worth knowing: comments made within 10 minutes of each other are batched into a single Slack message instead of individual messages. That is sensible noise control, but it means a burst of feedback on a design does not arrive as separate, actionable items - it arrives as one lump, with less context about what changed.
The "Ready for dev" gap is real and documented
As of April 2025, a feature request on Figma's community forum asked for Slack channel notifications when a frame is marked Ready for dev - not just personal alerts. The poster noted the Slack integration only notifies about comments and mentions, and that for dev handoff, status updates posted to team channels would keep product and dev teams aligned in real time.
By August 2025, the thread had two replies: one calling out that it should have been among the first things added, and another confirming the feature still does not exist.
This is not a minor usability complaint. The "Ready for dev" status is the handoff signal. When a designer marks a frame, section, or component with this status, it tells the development team that the design is finalized and approved for implementation. It is the moment the baton passes. And the baton is currently passed by email.
Most design handoffs break down not because the design is bad, but because developers lack the context to build it accurately. Sending the most critical signal to an inbox rather than the channel where developers track their work compounds that problem.
One more compounding factor: because developers are auto-subscribed whenever they open a file in Dev Mode, anyone who glances at a file once starts receiving notifications for every future "Ready for dev" change - bloating inboxes with alerts for designs they are not responsible for building.
| Event | Slack channel notification | Personal Slack DM | |
|---|---|---|---|
| Comment on file | ✓ (if subscribed) | ✓ (if @mentioned) | ✓ |
| New branch created | ✓ (if subscribed) | - | - |
| Invited to file | - | ✓ | ✓ |
| Ready for dev status set | ✗ | ✗ | ✓ |
| Library published | ✗ | - | - |
The table makes the gap concrete. The two events that matter most for cross-functional coordination - handoff status and library updates - are the ones the Slack integration does not cover.
What teams actually do to close the gap
Because the native integration does not forward handoff status, teams have built workarounds at varying levels of effort.
Figma webhooks (V2 API).
Figma's webhook API can post a message to a Slack channel when someone comments on a file. The same mechanism supports other event types.
FILE_COMMENT is the easiest event to wire. FILE_VERSION_UPDATE and status-change events require more handling. If your team has someone comfortable writing a small webhook receiver - or running it through a service like Pipedream or Make - this is the most reliable path, and it costs nothing beyond the engineering time.
Manual convention. Most teams fall back here without admitting it: the designer drops a link in #design-handoff with a message saying "X is ready." It works until it does not - a missed post, a shared channel that nobody monitors, or a handoff that happens on a Friday afternoon.
These status signals are supposed to replace the messy back-and-forth of Slack messages and Jira comments
, but without the automation, the Slack messages come back.
Third-party tools. There are purpose-built tools that sit between Figma and Slack and map more event types to channel messages, including version publishes and review requests.
Beagle in action#product-eng, 2:07pmHow a good AI teammate fits into this workflow
The underlying problem is coordination overhead. Someone has to translate a status change in one tool into an actionable message in another - with enough context that the receiver can act without asking a follow-up question.
That is exactly the kind of task an AI teammate handles well: read the trigger (a Slack message, a file link, a Jira ticket update), pull the relevant context from wherever it lives, draft the routing message, and wait for a human to approve before posting. Designers can add notes to statuses about updates or changes
- those notes are the context that usually gets lost when a handoff is announced by a generic "this is ready" message.
The 30% efficiency gain often cited from Figma Dev Mode adoption ( according to a Forrester TEI report, teams using Figma experience a 30% increase in development efficiency ) assumes the handoff signal actually reaches the right person. Without a reliable Slack notification for "Ready for dev," some of that gain sits in email.
Figma Slack integration: common questions
Does the Figma Slack integration notify you when a design is marked "Ready for dev"?
No. As of August 2025, "Ready for dev" status changes send an email notification to developers who have previously opened the file in Dev Mode - but no Slack channel notification is fired. The Slack integration covers comments, mentions, branch updates, and new files, but not Dev Mode status changes. This is an open feature request on Figma's forum.
What events does a Figma channel subscription in Slack cover?
A channel subscription covers comments, @mentions, branching updates, new files, and new folders in your subscribed resource. It does not cover Dev Mode status changes, library publishes, or file version history updates. Comments posted within a 10-minute window are batched into a single Slack message.
Can you reply to a Figma comment directly from Slack?
Yes. You can get notified about comments, mentions, and invites in Figma and FigJam files, and reply to feedback directly in Slack. This works for comments you are mentioned in via default notifications - but it does not open a shared thread visible to the whole channel.
What is the easiest way to get "Ready for dev" alerts into Slack today?
The lightest-weight option is Figma's webhook V2 API, which can post to a Slack channel on status-change events. It requires a small webhook receiver - deployable on Pipedream, Railway, or similar in under an hour. Alternatively, a structured Slack convention (designer posts a standard message with a Dev Mode link) plus a channel subscription for comment activity gets most of the way there without any custom code.
Does the Figma Slack integration require a paid Figma plan?
The integration is free on all Figma plans. Dev Mode itself - which includes "Ready for dev" status and the Completed status - requires a Full or Dev seat and a paid plan, with the Completed status available on Organization and Enterprise plans only.