Name: Zendesk ticket reply closure watcher
Author: recued-core

Zendesk ticket reply closure watcher

by recued-core v1

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.

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.

Zendesk ticket reply closure watcher

This recipe Background automation

zendesksupportticketreply

by recued-core pinned v1

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.

zendesksupportticketreply

by recued-core pinned v1

Zendesk ticket review brief

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.

zendesksupportticketcomments

by recued-core pinned v1

Zendesk ticket reply closure watcher timeout

Background automation

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.

zendeskwatchertimeoutowner-review

by recued-core pinned v1

Zendesk ticket reply closure watcher lifecycle review

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.

zendeskwatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 102 steps

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

Data fetch

▼ shared_ticket_watches ?

▼

Process (101 steps)

■ now date_add

Add 0 days to

■ watch_rows filter

Filter by condition

■ watch_rows_for_connection filter

Filter by condition

■ watch_rows_with_ticket filter

Filter by condition

■ never_checked_watch_rows filter

Filter by condition

■ checked_watch_rows filter

Filter by condition

■ checked_watch_rows_oldest_first sort

Sort by value.last_checked_at

■ fair_watch_rows flatten

Flatten nested lists in

■ candidate_rows slice

Take a subset of

■ batch_count count

Count items in candidate rows

■ candidate_count count

Count items in watch rows with ticket

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting zendesk has data

■ skip_ticket_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ ticket ?

skip: step.skip_ticket_read equal true

■ ticket_live_batch_context pick

Keep only specific fields from

■ ticket_batch_context_envelopes merge

Combine objects together

■ ticket_batch_contexts map

Extract from each item

■ live_status default

Apply default

■ live_status_live_batch_context pick

Keep only specific fields from

■ live_status_batch_context_envelopes merge

Combine objects together

■ live_status_batch_contexts map

Extract from each item

■ live_status_norm lowercase

Convert item live status to lowercase

■ live_status_norm_live_batch_context pick

Keep only specific fields from

■ live_status_norm_batch_context_envelopes merge

Combine objects together

■ live_status_norm_batch_contexts map

Extract from each item

■ closure_status compare

Check if item live status norm is one of setting closure statuses

■ closure_status_live_batch_context pick

Keep only specific fields from

■ closure_status_batch_context_envelopes merge

Combine objects together

■ closure_status_batch_contexts map

Extract from each item

■ needs_owner_review compare

Check if item live status norm is one of setting owner review statuses

■ needs_owner_review_live_batch_context pick

Keep only specific fields from

■ needs_owner_review_batch_context_envelopes merge

Combine objects together

■ needs_owner_review_batch_contexts map

Extract from each item

■ still_waiting compare

Check if item live status norm is one of setting waiting statuses

■ still_waiting_live_batch_context pick

Keep only specific fields from

■ still_waiting_batch_context_envelopes merge

Combine objects together

■ still_waiting_batch_contexts map

Extract from each item

■ actionable_status any

Check if any of the conditions are true

■ actionable_status_live_batch_context pick

Keep only specific fields from

■ actionable_status_batch_context_envelopes merge

Combine objects together

■ actionable_status_batch_contexts map

Extract from each item

■ closed_status ternary

Apply ternary

■ closed_status_live_batch_context pick

Keep only specific fields from

■ closed_status_batch_context_envelopes merge

Combine objects together

■ closed_status_batch_contexts map

Extract from each item

■ owner_action ternary

Apply ternary

■ owner_action_live_batch_context pick

Keep only specific fields from

■ owner_action_batch_context_envelopes merge

Combine objects together

■ owner_action_batch_contexts map

Extract from each item

■ skip_close any

Check if any of the conditions are true

■ skip_close_live_batch_context pick

Keep only specific fields from

■ skip_close_batch_context_envelopes merge

Combine objects together

■ skip_close_batch_contexts map

Extract from each item

■ closed_watch_key replace

Replace text in item watch key

■ closed_watch_key_live_batch_context pick

Keep only specific fields from

■ closed_watch_key_batch_context_envelopes merge

Combine objects together

■ closed_watch_key_batch_contexts map

Extract from each item

■ close_watch ?

skip: item.skip_close equal true

■ close_watch_live_batch_context pick

Keep only specific fields from

■ close_watch_batch_context_envelopes merge

Combine objects together

■ close_watch_batch_contexts map

Extract from each item

■ delete_closed_active_watch ?

skip: item.close_watch.ok not_equal true

■ delete_closed_active_watch_live_batch_context pick

Keep only specific fields from

■ delete_closed_active_watch_batch_context_envelopes merge

Combine objects together

■ delete_closed_active_watch_batch_contexts map

Extract from each item

■ notify_closed_enabled compare

Check if setting notify when closed equals true

■ notify_closed_enabled_live_batch_context pick

Keep only specific fields from

■ notify_closed_enabled_batch_context_envelopes merge

Combine objects together

■ notify_closed_enabled_batch_contexts map

Extract from each item

■ notify_review_enabled compare

Check if setting notify when owner review equals true

■ notify_review_enabled_live_batch_context pick

Keep only specific fields from

■ notify_review_enabled_batch_context_envelopes merge

Combine objects together

■ notify_review_enabled_batch_contexts map

Extract from each item

■ notify_enabled ternary

Apply ternary

■ notify_enabled_live_batch_context pick

Keep only specific fields from

■ notify_enabled_batch_context_envelopes merge

Combine objects together

■ notify_enabled_batch_contexts map

Extract from each item

■ should_notify all

Check if all conditions are true

■ should_notify_live_batch_context pick

Keep only specific fields from

■ should_notify_batch_context_envelopes merge

Combine objects together

■ should_notify_batch_contexts map

Extract from each item

■ notify_owner ?

skip: item.should_notify not_equal true

■ notify_owner_live_batch_context pick

Keep only specific fields from

■ notify_owner_batch_context_envelopes merge

Combine objects together

■ notify_owner_batch_contexts map

Extract from each item

■ refreshed_watch_value merge

Combine objects together

skip: item.delete_closed_active_watch.ok equal true

■ refreshed_watch_value_live_batch_context pick

Keep only specific fields from

■ refreshed_watch_value_batch_context_envelopes merge

Combine objects together

■ refreshed_watch_value_batch_contexts map

Extract from each item

■ refresh_active_watch ?

skip: item.delete_closed_active_watch.ok equal true

■ refresh_active_watch_live_batch_context pick

Keep only specific fields from

■ refresh_active_watch_batch_context_envelopes merge

Combine objects together

■ refresh_active_watch_batch_contexts map

Extract from each item

■ closed_batch_rows filter

Filter by condition

■ refreshed_batch_rows filter

Filter by condition

■ closed_batch_count count

Count items in closed batch rows

■ refreshed_batch_count count

Count items in refreshed batch rows

■ summary to_summary

Format results as a summary card

Settings 8 configurable

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

zendesk setting =

channels setting = in_app

batch limit setting = 5

closure statuses setting = solved,closed

waiting statuses setting = pending,hold,on-hold

notify when closed setting = true

owner review statuses setting = new,open

notify when owner review setting = true

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

Send notificationsRead your Zendesk connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

recued-core

Details

102 steps 8 configurable settings recipe_id: zendesk-ticket-reply-closure-watcher

Zendesk ticket reply closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details