Use “Zendesk view ticket digest” in Recued. It provides a scheduled, read-only digest for one Zendesk view.

How it works 14 steps

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

Process (14 steps)

◆ agent recued-core.zendesk.user.current

Current user on zendesk

◆ view recued-core.zendesk.view.read

Read view on zendesk

◆ rows_raw recued-core.zendesk.view.execute

Execute view on zendesk

■ 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 core.notification.send

Send notification

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

▼

Output

summary card

table ticket_table

Settings 7 configurable

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

view id setting = [object Object]

channels setting = [object Object]

end hour setting = 10

weekdays setting = 1,2,3,4,5

row limit setting = 25

start hour setting = 8

notify when tickets setting = true