Workflow origin for the ClickUp task comment closure loop. It reads one ClickUp task and current comments for context, creates exactly one owner-provided task comment through recued-core.clickup.task.comment.create, and when the comment succeeds it seeds durable data.shared closure state for clickup-task-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, close, delete, attach to, assign, tag, checklist, time-track, link, webhook, or otherwise mutate ClickUp tasks.
Comment on ClickUp task with closure watch
Workflow origin for the ClickUp task comment closure loop. It reads one ClickUp task and current comments for context, creates exactly one owner-provided task comment through recued-core.clickup.task.comment.create, and when the comment succeeds it seeds durable data.shared closure state for clickup-task-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, close, delete, attach to, assign, tag, checklist, time-track, link, webhook, or otherwise mutate ClickUp tasks.
Complete workflow
ClickUp Task Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created ClickUp task comments. It composes the ClickUp capability pack with a closure ledger: add one owner-approved comment to an existing ClickUp task, persist only the connection/task/comment linkage in data.shared, and let a scheduled watcher re-read that exact task until ClickUp reports a configured terminal status such as complete, completed, closed, or done. This pack does not replace ClickUp task comments, native notifications, status workflows, task close controls, dashboards, reminders, automations, webhooks, or general project reporting; it adds Recued-visible closure state for task comments 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.
Scheduled adopter for ClickUp task comment closure rows seeded by comment-clickup-task-with-closure. It lists only Recued-originated task-comment watches, re-reads a bounded batch of ClickUp task, and closes the shared row when ClickUp reports a configured terminal status such as complete, completed, closed, or done. It can notify the owner on closure, but it never creates, updates, transitions, closes, deletes, attaches to, assigns, tags, checklists, time-tracks, links, webhooks, comments on, or otherwise mutates ClickUp tasks.
Low-frequency timeout role for recued-core/clickup-task-comment-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.
Owner-visible list/close role for recued-core/clickup-task-comment-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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (40 steps)
task_id_value
trim
Trim whitespace from setting task id
team_id_value
trim
Trim whitespace from setting team id
comment_text_value
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting clickup has data
has_task_id
compare
Check if task id value has data
custom_task_ids_enabled
compare
Check if setting custom task ids equals true
has_team_id
compare
Check if team id value has data
missing_team_for_custom_task_id
all
Check if all conditions are true
has_comment_text
compare
Check if comment text value has data
skip_task_read
any
Check if any of the conditions are true
task
?
skip: step.skip_task_read equal true
task_status
default
Apply default
has_task_status
compare
Check if task status has data
task_status_norm
lowercase
Convert task status to lowercase
task_already_terminal
compare
Check if task status norm is one of setting terminal statuses
skip_comment_context
any
Check if any of the conditions are true
comments_raw
?
skip: step.skip_comment_context equal true
comments
default
Apply default
comment_count_before_create
count
Count items in comments
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment id has data
task_list_id
default
Apply default
created_at
date_add
Add 0 days to
raw_task_key
join
Join items with ":"
task_key_colon
replace
Replace text in raw task key
task_key_slash
replace
Replace text in task key colon
task_key_dot
replace
Replace text in task key slash
task_key_at
replace
Replace text in task key dot
task_key_space
replace
Replace text in task key at
task_key_left_angle
replace
Replace text in task key space
task_key_right_angle
replace
Replace text in task key left angle
task_key_plus
replace
Replace text in task key right angle
task_key_equals
replace
Replace text in task key plus
task_key_question
replace
Replace text in task 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_clickup_task_comment_closure_watch
?
skip: step.skip_closure_seed equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
clickup
setting
=
task id
setting
=
team id
setting
=
notify all
setting
=
false
comment text
setting
=
custom task ids
setting
=
false
terminal statuses
setting
=
complete,completed,closed,done
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.