Workflow origin for the Zendesk ticket reply closure loop. It reads one ticket for context, updates exactly that ticket with an owner-provided public reply through recued-core.zendesk.ticket.update, and when the public reply succeeds it seeds durable data.shared closure state for zendesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create internal notes, delete, bulk update, attach files, redact comments, execute macros, create or edit triggers or automations, change SLA/admin settings, or call arbitrary Zendesk endpoints.
Zendesk Ticket Reply Closure Loop
Workflow pack for Recued-sent Zendesk public replies. It composes the Zendesk capability pack with a closure ledger: send one public ticket reply through the existing Zendesk approval gate, persist only the connection/ticket reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact ticket until Zendesk reports solved/closed or an owner-actionable status such as new/open. This pack does not replace Zendesk triggers, automations, views, macros, SLA policy, or helpdesk queue rules; it adds Recued-visible closure state for tickets Recued replied to.
What this pack installs
Included recipes
5 pinned recipes
This pack installs the complete recipe workflow together. 2 supporting recipes run as background automation.
Scheduled adopter for Zendesk ticket reply closure rows seeded by send-zendesk-ticket-reply-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Zendesk, and closes or flags the shared row when Zendesk 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, executes macros, creates or edits triggers or automations, changes SLA/admin settings, redacts comments, deletes records, or calls arbitrary Zendesk endpoints.
Read-only review brief for one Zendesk ticket. It reads ticket details, comments, audits, and ticket metrics through recued-core.zendesk, then asks the AI summarizer for customer ask, status, blockers, owner expectations, and the next response. It never creates, updates, deletes, redacts comments, executes macros, changes admin settings, or calls arbitrary Zendesk endpoints.
Low-frequency timeout role for recued-core/zendesk-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.
Owner-visible list/close role for recued-core/zendesk-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.
Builds on
- zendesk v1+
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.