Skip to content
Recued
Menu
← Back to recipes

Comment on monday.com item with closure watch

by recued-core v1

Workflow origin for the monday.com item update closure loop. It reads one monday.com board, item, and current item updates for context, creates exactly one owner-provided item update through recued-core.monday.update.create, and when the update succeeds it seeds durable data.shared closure state for monday-item-update-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create items, edit column values, move, archive, delete, restructure, upload to, invite users to, automate, notify from, or otherwise mutate monday.com items beyond the owner-approved update/comment.

Complete workflow

Workflow pack for Recued-created monday.com item updates. It composes the monday.com capability pack with a closure ledger: add one owner-approved update/comment to an existing monday.com item, persist only the connection/board/item/update linkage in data.shared, and let a scheduled watcher re-read that exact item until monday.com reports the item archived, deleted, or moved into a configured terminal group. Archived or terminal-group items close the Recued row; deleted items are marked for owner review. This pack does not replace monday.com item updates, native automations, notifications, dashboards, groups, status columns, item archive controls, board permissions, WorkForms, docs, or general board reporting; it adds Recued-visible closure state for item updates Recued created.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Workflow origin for the monday.com item update closure loop. It reads one monday.com board, item, and current item updates for context, creates exactly one owner-provided item update through recued-core.monday.update.create, and when the update succeeds it seeds durable data.shared closure state for monday-item-update-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create items, edit column values, move, archive, delete, restructure, upload to, invite users to, automate, notify from, or otherwise mutate monday.com items beyond the owner-approved update/comment.

mondaymonday.comitemsupdates
by recued-core pinned v1

Scheduled adopter for monday.com item update closure rows seeded by comment-monday-item-with-closure. It lists only Recued-originated item-update watches, re-reads a bounded batch of monday.com item, closes the shared row when monday.com reports the item archived or moved into a configured terminal group, and marks the row for owner review when the item was deleted. It can notify the owner on terminal state, but it never creates, updates, moves, archives, deletes, restructures, uploads to, invites users to, automates, notifies from, comments on, or otherwise mutates monday.com items.

mondaymonday.comitemsupdates
by recued-core pinned v1

Low-frequency timeout role for recued-core/monday-item-update-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

mondaywatchertimeoutowner-review
by recued-core pinned v1

Owner-visible list/close role for recued-core/monday-item-update-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

mondaywatcherreviewclose
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 45 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (45 steps)
board_id_value trim
Trim whitespace from setting board id
item_id_value trim
Trim whitespace from setting item id
update_body_value trim
Trim whitespace from setting update body
has_connection compare
Check if setting monday has data
has_board_id compare
Check if board id value has data
has_item_id compare
Check if item id value has data
has_update_body compare
Check if update body value has data
skip_context_reads any
Check if any of the conditions are true
board ?
skip: step.skip_context_reads equal true
item_details ?
skip: step.skip_context_reads equal true
live_item_id default
Apply default
has_live_item compare
Check if live item id has data
live_board_id default
Apply default
item_on_configured_board compare
Check if live board id equals board id value
item_state default
Apply default
item_state_norm lowercase
Convert item state to lowercase
item_archived compare
Check if item state norm equals archived
item_deleted compare
Check if item state norm equals deleted
item_group_id default
Apply default
item_in_terminal_group compare
Check if item group id is one of setting terminal group ids
item_already_terminal any
Check if any of the conditions are true
skip_update_context any
Check if any of the conditions are true
updates_raw ?
skip: step.skip_update_context equal true
updates default
Apply default
update_count_before_create count
Count items in updates
skip_update_create any
Check if any of the conditions are true
created_update ?
skip: step.skip_update_create equal true
created_update_id default
Apply default
has_created_update compare
Check if created update id has data
created_at date_add
Add 0 days to
raw_item_key join
Join items with ":"
item_key_colon replace
Replace text in raw item key
item_key_slash replace
Replace text in item key colon
item_key_dot replace
Replace text in item key slash
item_key_at replace
Replace text in item key dot
item_key_space replace
Replace text in item key at
item_key_left_angle replace
Replace text in item key space
item_key_right_angle replace
Replace text in item key left angle
item_key_plus replace
Replace text in item key right angle
item_key_equals replace
Replace text in item key plus
item_key_question replace
Replace text in item key equals
skip_closure_seed any
Check if any of the conditions are true
closure_timeout_at date_add
Add setting no response timeout days days to
seed_monday_item_update_closure_watch ?
skip: step.skip_closure_seed equal true
summary to_summary
Format results as a summary card
Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

monday setting =
item id setting =
board id setting =
update body setting =
mentions list setting =
terminal group ids setting =
no response timeout days setting = 30

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Monday connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.itemsdata.create_updatedata.shareddata.boards

About

Tags

monday mondaymonday.comitemsupdatescommentswork-managementproject-managementapprovalclosed-loopstate:monday-item-update-closure-watcherpack:monday-item-update-closure

Details

45 steps 7 configurable settings recipe_id: comment-monday-item-with-closure