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.
Reply to Front conversation with reopen watch
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.
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.
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.
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.
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.
Process (33 steps)
conversation_id_value
trim
Trim whitespace from setting conversation id
reply_text
trim
Trim whitespace from setting reply body
reason_text
trim
Trim whitespace from setting reason
has_reply
compare
Check if reply text has data
conversation
?
events_before_raw
?
events_before
default
Apply default
baseline_event_id
default
Apply default
baseline_event_type
default
Apply default
skip_public_reply
compare
Check if has reply does not equal true
public_reply
?
skip: step.skip_public_reply equal true
previous_status
default
Apply default
previous_status_category
default
Apply default
replied_conversation_id
default
Apply default
has_replied_conversation
compare
Check if replied conversation id has data
replied_at
date_add
Add 0 days to
conversation_key_seed
default
Apply default
raw_conversation_key
join
Join items with ":"
conversation_key_colon
replace
Replace text in raw conversation key
conversation_key_slash
replace
Replace text in conversation key colon
conversation_key_dot
replace
Replace text in conversation key slash
conversation_key_at
replace
Replace text in conversation key dot
conversation_key_space
replace
Replace text in conversation key at
conversation_key_left_angle
replace
Replace text in conversation key space
conversation_key_right_angle
replace
Replace text in conversation key left angle
conversation_key_plus
replace
Replace text in conversation key right angle
conversation_key_equals
replace
Replace text in conversation key plus
conversation_key_question
replace
Replace text in conversation key equals
skip_reopen_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_front_reopen_watch
?
skip: step.skip_reopen_seed equal true
skipped
compare
Check if skip public reply equals true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
front
setting
=
reason
setting
=
reply body
setting
=
conversation id
setting
=
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.