Skip to content
Recued
Menu
← Back to recipes

Reply to Intercom conversation with closure watch

by recued-core v1

Workflow origin for the Intercom conversation reply closure loop. It reads one conversation, sends exactly one owner-provided customer-visible admin comment through recued-core.intercom.conversation.reply, and when the approved reply succeeds it seeds durable data.shared closure state for intercom-conversation-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not add internal notes, close, reopen, snooze, assign, tag, mutate contacts or companies, create or update tickets, configure Intercom Workflows or Rules, create webhooks, delete records, bulk mutate, or call arbitrary Intercom endpoints.

Complete workflow

Workflow pack for Recued-sent Intercom customer replies. It composes the Intercom capability pack with a closure ledger: send one public admin comment through the existing Intercom approval gate, persist only the connection/conversation reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact conversation until Intercom reports a configured closure state or a customer-waiting owner-review signal after the Recued reply. This pack does not replace Intercom Workflows, Rules, snooze/reopen/close automation, assignment/routing, SLAs, native notifications, webhooks, or teammate workflows; 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 Intercom conversation reply closure loop. It reads one conversation, sends exactly one owner-provided customer-visible admin comment through recued-core.intercom.conversation.reply, and when the approved reply succeeds it seeds durable data.shared closure state for intercom-conversation-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not add internal notes, close, reopen, snooze, assign, tag, mutate contacts or companies, create or update tickets, configure Intercom Workflows or Rules, create webhooks, delete records, bulk mutate, or call arbitrary Intercom endpoints.

intercomsupportconversationreply
by recued-core pinned v1

Scheduled adopter for Intercom conversation reply closure rows seeded by reply-intercom-conversation-with-closure-watch. It lists only Recued-originated public-reply watches, re-reads a bounded batch of Intercom conversation, and closes or flags the shared row when Intercom reports configured closure state or customer-waiting owner-review state after the Recued reply. It can notify the owner on closure or owner-actionable customer-return states, but it never replies, adds notes, closes, reopens, snoozes, assigns, tags, mutates contacts or companies, creates or updates tickets, configures Intercom Workflows or Rules, creates webhooks, deletes records, bulk mutates, or calls arbitrary Intercom endpoints.

intercomsupportconversationreply
by recued-core pinned v1

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

intercomwatchertimeoutowner-review
by recued-core pinned v1

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

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

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

Process (40 steps)
conversation_id_value trim
Trim whitespace from setting conversation id
admin_id_value trim
Trim whitespace from setting admin id
reply_text trim
Trim whitespace from setting reply body
reason_text trim
Trim whitespace from setting reason
has_conversation compare
Check if conversation id value has data
has_admin compare
Check if admin id value has data
has_reply compare
Check if reply text has data
conversation ?
skip_public_reply any
Check if any of the conditions are true
public_reply ?
skip: step.skip_public_reply equal true
previous_state default
Apply default
previous_open default
Apply default
previous_waiting_since 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_state default
Apply default
replied_open default
Apply default
replied_waiting_since default
Apply default
replied_updated_at default
Apply default
last_admin_reply_at default
Apply default
last_contact_reply_at default
Apply default
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_intercom_reply_closure_watch ?
skip: step.skip_closure_seed equal true
skipped compare
Check if skip public reply equals true
card to_summary
Format results as a summary card
Settings 8 configurable

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

reason setting =
admin id setting =
intercom setting =
reply body setting =
attachment urls setting =
conversation id setting =
skip notifications setting = false
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 Intercom connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

intercom intercomsupportconversationreplyapprovalcustomer-serviceclosure-watchclosed-loopstate:intercom-conversation-reply-closure-watcherpack:intercom-conversation-reply-closure

Details

40 steps 8 configurable settings recipe_id: reply-intercom-conversation-with-closure-watch