Skip to content
Recued
Menu
← Back to recipes

Reply to Help Scout conversation with closure

by recued-core 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.

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.

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

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

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 36 steps

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

Process (36 steps)
conversation_id_value trim
Trim whitespace from setting conversation id
reply_text trim
Trim whitespace from setting reply body
status_value trim
Trim whitespace from setting status after reply
reason_text trim
Trim whitespace from setting reason
has_reply compare
Check if reply text has data
has_status compare
Check if status value has data
conversation ?
threads ?
has_customer_id compare
Check if conversation result primaryCustomer id has data
skip_public_reply any
Check if any of the conditions are true
public_reply ?
skip: step.skip_public_reply equal true
previous_status default
Apply default
reply_write_http_status default
Apply default
requested_status default
Apply default
replied_conversation_id_primary 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_closure_seed any
Check if any of the conditions are true
closure_timeout_at date_add
Add setting no response timeout days days to
seed_helpscout_reply_closure_watch ?
skip: step.skip_closure_seed equal true
thread_count count
Count items in threads result
skipped compare
Check if skip public reply equals true
card to_summary
Format results as a summary card
Settings 6 configurable

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

reason setting =
helpscout setting =
reply body setting =
conversation id setting =
status after reply setting = pending
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.

Where it runs

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

Permissions it requires

Read your Helpscout connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

helpscout helpscoutsupporthelpdeskconversationreplyapprovalcustomer-serviceclosed-loopstate:helpscout-conversation-reply-closure-watcherpack:helpscout-conversation-reply-closure

Details

36 steps 6 configurable settings recipe_id: reply-helpscout-conversation-with-closure