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.
Reply to Intercom conversation with closure watch
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.
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.
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.
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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
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.