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.
Send Zendesk ticket reply with closure
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.
Complete workflow
Zendesk Ticket Reply Closure Loop
5 pinned recipes
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.
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 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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (35 steps)
ticket_id_value
trim
Trim whitespace from setting ticket id
reply_text
trim
Trim whitespace from setting reply body
status_value
trim
Trim whitespace from setting status after reply
reason_text
trim
Trim whitespace from setting reason
has_reply
compare
Check if reply text has data
has_status
compare
Check if status value has data
ticket
?
skip_status_reply
any
Check if any of the conditions are true
skip_reply_only
any
Check if any of the conditions are true
reply_with_status
?
skip: step.skip_status_reply equal true
reply_only
?
skip: step.skip_reply_only equal true
updated_ticket
ternary
Apply ternary
updated_ticket_id
default
Apply default
has_updated_ticket
compare
Check if updated ticket id has data
requested_status
default
Apply default
requested_status_norm
lowercase
Convert requested status to lowercase
previous_status_norm
lowercase
Convert ticket result status to lowercase
replied_at
date_add
Add 0 days to
ticket_key_seed
default
Apply default
raw_ticket_key
join
Join items with ":"
ticket_key_colon
replace
Replace text in raw ticket key
ticket_key_slash
replace
Replace text in ticket key colon
ticket_key_dot
replace
Replace text in ticket key slash
ticket_key_at
replace
Replace text in ticket key dot
ticket_key_space
replace
Replace text in ticket key at
ticket_key_left_angle
replace
Replace text in ticket key space
ticket_key_right_angle
replace
Replace text in ticket key left angle
ticket_key_plus
replace
Replace text in ticket key right angle
ticket_key_equals
replace
Replace text in ticket key plus
ticket_key_question
replace
Replace text in ticket 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_zendesk_reply_closure_watch
?
skip: step.skip_closure_seed equal true
skipped
compare
Check if has reply does not equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
reason
setting
=
zendesk
setting
=
ticket id
setting
=
reply body
setting
=
status after reply
setting
=
pending
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.