Name: Figma comment reply closure watcher
Author: recued-core

Figma comment reply closure watcher

by recued-core v1

Scheduled adopter for Figma comment reply closure rows seeded by reply-figma-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Figma file's comments, and closes the shared row when Figma reports the watched root comment resolved or no longer returns it. It can notify the owner on resolution or disappearance, but it never creates, edits, deletes, or resolves comments, adds reactions, mutates files, exports images, configures webhooks, or calls arbitrary Figma endpoints.

Complete workflow

Figma Comment Reply Closure Loop 4 pinned recipes

Workflow pack for Recued-sent Figma comment replies. It composes the Figma capability pack with a closure ledger: reply once to an existing Figma file comment through the existing approval gate, persist only the connection/file/comment/reply linkage in data.shared, and let a scheduled watcher re-read that exact file comment until Figma reports it resolved or the comment is no longer present. This pack does not replace Figma comments, native notifications, design review dashboards, webhook administration, comment resolution controls, or general file-status reporting; it adds Recued-visible closure state for comment replies Recued sent.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Figma comment reply closure watcher

This recipe Background automation

figmacommentscollaborationdesign-review

by recued-core pinned v1

Reply to Figma comment with closure watch

Workflow origin for the Figma comment reply closure loop. It reads one Figma file's comments for context, creates exactly one owner-provided reply on an existing comment through recued-core.figma.comment.create, and when the reply succeeds it seeds durable data.shared closure state for figma-comment-reply-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create top-level comments, delete comments, add reactions, mutate files, export images, configure webhooks, or call arbitrary Figma endpoints.

figmacommentscollaborationdesign-review

by recued-core pinned v1

Figma comment reply closure watcher timeout

Background automation

Low-frequency timeout role for recued-core/figma-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.

figmawatchertimeoutowner-review

by recued-core pinned v1

Figma comment reply closure watcher lifecycle review

Owner-visible list/close role for recued-core/figma-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.

figmawatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 123 steps

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

Data fetch

▼ shared_comment_watches ?

▼

Process (122 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 figma has data

■ skip_comment_search any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ comments_raw ?

skip: step.skip_comment_search equal true

■ comments_raw_live_batch_context pick

Keep only specific fields from

■ comments_raw_batch_context_envelopes merge

Combine objects together

■ comments_raw_batch_contexts map

Extract from each item

■ comments default

Apply default

■ comments_live_batch_context pick

Keep only specific fields from

■ comments_batch_context_envelopes merge

Combine objects together

■ comments_batch_contexts map

Extract from each item

■ matched_comment filter

Filter by condition

■ matched_comment_live_batch_context pick

Keep only specific fields from

■ matched_comment_batch_context_envelopes merge

Combine objects together

■ matched_comment_batch_contexts map

Extract from each item

■ live_comment slice

Take a subset of

■ live_comment_live_batch_context pick

Keep only specific fields from

■ live_comment_batch_context_envelopes merge

Combine objects together

■ live_comment_batch_contexts map

Extract from each item

■ has_live_comment compare

Check if item live comment has data

■ has_live_comment_live_batch_context pick

Keep only specific fields from

■ has_live_comment_batch_context_envelopes merge

Combine objects together

■ has_live_comment_batch_contexts map

Extract from each item

■ thread_missing compare

Check if item has live comment does not equal true

■ thread_missing_live_batch_context pick

Keep only specific fields from

■ thread_missing_batch_context_envelopes merge

Combine objects together

■ thread_missing_batch_contexts map

Extract from each item

■ live_resolved_at default

Apply default

■ live_resolved_at_live_batch_context pick

Keep only specific fields from

■ live_resolved_at_batch_context_envelopes merge

Combine objects together

■ live_resolved_at_batch_contexts map

Extract from each item

■ thread_resolved compare

Check if item live resolved at has data

■ thread_resolved_live_batch_context pick

Keep only specific fields from

■ thread_resolved_batch_context_envelopes merge

Combine objects together

■ thread_resolved_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_missing_enabled compare

Check if setting notify when missing equals true

■ notify_missing_enabled_live_batch_context pick

Keep only specific fields from

■ notify_missing_enabled_batch_context_envelopes merge

Combine objects together

■ notify_missing_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_missing all

Check if all conditions are true

■ should_notify_missing_live_batch_context pick

Keep only specific fields from

■ should_notify_missing_batch_context_envelopes merge

Combine objects together

■ should_notify_missing_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.

figma setting =

channels setting = in_app

batch limit setting = 5

notify when missing 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 Figma 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

123 steps 5 configurable settings recipe_id: figma-comment-reply-closure-watcher

Figma comment reply closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details