CUSTOMER SUPPORT
Daily digest pairing top Sentry crashes with their support tickets
Each morning, pulls the highest-impact Sentry issues from the last 24 hours, counts how many Zendesk tickets each crash generated.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionPull top Sentry issues by affected users (24h)Sentry
- ActionCount linked Zendesk tickets per issueZendesk
- LogicRank by combined impact and ticket volume
- OutputPost ranked crash-vs-ticket digest to SlackSlack
What it does
Produces a single daily readout that ranks crashes by real customer pain. It takes the top Sentry issues by affected-user count over the past day, cross-references how many Zendesk tickets mention each one, and posts a ranked list combining crash group, affected users, breadcrumb summary, and ticket volume.
When to use it
Use it for a daily support or engineering standup when you want to argue priorities with data rather than gut feel: the bug with the most tickets and most affected users floats to the top.
How it works
- 1A morning schedule triggers the run.
- 2Sentry is queried for the top issues of the last 24 hours by affected-user count.
- 3For each issue, Zendesk is searched to count linked tickets from the same window.
- 4A logic step ranks the issues by a combined impact-plus-ticket score.
- 5The ranked digest, with crash group, affected users, breadcrumb summary, and ticket counts, is posted to a Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.