Skip to content
Recued
Menu
← Back to recipes

Reply to Confluence inline comment with closure watch

by recued-core v1

Workflow origin for the Confluence inline comment reply closure loop. It reads one Confluence page and its open inline comments for context, creates exactly one owner-provided storage-format reply on an existing inline comment through recued-core.confluence.inline_comment.create, and when the reply succeeds it seeds durable data.shared closure state for confluence-inline-comment-reply-closure-watcher. It uses deterministic owner-provided storage content rather than AI and does not create top-level inline comments, create footer comments, edit or resolve comments, update pages, delete pages, update tasks, alter labels, change permissions, create properties, configure automations, or call arbitrary Atlassian endpoints.

Complete workflow

Workflow pack for Recued-created replies to existing Confluence inline comments. It composes the Confluence capability pack with a closure ledger: add one owner-approved storage-format reply to an existing inline comment on a configured page, persist only the connection/cloud/page/comment/reply linkage in data.shared, and let a scheduled watcher re-read that page's inline comments until Confluence reports the root comment resolved, no longer returns the comment, or the page reaches a configured terminal status. This pack does not replace Confluence inline comments, resolved-state controls, native notifications, tasks, page/blog workflows, page properties, automations, labels, permissions, or space governance; it adds Recued-visible closure state for inline-comment replies 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 Confluence inline comment reply closure loop. It reads one Confluence page and its open inline comments for context, creates exactly one owner-provided storage-format reply on an existing inline comment through recued-core.confluence.inline_comment.create, and when the reply succeeds it seeds durable data.shared closure state for confluence-inline-comment-reply-closure-watcher. It uses deterministic owner-provided storage content rather than AI and does not create top-level inline comments, create footer comments, edit or resolve comments, update pages, delete pages, update tasks, alter labels, change permissions, create properties, configure automations, or call arbitrary Atlassian endpoints.

confluencecommentsinline-commentsknowledge-base
by recued-core pinned v1

Scheduled adopter for Confluence inline comment reply closure rows seeded by reply-confluence-inline-comment-with-closure. It lists only Recued-originated inline-comment reply watches, re-reads a bounded batch of Confluence page and that page's inline comments, and closes or flags the shared row when Confluence reports the watched root comment resolved, the comment is no longer returned, or the page reaches a configured terminal status. It can notify the owner on resolution, disappearance, or terminal page status, but it never creates, updates, resolves, deletes, or comments on Confluence content, updates pages, changes tasks, alters labels, changes permissions, creates properties, configures automations, or calls arbitrary Atlassian endpoints.

confluencecommentsinline-commentsknowledge-base
by recued-core pinned v1

Low-frequency timeout role for recued-core/confluence-inline-comment-reply-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.

confluencewatchertimeoutowner-review
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 48 steps

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

Process (48 steps)
cloud_id_value trim
Trim whitespace from setting cloud id
page_id_value trim
Trim whitespace from setting page id
comment_id_value trim
Trim whitespace from setting comment id
reply_storage_body trim
Trim whitespace from setting reply storage value
has_connection compare
Check if setting atlassian has data
has_cloud_id compare
Check if cloud id value has data
has_page_id compare
Check if page id value has data
has_comment_id compare
Check if comment id value has data
has_reply_storage_value compare
Check if reply storage body has data
skip_page_read any
Check if any of the conditions are true
page ?
skip: step.skip_page_read equal true
page_status default
Apply default
has_page_status compare
Check if page status has data
page_status_norm lowercase
Convert page status to lowercase
page_already_terminal compare
Check if page status norm is one of setting page terminal statuses
skip_comment_list any
Check if any of the conditions are true
comments_raw ?
skip: step.skip_comment_list equal true
comments default
Apply default
target_comment_rows filter
Filter by condition
target_comment slice
Take a subset of
has_target_comment compare
Check if target comment has data
target_parent_comment_id default
Apply default
target_is_reply compare
Check if target parent comment id has data
target_status default
Apply default
target_status_norm lowercase
Convert target status to lowercase
target_already_resolved compare
Check if target status norm is one of setting resolved statuses
existing_replies filter
Filter by condition
reply_count_before_send count
Count items in existing replies
skip_reply any
Check if any of the conditions are true
reply ?
skip: step.skip_reply equal true
created_reply_id default
Apply default
has_created_reply compare
Check if created reply id has data
created_at date_add
Add 0 days to
raw_comment_key join
Join items with ":"
comment_key_colon replace
Replace text in raw comment key
comment_key_slash replace
Replace text in comment key colon
comment_key_dot replace
Replace text in comment key slash
comment_key_at replace
Replace text in comment key dot
comment_key_space replace
Replace text in comment key at
comment_key_left_angle replace
Replace text in comment key space
comment_key_right_angle replace
Replace text in comment key left angle
comment_key_plus replace
Replace text in comment key right angle
comment_key_equals replace
Replace text in comment key plus
comment_key_question replace
Replace text in comment 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_confluence_inline_comment_closure_watch ?
skip: step.skip_closure_seed equal true
summary to_summary
Format results as a summary card
Settings 8 configurable

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

page id setting =
cloud id setting =
atlassian setting =
comment id setting =
resolved statuses setting = resolved
reply storage value setting =
page terminal statuses setting = archived,deleted,trashed
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 Atlassian connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

confluence confluencecommentsinline-commentsknowledge-basecollaborationapprovalclosed-loopstate:confluence-inline-comment-reply-closure-watcherpack:confluence-inline-comment-reply-closure

Details

48 steps 8 configurable settings recipe_id: reply-confluence-inline-comment-with-closure