Freshdesk ticket triage digest
Scheduled read-only digest for a Freshdesk support queue. It reads the current agent, groups, matching tickets, ticket fields, and matching solution articles through recued-core.freshdesk, renders compact support tables, and can send an in-app nudge when matching tickets exist. It never creates, replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (22 steps)
ticket_query
trim
Trim whitespace from setting ticket query
article_term
trim
Trim whitespace from setting article term
agent
?
groups_raw
?
tickets_raw
?
fields_raw
?
articles_raw
?
tickets
default
Apply default
groups
default
Apply default
fields
default
Apply default
articles
default
Apply default
ticket_rows
slice
Take a subset of
article_rows
slice
Take a subset of
ticket_count
count
Count items in tickets
group_count
count
Count items in groups
field_count
count
Count items in fields
has_tickets
compare
Check if ticket count is greater than 0
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
ticket_table
to_table
Format results as a data table
article_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
freshdesk
setting
=
row limit
setting
=
25
start hour
setting
=
8
article term
setting
=
billing login refund
ticket query
setting
=
(status:2 OR status:3)
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.