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.
Comment on Google Drive file with closure watch
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.
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.
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.
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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (30 steps)
file_id
trim
Trim whitespace from setting file id
comment_text
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting google has data
has_file_id
compare
Check if file id has data
has_comment_text
compare
Check if comment text has data
skip_file_read
any
Check if any of the conditions are true
file
?
skip: step.skip_file_read equal true
comments_raw
?
skip: step.skip_file_read equal true
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
comments
default
Apply default
comment_count_before_create
count
Count items in comments
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment 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_google_drive_comment_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.
google
setting
=
file id
setting
=
comment text
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.