Owner-visible list/close role for recued-core/freshdesk-ticket-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.
Freshdesk ticket reply closure watcher lifecycle review
Owner-visible list/close role for recued-core/freshdesk-ticket-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.
Complete workflow
Workflow pack for Recued-sent Freshdesk public replies. It composes the Freshdesk capability pack with a closure ledger: send one public ticket reply through the existing Freshdesk approval gate, optionally set a configured Freshdesk numeric status such as Pending, persist only the connection/ticket reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact ticket until Freshdesk reports Resolved/Closed or an owner-actionable status such as Open. This pack does not replace Freshdesk automations, dispatch rules, Observer/Supervisor rules, SLA policy, ticket views, native notifications, or helpdesk queue rules; it adds Recued-visible closure state for tickets 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 Freshdesk ticket reply closure loop. It reads one ticket and its conversation context, creates exactly one owner-provided public reply through recued-core.freshdesk.ticket.reply.create, optionally updates that same ticket to a user-configured Freshdesk numeric status, and when the reply succeeds it seeds durable data.shared closure state for freshdesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create private notes, delete, bulk update, attach files, mutate contacts or companies, change automations/dispatch rules/SLA/admin settings, or call arbitrary Freshdesk endpoints.
Scheduled adopter for Freshdesk ticket reply closure rows seeded by reply-freshdesk-ticket-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Freshdesk, and closes or flags the shared row when Freshdesk reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates tickets, replies to customers, creates private notes, creates or edits automations/dispatch rules/SLA/admin settings, deletes records, or calls arbitrary Freshdesk endpoints.
Read-only AI-assisted review brief for one Freshdesk ticket. It reads the ticket, full conversation list, requester contact when available, company when available, time entries, and matching solution articles through recued-core.freshdesk, then summarizes the customer ask, urgency, history, support risk, and next response. It never replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.
Low-frequency timeout role for recued-core/freshdesk-ticket-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.
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.
close key
setting
=
row limit
setting
=
50
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.