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.
Confluence Inline Comment Reply Closure Loop
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.
What this pack installs
This pack installs the complete recipe workflow together. 2 supporting recipes run as background automation.
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.
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.
Owner-visible list/close role for recued-core/confluence-inline-comment-reply-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.
Builds on
- confluence v1+
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.