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.
Front conversation reply reopen watcher timeout
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.
Complete workflow
Front Conversation Reply Reopen Loop
5 pinned recipes
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.
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.
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.
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.
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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
active_watches
?
▼
Process (15 steps)
now
date_add
Add 0 minutes to
rows_with_timeout
filter
Filter by condition
timeout_checks
is_past
Check if is in the past
expired_checks
filter
Filter by condition
expired_rows
map
Extract from each item
timeout_rows
slice
Take a subset of
timeout_count
count
Count items in timeout rows
timeout_keys
replace
Replace text in item key
timeout_values
merge
Combine objects together
write_timed_out
?
delete_active
?
skip: item.result.ok not_equal true
moved_rows
filter
Filter by condition
moved_count
count
Count items in moved rows
notify_owner
?
skip: step.moved_rows is_empty
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
in_app
batch limit
setting
=
25
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.