Recued
Menu
← Back to recipes

Front inbox triage digest

by recued-core v2 10 views

Use “Front inbox triage digest” in Recued. It provides a scheduled, read-only triage digest for one Front inbox.

How it works 17 steps

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

Process (17 steps)
inbox ?
conversations_raw ?
teammates_raw ?
tags_raw ?
defaults defaults
Apply defaults
conversation_count count
Count items in conversations
teammate_count count
Count items in teammates
tag_count count
Count items in tags
has_conversations compare
Check if conversation count is greater than 0
notify_enabled compare
Check if setting notify when conversations equals true
should_notify all
Check if all conditions are true
notify ?
skip: step.should_notify not_equal true
conversation_rows slice
Take a subset of
tag_rows slice
Take a subset of
conversation_table to_table
Format results as a data table
tag_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 9 configurable

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

front setting =
channels setting = in_app
end hour setting = 10
inbox id setting = [object Object]
weekdays setting = 1,2,3,4,5
row limit setting = 20
start hour setting = 8
conversation query setting =
notify when conversations setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Send notificationsRead your Front connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

front frontinboxsupportconversationsdigestcustomer-serviceshared-inboxpack:front

Details

17 steps 9 configurable settings recipe_id: inbox-triage-digest-front