Name: Help Scout conversation reply closure watcher
Author: recued-core

Help Scout conversation reply closure watcher

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

Complete workflow

Help Scout Conversation Reply Closure Loop 5 pinned recipes

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

This recipe Background automation

helpscoutsupporthelpdeskconversation

by recued-core pinned v1

Reply to Help Scout conversation with closure

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

Help Scout conversation review brief

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

Help Scout conversation reply closure watcher timeout

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

Help Scout conversation reply closure watcher lifecycle review

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

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

Data fetch

▼ shared_conversation_watches ?

▼

Process (121 steps)

■ now date_add

Add 0 days to

■ watch_rows filter

Filter by condition

■ watch_rows_for_connection filter

Filter by condition

■ watch_rows_with_conversation filter

Filter by condition

■ never_checked_watch_rows filter

Filter by condition

■ checked_watch_rows filter

Filter by condition

■ checked_watch_rows_oldest_first sort

Sort by value.last_checked_at

■ fair_watch_rows flatten

Flatten nested lists in

■ candidate_rows slice

Take a subset of

■ batch_count count

Count items in candidate rows

■ candidate_count count

Count items in watch rows with conversation

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting helpscout has data

■ skip_conversation_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ conversation ?

skip: step.skip_conversation_read equal true

■ conversation_live_batch_context pick

Keep only specific fields from

■ conversation_batch_context_envelopes merge

Combine objects together

■ conversation_batch_contexts map

Extract from each item

■ live_status default

Apply default

■ live_status_live_batch_context pick

Keep only specific fields from

■ live_status_batch_context_envelopes merge

Combine objects together

■ live_status_batch_contexts map

Extract from each item

■ live_status_text lowercase

Convert item live status to lowercase

■ live_status_text_live_batch_context pick

Keep only specific fields from

■ live_status_text_batch_context_envelopes merge

Combine objects together

■ live_status_text_batch_contexts map

Extract from each item

■ closure_status compare

Check if item live status text is one of setting closure statuses

■ closure_status_live_batch_context pick

Keep only specific fields from

■ closure_status_batch_context_envelopes merge

Combine objects together

■ closure_status_batch_contexts map

Extract from each item

■ needs_owner_review compare

Check if item live status text is one of setting owner review statuses

■ needs_owner_review_live_batch_context pick

Keep only specific fields from

■ needs_owner_review_batch_context_envelopes merge

Combine objects together

■ needs_owner_review_batch_contexts map

Extract from each item

■ still_waiting compare

Check if item live status text is one of setting waiting statuses

■ still_waiting_live_batch_context pick

Keep only specific fields from

■ still_waiting_batch_context_envelopes merge

Combine objects together

■ still_waiting_batch_contexts map

Extract from each item

■ actionable_status any

Check if any of the conditions are true

■ actionable_status_live_batch_context pick

Keep only specific fields from

■ actionable_status_batch_context_envelopes merge

Combine objects together

■ actionable_status_batch_contexts map

Extract from each item

■ closed_status ternary

Apply ternary

■ closed_status_live_batch_context pick

Keep only specific fields from

■ closed_status_batch_context_envelopes merge

Combine objects together

■ closed_status_batch_contexts map

Extract from each item

■ owner_review_owner_action_text trim

Trim whitespace from setting owner review owner action

■ owner_review_owner_action_text_live_batch_context pick

Keep only specific fields from

■ owner_review_owner_action_text_batch_context_envelopes merge

Combine objects together

■ owner_review_owner_action_text_batch_contexts map

Extract from each item

■ closed_owner_action_text trim

Trim whitespace from setting closed owner action

■ closed_owner_action_text_live_batch_context pick

Keep only specific fields from

■ closed_owner_action_text_batch_context_envelopes merge

Combine objects together

■ closed_owner_action_text_batch_contexts map

Extract from each item

■ owner_action ternary

Apply ternary

■ owner_action_live_batch_context pick

Keep only specific fields from

■ owner_action_batch_context_envelopes merge

Combine objects together

■ owner_action_batch_contexts map

Extract from each item

■ skip_close any

Check if any of the conditions are true

■ skip_close_live_batch_context pick

Keep only specific fields from

■ skip_close_batch_context_envelopes merge

Combine objects together

■ skip_close_batch_contexts map

Extract from each item

■ closed_watch_key replace

Replace text in item watch key

■ closed_watch_key_live_batch_context pick

Keep only specific fields from

