Weekly Figma design review agenda in Notion

Every Monday morning, get a Notion agenda grouping your Figma files by ready to review, blocked, and shipped last week, with thumbnails and a Slack ping.

Agentic Task
FigmaNotionSlack BotProductOperationsMeeting WorkflowsDaily Digests
PromptCreate

Every Monday at 8am, prep the design review meeting by scanning a configured list of Figma design files and drafting an agenda for the team. Take three inputs at the top of the workflow: the list of Figma file keys (or file URLs) to review, the Notion parent database id for the 'Design Reviews' database, and the Slack channel id where the announcement should land.

For each Figma file, call Get File Metadata for the file name and last-modified timestamp, Get File Versions to see which named versions shipped in the last seven days, and Get Comments to pull open threads, mentions, and unresolved questions. If a file shows no new named versions, no fresh comments, and no changes since last Monday, skip it so the agenda stays focused. For any frame whose name or comment context flags it as 'ready for review', call Render Images of File Nodes to grab a PNG thumbnail. Figma render URLs expire after 30 days, so download the image bytes immediately and embed those in the Notion page rather than linking to the temporary Figma URL.

Draft an agenda grouped into three sections: 'Ready to review' (files with frames marked ready for review), 'Blocked on questions' (files with unresolved comments or open @-mentions the team needs to answer), and 'Shipped last week' (files whose named versions landed inside the seven-day window). Under each file give a one-line human summary of what changed or what needs a decision, plus a Figma deep-link that jumps straight to the relevant node when one is available.

Publish the agenda by calling Create a Page in Notion under the configured Design Reviews database (page title 'Design review — <this Monday's date>'), then use Append Block Children to fill it in: heading blocks for each of the three sections, one child block per file with the summary and the Figma link, and embedded thumbnails right below the ready-to-review entries. Finally, call Slack Send a Message on Slack Bot to post a short heads-up in the configured channel with the Notion page URL and a one-sentence preview of what's on the agenda (e.g. 'Design review agenda is up — 3 ready, 2 blocked, 4 shipped last week'). Skip the Slack post if the agenda ends up empty.

Configurable inputs the author should surface at the top of the workflow: the Figma file list, the Notion Design Reviews database id, the Slack channel id, the activity window (default 7 days), the naming pattern that marks a frame as ready for review (default: frame name contains 'ready for review'), and the schedule (default Monday 8am in the org's timezone).

Additional information

What does this prompt do?
  • Scans a list of Figma files you care about for last week's named versions, unresolved comments and mentions, and freshly modified frames
  • Groups files into 'ready to review', 'blocked on questions', and 'shipped last week' with a one-line summary and a Figma deep-link for each
  • Grabs thumbnails of frames flagged as ready for review and saves them into the Notion page so the agenda still works after Figma's live preview links expire
  • Publishes a fresh page under your 'Design Reviews' database in Notion and posts a short Slack heads-up pointing the team at it
  • Skips any file with zero activity in the last seven days so the agenda stays focused on what actually needs discussion
What do I need to use this?
  • A Figma account with access to the design files you want reviewed each week
  • A Notion workspace with a 'Design Reviews' database, shared with your Notion connection
  • A Slack workspace and the channel where the design team gathers before reviews
  • The list of Figma file links to review, the Notion database link, and the Slack channel you want pinged
How can I customize it?
  • Swap the list of Figma files to focus on whichever projects your team is reviewing this quarter
  • Change the schedule to fit your review rhythm, whether that's mornings, afternoons, weekly, biweekly, or a different day of the week
  • Point it at a different Slack channel, or send to Microsoft Teams instead
  • Adjust the seven-day activity window if your team reviews on a shorter or longer cadence
  • Rename the three sections or add your own, like 'design QA' or 'exec preview'

Frequently asked questions

What if a Figma file had zero activity last week?
It gets skipped. The agenda only lists files with new versions, fresh comments, or frames flagged as ready to review, so the team never sits through a stale file.
Will the thumbnails still work weeks later?
Yes. Figma's live preview links expire after 30 days, so the workflow saves the thumbnail images directly into your Notion page rather than linking to a URL that goes stale.
Does it grab every design file in my Figma team?
No. You give it the exact list of files you want reviewed each Monday, so it stays focused on the projects that actually matter.
How does it know a frame is 'ready for review'?
It looks for frames that are named or tagged as ready for review inside each file. You can tell the workflow which naming convention your team uses.
Do I need a paid Notion plan for this?
No. Any Notion workspace works, as long as your Design Reviews database is shared with the Notion connection you set up.

Stop stitching your design review agenda together by hand.

Let this workflow round up Figma versions, comments, and thumbnails every Monday and hand your team a ready-made Notion agenda.