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

Canva comment reply closure watcher

by recued-core v1

Scheduled adopter for Canva comment reply closure rows seeded by reply-canva-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Canva preview comment thread, and closes the shared row when Canva reports that thread resolved. It can notify the owner on resolution, but it never replies to comments, resolves or deletes comment threads, mutates designs, exports files, creates webhooks, or calls arbitrary Canva endpoints.

Complete workflow

Canva Comment Reply Closure Loop 4 pinned recipes

Workflow pack for Recued-sent Canva comment replies. It composes the Canva capability pack with a closure ledger: reply once to an existing Canva preview comment thread through the existing approval gate, persist only the connection/design/thread/reply linkage in data.shared, and let a scheduled watcher re-read that exact thread until Canva reports it resolved. This pack does not replace Canva comments, native notifications, comment resolution, design review dashboards, webhook administration, or general design 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.

Canva comment reply closure watcher

This recipe Background automation

canvacommentscollaborationcreative-review

by recued-core pinned v1

Reply to Canva comment with closure watch

Workflow origin for the Canva comment reply closure loop. It reads one preview Canva comment thread and reply page for context, creates exactly one owner-provided plaintext reply through recued-core.canva.comment.reply.create, and when the reply succeeds it seeds durable data.shared closure state for canva-comment-reply-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create comment threads, resolve or delete comments, mutate designs, export files, configure webhooks, or call arbitrary Canva endpoints.

canvacommentscollaborationcreative-review

by recued-core pinned v1

Canva comment reply closure watcher timeout

Background automation

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

canvawatchertimeoutowner-review

by recued-core pinned v1

Canva comment reply closure watcher lifecycle review

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

canvawatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 75 steps

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

Data fetch

▼ shared_comment_watches ?

▼

Process (74 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_design filter

Filter by condition

■ watch_rows_with_thread 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 thread

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting canva has data

■ skip_thread_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ thread ?

skip: step.skip_thread_read equal true

■ thread_live_batch_context pick

Keep only specific fields from

■ thread_batch_context_envelopes merge

Combine objects together

■ thread_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

■ live_updated_at default

Apply default

■ live_updated_at_live_batch_context pick

Keep only specific fields from

■ live_updated_at_batch_context_envelopes merge

Combine objects together

■ live_updated_at_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_enabled compare

Check if setting notify when resolved equals true

■ notify_enabled_live_batch_context pick

Keep only specific fields from

■ notify_enabled_batch_context_envelopes merge

Combine objects together

■ notify_enabled_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

■ 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 4 configurable

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

canva setting =

channels setting = in_app

batch limit setting = 5

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 Canva 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

75 steps 4 configurable settings recipe_id: canva-comment-reply-closure-watcher

Canva comment reply closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details