Skip to content
Recued
Menu
← Back to recipes

Front conversation reply reopen watcher lifecycle review

by recued-core v1

Owner-visible list/close role for recued-core/front-conversation-reply-reopen. 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

Workflow pack for Recued-sent Front customer replies. It composes the Front capability pack with a reopen ledger: send one customer reply through the existing Front approval gate, persist only the connection/conversation/event-baseline linkage in data.shared, and let a scheduled watcher re-read that exact conversation and latest events until Front reports archived/spam/trashed/deleted, a resolved ticket category, or a newer owner-actionable event such as inbound, reopen, or delivery error. This pack does not replace Front Rules, reminders, time-goal rules, required tagging, native notifications, inbox routing, webhooks, application triggers, or teammate workflows; it adds Recued-visible closure/reopen state for conversations Recued replied to.

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

Owner-visible list/close role for recued-core/front-conversation-reply-reopen. 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.

frontwatcherreviewclose
by recued-core pinned v1

Workflow origin for the Front conversation reply reopen loop. It reads one conversation and its latest event, sends exactly one owner-provided customer reply through recued-core.front.conversation.reply, and when the approved reply operation succeeds it seeds durable data.shared state for front-conversation-reply-reopen-watcher. It uses user-configured deterministic copy rather than AI and does not archive conversations, change ticket status, create internal comments, mutate tags or custom fields, configure Front Rules, create reminders, alter inbox/admin settings, create webhooks or application triggers, delete records, upload attachments, bulk mutate, or call arbitrary Front endpoints.

frontsupportshared-inboxconversation
by recued-core pinned v1

Scheduled adopter for Front conversation reply reopen rows seeded by reply-front-conversation-with-reopen-watch. It lists only Recued-originated public-reply watches, re-reads a bounded batch of Front conversation and its latest events, and closes or flags the shared row when Front reports a terminal status, resolved ticket category, newer customer-return event, reopen event, or delivery error. It can notify the owner on closure or owner-actionable states, but it never updates conversations, sends replies, creates comments, creates reminders, mutates tags or custom fields, creates or edits Front Rules, changes inbox/admin settings, creates webhooks or application triggers, deletes records, bulk mutates, or calls arbitrary Front endpoints.

frontsupportshared-inboxconversation
by recued-core pinned v1

Read-only AI-assisted brief for one Front conversation. It reads conversation metadata, messages, internal comments, events, followers, and inboxes through recued-core.front, then summarizes customer context, issue state, suggested next reply, and operational follow-ups. It never sends replies, posts comments, changes status, tags, assignees, contacts, or knowledge base content.

frontconversationsupportcustomer-service
by recued-core pinned v1

Low-frequency timeout role for recued-core/front-conversation-reply-reopen. 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.

frontwatchertimeoutowner-review
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 13 steps

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_front-conversation-reply-reopen.timed_out.
close_is_closed starts_with
Check if close key starts with data.shared.recipe.recued-core_front-conversation-reply-reopen.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 2 configurable

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.

Where it runs

Device + server Runs on your device (browser) or your server.

Data it touches

Warehousedata.shared

About

Tags

front watcherreviewcloseclosed-looprole:reviewrole:closebundle:front-conversation-reply-reopen

Details

13 steps 2 configurable settings recipe_id: review-front-conversation-reply-reopen-lifecycle