Recued
Get started
Menu
Publish Sign in GitHub
← Back to recipes

Comment on monday.com item with closure watch

by recued-core v1 6 views

Use “Comment on monday.com item with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

monday.com Item Update Closure Loop 4 pinned recipes

Use monday.com Item Update Closure Loop in Recued for items, updates, comments, and work management. It includes 2 ready-to-run workflows and 1 related pack in one install.

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

monday.com item update closure watcher
Background automation

Use “monday.com item update closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

mondaymonday.comitemsupdates
by recued-core pinned v1
monday.com item update closure watcher timeout
Background automation

Use “monday.com item update closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, 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
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.

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

recued-core

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-item-with-closure-monday