Skip to content
Recued
Menu
← Back to recipes

Zendesk view ticket digest

by recued-core v1

Scheduled read-only digest for one Zendesk view. It reads the current agent, view metadata, and a bounded page of view rows through recued-core.zendesk, renders a compact table, and can send an in-app nudge when tickets are visible. It does not create, update, delete, bulk update, attach files, redact comments, execute macros, change admin settings, or call arbitrary Zendesk endpoints.

How it works 14 steps

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

Process (14 steps)
agent ?
view ?
rows_raw ?
rows default
Apply default
ticket_count count
Count items in rows
has_tickets compare
Check if ticket count is greater than 0
notify_enabled compare
Check if setting notify when tickets equals true
should_notify all
Check if all conditions are true
notify ?
skip: step.should_notify not_equal true
ticket_rows slice
Take a subset of
ticket_subjects pluck
Extract subject from each item
ticket_subjects_text join
Join items with " "
ticket_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 8 configurable

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

view id setting =
zendesk setting =
channels setting = in_app
end hour setting = 10
weekdays setting = 1,2,3,4,5
row limit setting = 25
start hour setting = 8
notify when tickets 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.

About

Tags

zendesk zendesksupportticketsviewsdigestschedulenotificationpack:zendesk

Details

14 steps 8 configurable settings recipe_id: zendesk-view-ticket-digest