Owner-visible list/close role for recued-core/google-drive-file-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.
Google Drive file comment closure watcher lifecycle review
Owner-visible list/close role for recued-core/google-drive-file-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.
Complete workflow
Google Drive File Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Google Drive file comments. It composes the Google Drive capability pack with a closure ledger: add one comment to an existing Drive file through the existing approval gate, persist only the connection/file/comment linkage in data.shared, and let a scheduled watcher re-read that exact comment until Drive reports it resolved or deleted. This pack does not replace Google Drive comments, native Drive notifications, document review dashboards, permission workflows, comment resolution controls, or general file-status reporting; it adds Recued-visible closure state for file 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.
Workflow origin for the Google Drive file comment closure loop. It reads one Drive file and its current comments for context, creates exactly one owner-provided top-level file comment through recued-core.gdrive.file.comment.create, and when the comment succeeds it seeds durable data.shared closure state for google-drive-file-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not edit or delete comments, resolve comment threads, change file permissions, mutate document body content, download files, move files, create folders, configure Drive notifications, or call arbitrary Google Drive endpoints.
Scheduled adopter for Google Drive file comment closure rows seeded by comment-google-drive-file-with-closure. It lists only Recued-originated file-comment watches, re-reads a bounded batch of Drive comment thread, and closes the shared row when Google Drive reports that comment resolved or deleted. It can notify the owner on resolution or deletion, but it never creates, edits, deletes, or resolves comments, changes file permissions, mutates document body content, downloads files, moves files, configures Drive notifications, or calls arbitrary Google Drive endpoints.
Low-frequency timeout role for recued-core/google-drive-file-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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
active_rows
?
timed_out_rows
?
closed_rows
?
▼
Process (10 steps)
close_key
trim
Trim whitespace from setting close key
close_is_timed_out
starts_with
Check if close key starts with data.shared.recipe.recued-core_google-drive-file-comment-closure.timed_out.
close_is_closed
starts_with
Check if close key starts with data.shared.recipe.recued-core_google-drive-file-comment-closure.closed.
close_allowed
any
Check if any of the conditions are true
close_terminal_row
?
skip: step.close_allowed not_equal true
lifecycle_rows
flatten
Flatten nested lists in
shown_rows
slice
Take a subset of
row_count
count
Count items in lifecycle rows
table
to_table
Format results as a data table
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
close key
setting
=
row limit
setting
=
50
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.