Approval-gated Help Scout reply workflow. It reads the target conversation and thread history for context, then adds exactly one customer-visible reply or one internal note through recued-core.helpscout. It does not create conversations, update tags or custom fields, mutate customers or users, download or upload attachments, delete, bulk-mutates, run workflows, change inbox/admin settings, or call arbitrary Help Scout endpoints.

How it works 13 steps

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

Process (13 steps)

■ reply_text trim

Trim whitespace from setting body text

■ has_body compare

Check if reply text 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

■ skip_internal_note any

Check if any of the conditions are true

■ public_reply_created ?

skip: step.skip_public_reply equal true

■ internal_note ?

skip: step.skip_internal_note equal true

■ thread_count count

Count items in threads result

■ created_thread ternary

Apply ternary

■ skipped all

Check if all conditions are true

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

draft setting = false

body text setting =

helpscout setting =

public reply setting = true

conversation id setting =