Skip to content
Recued
Menu
← Back to recipes

Help Scout conversation reply closure watcher timeout

by recued-core v1

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

Complete workflow

Workflow pack for Recued-sent Help Scout public replies. It composes the Help Scout capability pack with a closure ledger: send one public conversation reply through the existing Help Scout approval gate, set a configured Help Scout status such as pending in the same reply, persist only the connection/conversation reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact conversation until Help Scout reports closed/spam or an owner-actionable status such as active/open. This pack does not replace Help Scout Workflows, manual workflows, inbox rules, mailbox/admin settings, webhook automation, native notifications, or helpdesk queue rules; it adds Recued-visible closure 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.

Help Scout conversation reply closure watcher timeout
This recipe Background automation

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

helpscoutwatchertimeoutowner-review
by recued-core pinned v1

Workflow origin for the Help Scout conversation reply closure loop. It reads one conversation and thread page, creates exactly one owner-provided customer-visible reply through recued-core.helpscout.conversation.reply.create, sets a user-configured Help Scout status in that same reply call, and when the reply succeeds it seeds durable data.shared closure state for helpscout-conversation-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create conversations, create internal notes, mutate tags or custom fields, run Help Scout Workflows, change mailbox/admin settings, create or edit webhooks, delete records, upload attachments, bulk mutate, or call arbitrary Help Scout endpoints.

helpscoutsupporthelpdeskconversation
by recued-core pinned v1

Scheduled adopter for Help Scout conversation reply closure rows seeded by reply-helpscout-conversation-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of conversation from Help Scout, and closes or flags the shared row when Help Scout reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates conversations, replies to customers, creates internal notes, creates or edits Help Scout Workflows, changes mailbox/admin settings, creates webhooks, deletes records, bulk mutates, or calls arbitrary Help Scout endpoints.

helpscoutsupporthelpdeskconversation
by recued-core pinned v1

Read-only AI-assisted review brief for one Help Scout conversation. It reads the conversation, its thread history, primary customer profile, and team context through recued-core.helpscout, then summarizes customer ask, latest state, sentiment, support risk, and next response. It never replies, notes, updates tags or custom fields, mutates users or inbox settings, downloads attachments, deletes, bulk-mutates, runs workflows, or calls arbitrary Help Scout endpoints.

helpscoutsupporthelpdeskconversation
by recued-core pinned v1

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

helpscoutwatcherreviewclose
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 16 steps

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 2 configurable

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.

Where it runs

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

Permissions it requires

Send notifications
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

helpscout watchertimeoutowner-reviewclosed-looprole:timeoutbundle:helpscout-conversation-reply-closure

Details

16 steps 2 configurable settings recipe_id: timeout-helpscout-conversation-reply-closure-watches