Name: Google Drive file comment closure watcher
Author: recued-core

Google Drive file comment closure watcher

by recued-core v1

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.

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.

Google Drive file comment closure watcher

This recipe Background automation

google-drivegdrivecommentscollaboration

by recued-core pinned v1

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.

google-drivegdrivecommentscollaboration

by recued-core pinned v1

Google Drive file comment closure watcher timeout

Background automation

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.

google-drivewatchertimeoutowner-review

by recued-core pinned v1

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.

google-drivewatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 111 steps

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

Data fetch

▼ shared_comment_watches ?

▼

Process (110 steps)

■ now date_add

Add 0 days to

■ watch_rows filter

Filter by condition

■ watch_rows_for_connection filter

Filter by condition

■ watch_rows_with_file filter

Filter by condition

■ watch_rows_with_comment filter

Filter by condition

■ never_checked_watch_rows filter

Filter by condition

■ checked_watch_rows filter

Filter by condition

■ checked_watch_rows_oldest_first sort

Sort by value.last_checked_at

■ fair_watch_rows flatten

Flatten nested lists in

■ candidate_rows slice

Take a subset of

■ batch_count count

Count items in candidate rows

■ candidate_count count

Count items in watch rows with comment

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting google has data

■ skip_comment_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ comment ?

skip: step.skip_comment_read equal true

■ comment_live_batch_context pick

Keep only specific fields from

■ comment_batch_context_envelopes merge

Combine objects together

■ comment_batch_contexts map

Extract from each item

■ live_resolved_value default

Apply default

■ live_resolved_value_live_batch_context pick

Keep only specific fields from

■ live_resolved_value_batch_context_envelopes merge

Combine objects together

■ live_resolved_value_batch_contexts map

Extract from each item

■ comment_resolved compare

Check if item live resolved value equals true

■ comment_resolved_live_batch_context pick

Keep only specific fields from

■ comment_resolved_batch_context_envelopes merge

Combine objects together

■ comment_resolved_batch_contexts map

Extract from each item

■ live_deleted_value default

Apply default

■ live_deleted_value_live_batch_context pick

Keep only specific fields from

■ live_deleted_value_batch_context_envelopes merge

Combine objects together

■ live_deleted_value_batch_contexts map

Extract from each item

■ comment_deleted compare

Check if item live deleted value equals true

■ comment_deleted_live_batch_context pick

Keep only specific fields from

■ comment_deleted_batch_context_envelopes merge

Combine objects together

■ comment_deleted_batch_contexts map

Extract from each item

■ actionable_status any

Check if any of the conditions are true

■ actionable_status_live_batch_context pick

Keep only specific fields from

■ actionable_status_batch_context_envelopes merge

Combine objects together

■ actionable_status_batch_contexts map

Extract from each item

■ closed_status ternary

Apply ternary

■ closed_status_live_batch_context pick

Keep only specific fields from

■ closed_status_batch_context_envelopes merge

Combine objects together

■ closed_status_batch_contexts map

Extract from each item

■ owner_action ternary

Apply ternary

■ owner_action_live_batch_context pick

Keep only specific fields from

■ owner_action_batch_context_envelopes merge

Combine objects together

■ owner_action_batch_contexts map

Extract from each item

■ skip_close any

Check if any of the conditions are true

■ skip_close_live_batch_context pick

Keep only specific fields from

■ skip_close_batch_context_envelopes merge

Combine objects together

■ skip_close_batch_contexts map

Extract from each item

■ closed_watch_key replace

Replace text in item watch key

■ closed_watch_key_live_batch_context pick

Keep only specific fields from

■ closed_watch_key_batch_context_envelopes merge

Combine objects together

■ closed_watch_key_batch_contexts map

Extract from each item

■ close_watch ?

skip: item.skip_close equal true

■ close_watch_live_batch_context pick

Keep only specific fields from

■ close_watch_batch_context_envelopes merge

Combine objects together

■ close_watch_batch_contexts map

Extract from each item

■ delete_closed_active_watch ?

skip: item.close_watch.ok not_equal true

■ delete_closed_active_watch_live_batch_context pick

Keep only specific fields from

■ delete_closed_active_watch_batch_context_envelopes merge

Combine objects together

■ delete_closed_active_watch_batch_contexts map

Extract from each item

■ notify_resolved_enabled compare

Check if setting notify when resolved equals true

■ notify_resolved_enabled_live_batch_context pick

Keep only specific fields from

■ notify_resolved_enabled_batch_context_envelopes merge

Combine objects together

■ notify_resolved_enabled_batch_contexts map

Extract from each item

■ notify_deleted_enabled compare

Check if setting notify when deleted equals true

■ notify_deleted_enabled_live_batch_context pick

Keep only specific fields from

■ notify_deleted_enabled_batch_context_envelopes merge

Combine objects together

■ notify_deleted_enabled_batch_contexts map

Extract from each item

■ should_notify_resolved all

Check if all conditions are true

■ should_notify_resolved_live_batch_context pick

Keep only specific fields from

■ should_notify_resolved_batch_context_envelopes merge

Combine objects together

■ should_notify_resolved_batch_contexts map

Extract from each item

■ should_notify_deleted all

Check if all conditions are true

■ should_notify_deleted_live_batch_context pick

Keep only specific fields from

■ should_notify_deleted_batch_context_envelopes merge

Combine objects together

■ should_notify_deleted_batch_contexts map

Extract from each item

■ status_should_notify any

Check if any of the conditions are true

■ status_should_notify_live_batch_context pick

Keep only specific fields from

■ status_should_notify_batch_context_envelopes merge

Combine objects together

■ status_should_notify_batch_contexts map

Extract from each item

■ should_notify all

Check if all conditions are true

■ should_notify_live_batch_context pick

Keep only specific fields from

■ should_notify_batch_context_envelopes merge

Combine objects together

■ should_notify_batch_contexts map

Extract from each item

■ notification_title ternary

Apply ternary

■ notification_title_live_batch_context pick

Keep only specific fields from

■ notification_title_batch_context_envelopes merge

Combine objects together

■ notification_title_batch_contexts map

Extract from each item

■ notify_owner ?

skip: item.should_notify not_equal true

■ notify_owner_live_batch_context pick

Keep only specific fields from

■ notify_owner_batch_context_envelopes merge

Combine objects together

■ notify_owner_batch_contexts map

Extract from each item

■ refreshed_watch_value merge

Combine objects together

skip: item.delete_closed_active_watch.ok equal true

■ refreshed_watch_value_live_batch_context pick

Keep only specific fields from

■ refreshed_watch_value_batch_context_envelopes merge

Combine objects together

■ refreshed_watch_value_batch_contexts map

Extract from each item

■ refresh_active_watch ?

skip: item.delete_closed_active_watch.ok equal true

■ refresh_active_watch_live_batch_context pick

Keep only specific fields from

■ refresh_active_watch_batch_context_envelopes merge

Combine objects together

■ refresh_active_watch_batch_contexts map

Extract from each item

■ closed_batch_rows filter

Filter by condition

■ refreshed_batch_rows filter

Filter by condition

■ closed_batch_count count

Count items in closed batch rows

■ refreshed_batch_count count

Count items in refreshed batch rows

■ summary to_summary

Format results as a summary card

Settings 5 configurable

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

google setting =

channels setting = in_app

batch limit setting = 5

notify when deleted setting = true

notify when resolved setting = true

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

Send notificationsRead your Google connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

recued-core

Details

111 steps 5 configurable settings recipe_id: google-drive-file-comment-closure-watcher

Google Drive file comment closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details