Turn today's Miro boards into written Notion summaries

Every weekday at 6pm, turn any Miro board my team touched today into a written summary document in Notion, so the people who missed the session do not have to squint at a canvas to work out what was decided. Use a cron trigger for this.

Start in Miro with List Boards to find the boards that were modified today, and ignore everything that was not touched, so untouched boards are never rewritten. For each board that qualifies, call Get Board to pick up its proper title and the link back to the board. Then call List Board Items to read the full contents: sticky notes, text items, shapes, cards and frames. That items endpoint is read only and returns items of every type together, which is exactly what I want, and it is cursor paginated, so keep following the cursor until you have every item on the board rather than summarizing only the first page.

Organize the write up by frame. Each item carries a parent field indicating which frame contains it, so group the items into their frames and use each frame title as a section heading in the document, in the order the frames read across the canvas from left to right and top to bottom. Within a section, use each item's position coordinates to work out which notes sit together as a cluster and which sit apart, since spatial grouping is how people encode meaning on a board. Anything that is not inside a frame goes in a short closing section for loose items. Do not try to reconstruct the flow of a diagram from connector lines as the primary structure. Frames and item positions are the structure. If a particular frame is clearly a flow diagram and the direction genuinely matters, you may call List Connectors on that board to check which items point at which, but treat it as a supporting detail only.

Write flowing prose that explains what the board actually says, not a dump of the raw note text in a bulleted list. Under each frame heading, explain the point that frame is making, what the group converged on, where notes cluster into a theme, and where the board records disagreement or an open question. Name the specific content from the notes so the summary is concrete, but connect it into sentences a person can read cold without ever opening the board. If a frame holds only a couple of stray notes and there is nothing real to say, cover it in a sentence rather than padding it out.

Create the document in Notion with Create a Page as a child of my team's workspace page, titling it with the board name and the session date. Then fill the body using Update Page Content as Markdown, with the frame sections as headings. Always open the page with a link back to the source Miro board and the date of the session, so the document is traceable to the canvas it came from. Create a new dated page on each run rather than overwriting an earlier one, so a board that gets worked on repeatedly builds up a history of sessions.

Finish by posting the Notion link to my team's Slack channel using Send a Message, with a single line describing what the board covered, for example which decision was made or which part of the product it concerned, so people can tell from the message alone whether they need to read it. Write one Notion page and one Slack message per board. If several boards were touched today, handle each one separately. If no boards were modified today, do nothing at all and post no Slack message.