Does it create a task per action item or per meeting?

Per meeting in this recipe, with the next steps in a column. If you want one item per action item, have the agent loop the next-step list from get_meeting_assets and call create_item for each.

How does it avoid logging a meeting twice?

By storing each recording's meeting ID against the monday item it created. Each run it reads recent recordings, drops the ones already logged, and writes items only for new ones.

Zoommonday.com

Create monday.com items from Zoom meeting recordings

A Zoom + monday.com agent flow

Action items decided on a Zoom call live in someone's memory until they don't, and the next meeting opens with nobody having done the thing. A team that runs its work in monday.com wants each recorded meeting to leave a trail on the board automatically. The agent lists recent recordings with recordings_list, pulls the AI-generated summary and next steps for each with get_meeting_assets, and creates a monday item per meeting with create_item. Zoom answers the agent's call rather than pushing, so the agent reads on a cadence, after each meeting block or once a day, and only recordings it hasn't processed turn into items.

The flow

Zoomrecordings_list

Lists the user's cloud recordings, with date range and paging filters.

monday.comcreate_item

Creates a new item in a board, optionally with column values.

Step by step

Pick the board and the window
Point the agent at one monday board with a column for the meeting and a column for the next steps. Decide the date range it reads, for instance recordings from the last day.
List recent recordings
The agent calls recordings_list for the window, getting each meeting's topic, start time, and IDs. It then calls get_meeting_assets per recording to read the summary and the next-step items Zoom extracted.
Create the monday items
For each meeting the agent calls create_item with the topic as the item name and column values for the date, the summary, and the next steps, plus a link to the recording.
Record what's already logged
Store each recording's meeting ID against the item it created. Next run the agent skips recordings already logged, so a meeting isn't written to the board twice.

Tell your agent

Once a day, list my Zoom cloud recordings from the last 24 hours. For each one not already logged, read its summary and next steps, then create a monday item on the Meeting Follow-ups board with the meeting topic, date, the summary, the next steps, and a link to the recording. Skip recordings you've already logged.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Zoom install guide monday.com install guide

Worth knowing

recordings_list returns recordings, not live calls, so a meeting only appears once its cloud recording has processed. The item lands after Zoom finishes the recording, not while the call is happening.
get_meeting_assets returns the AI summary when the account has that feature enabled. If a meeting has no summary, have the agent fall back to the topic and a link rather than skipping the item.
create_item writes to a board by ID, and column values must match the board's column types and IDs. Read the board schema once with get_board_schema so the summary and date land in the right columns.

Questions

Does it create a task per action item or per meeting?: Per meeting in this recipe, with the next steps in a column. If you want one item per action item, have the agent loop the next-step list from get_meeting_assets and call create_item for each.
How does it avoid logging a meeting twice?: By storing each recording's meeting ID against the monday item it created. Each run it reads recent recordings, drops the ones already logged, and writes items only for new ones.