■ closed_watch_key_batch_context_envelopes merge

Combine objects together

■ closed_watch_key_batch_contexts map

Extract from each item

■ close_watch ?

skip: item.skip_close equal true

■ close_watch_live_batch_context pick

Keep only specific fields from

■ close_watch_batch_context_envelopes merge

Combine objects together

■ close_watch_batch_contexts map

Extract from each item

■ delete_closed_active_watch ?

skip: item.close_watch.ok not_equal true

■ delete_closed_active_watch_live_batch_context pick

Keep only specific fields from

■ delete_closed_active_watch_batch_context_envelopes merge

Combine objects together

■ delete_closed_active_watch_batch_contexts map

Extract from each item

■ notify_closed_enabled compare

Check if setting notify when closed equals true

■ notify_closed_enabled_live_batch_context pick

Keep only specific fields from

■ notify_closed_enabled_batch_context_envelopes merge

Combine objects together

■ notify_closed_enabled_batch_contexts map

Extract from each item

■ notify_review_enabled compare

Check if setting notify when owner review equals true

■ notify_review_enabled_live_batch_context pick

Keep only specific fields from

■ notify_review_enabled_batch_context_envelopes merge

Combine objects together

■ notify_review_enabled_batch_contexts map

Extract from each item

■ notify_enabled ternary

Apply ternary

■ notify_enabled_live_batch_context pick

Keep only specific fields from

■ notify_enabled_batch_context_envelopes merge

Combine objects together

■ notify_enabled_batch_contexts map

Extract from each item

■ notification_title_prefix_text trim

Trim whitespace from setting notification title prefix

■ notification_title_prefix_text_live_batch_context pick

Keep only specific fields from

■ notification_title_prefix_text_batch_context_envelopes merge

Combine objects together

■ notification_title_prefix_text_batch_contexts map

Extract from each item

■ notification_title concat

Combine text or lists together

■ notification_title_live_batch_context pick

Keep only specific fields from

■ notification_title_batch_context_envelopes merge

Combine objects together

■ notification_title_batch_contexts map

Extract from each item

■ notification_text concat

Combine text or lists together

■ notification_text_live_batch_context pick

Keep only specific fields from

■ notification_text_batch_context_envelopes merge

Combine objects together

■ notification_text_batch_contexts map

Extract from each item

■ should_notify all

Check if all conditions are true

■ should_notify_live_batch_context pick

Keep only specific fields from

■ should_notify_batch_context_envelopes merge

Combine objects together

■ should_notify_batch_contexts map

Extract from each item

■ notify_owner ?

skip: item.should_notify not_equal true

■ notify_owner_live_batch_context pick

Keep only specific fields from

■ notify_owner_batch_context_envelopes merge

Combine objects together

■ notify_owner_batch_contexts map

Extract from each item

■ refreshed_watch_value merge

Combine objects together

skip: item.delete_closed_active_watch.ok equal true

■ refreshed_watch_value_live_batch_context pick

Keep only specific fields from

■ refreshed_watch_value_batch_context_envelopes merge

Combine objects together

■ refreshed_watch_value_batch_contexts map

Extract from each item

■ refresh_active_watch ?

skip: item.delete_closed_active_watch.ok equal true

■ refresh_active_watch_live_batch_context pick

Keep only specific fields from

■ refresh_active_watch_batch_context_envelopes merge

Combine objects together

■ refresh_active_watch_batch_contexts map

Extract from each item

■ closed_batch_rows filter

Filter by condition

■ refreshed_batch_rows filter

Filter by condition

■ closed_batch_count count

Count items in closed batch rows

■ refreshed_batch_count count

Count items in refreshed batch rows

■ summary to_summary

Format results as a summary card

Settings 11 configurable

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

channels setting = in_app

helpscout setting =

batch limit setting = 5

closure statuses setting = closed,spam

waiting statuses setting = pending

notify when closed setting = true

closed owner action setting = Conversation reached a Help Scout closure status; no further Recued follow-up is open for this conversation.

owner review statuses setting = active,open

notify when owner review setting = true

notification title prefix setting = Help Scout conversation status

owner review owner action setting = Conversation is back in an agent-actionable Help Scout status; review the latest conversation before replying again.

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 notificationsRead your Helpscout connection

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

Data it touches

Warehousedata.shared

About

recued-core

Details

122 steps 11 configurable settings recipe_id: helpscout-conversation-reply-closure-watcher

Help Scout conversation reply closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details