Approval-gated Zendesk ticket reply for one ticket. It reads the ticket for context, then updates exactly one ticket with a public reply or internal note and can optionally set a status. It does not create tickets, delete, bulk update, attach files, redact comments, execute macros, change admin settings, or call arbitrary Zendesk endpoints.

How it works 12 steps

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

Process (12 steps)

■ reply_body trim

Trim whitespace from setting reply body

■ status trim

Trim whitespace from setting status

■ has_reply compare

Check if reply body has data

■ has_status compare

Check if status 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

■ skipped compare

Check if has reply does not equal true

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

status setting =

zendesk setting =

ticket id setting =

reply body setting =

public reply setting = true