Use “Reply to Help Scout conversation with closure” in Recued. It carries out the named workflow using the connections and settings you choose.
Reply to Help Scout conversation with closure
Use “Reply to Help Scout conversation with closure” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Help Scout Conversation Reply Closure Loop
5 pinned recipes
Use Help Scout Conversation Reply Closure Loop in Recued for support, helpdesk, closed loop, and state helpscout conversation reply closure watcher. It includes 3 ready-to-run workflows and 1 related pack in one install.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Help Scout conversation reply closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.
Use “Help Scout conversation review brief” in Recued. It provides a read-only AI-assisted review brief for one Help Scout conversation.
Use “Help Scout conversation reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Use “Help Scout conversation reply closure watcher lifecycle review” in Recued. It carries out the named workflow using the connections and settings you choose.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (34 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
defaults
defaults
Apply defaults
defaults_2
defaults
Apply defaults
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
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.