Workflow origin for the GitLab issue note closure loop. It reads one GitLab issue and current comment notes for context, creates exactly one owner-provided public note through recued-core.gitlab.issue.note.create, and when the note succeeds it seeds durable data.shared closure state for gitlab-issue-note-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, move, label, assign, or otherwise mutate GitLab issues.
Comment on GitLab issue with closure watch
Workflow origin for the GitLab issue note closure loop. It reads one GitLab issue and current comment notes for context, creates exactly one owner-provided public note through recued-core.gitlab.issue.note.create, and when the note succeeds it seeds durable data.shared closure state for gitlab-issue-note-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, move, label, assign, or otherwise mutate GitLab issues.
Complete workflow
GitLab Issue Note Closure Loop
4 pinned recipes
Workflow pack for Recued-created GitLab issue notes. It composes the GitLab capability pack with a closure ledger: add one owner-approved public note to an existing GitLab issue, persist only the connection/project/issue/note linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitLab reports it closed. This pack does not replace GitLab issue comments, native notifications, issue state controls, boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue notes 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 GitLab issue note closure rows seeded by comment-gitlab-issue-with-closure. It lists only Recued-originated issue-note watches, re-reads a bounded batch of GitLab issue, and closes the shared row when GitLab reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, moves, labels, assigns, comments on, or otherwise mutates GitLab issues.
Low-frequency timeout role for recued-core/gitlab-issue-note-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/gitlab-issue-note-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 (35 steps)
project_id_value
trim
Trim whitespace from setting project id
issue_iid_value
trim
Trim whitespace from setting issue iid
note_body_value
trim
Trim whitespace from setting note body
has_connection
compare
Check if setting gitlab has data
has_project_id
compare
Check if project id value has data
has_issue_iid
compare
Check if issue iid value has data
has_note_body
compare
Check if note body value has data
skip_issue_read
any
Check if any of the conditions are true
issue
?
skip: step.skip_issue_read equal true
notes_raw
?
skip: step.skip_issue_read equal true
state
default
Apply default
has_issue_state
compare
Check if state has data
issue_already_closed
compare
Check if state equals closed
notes
default
Apply default
note_count_before_create
count
Count items in notes
skip_note_create
any
Check if any of the conditions are true
created_note
?
skip: step.skip_note_create equal true
created_note_id
default
Apply default
has_created_note
compare
Check if created note id has data
created_at
date_add
Add 0 days to
raw_issue_key
join
Join items with ":"
issue_key_colon
replace
Replace text in raw issue key
issue_key_slash
replace
Replace text in issue key colon
issue_key_dot
replace
Replace text in issue key slash
issue_key_at
replace
Replace text in issue key dot
issue_key_space
replace
Replace text in issue key at
issue_key_left_angle
replace
Replace text in issue key space
issue_key_right_angle
replace
Replace text in issue key left angle
issue_key_plus
replace
Replace text in issue key right angle
issue_key_equals
replace
Replace text in issue key plus
issue_key_question
replace
Replace text in issue 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_gitlab_issue_note_closure_watch
?
skip: step.skip_closure_seed equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
gitlab
setting
=
issue iid
setting
=
note body
setting
=
project id
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.