CUSTOMER SUPPORT
Notify affected tickets when their Sentry crash is resolved
When a Sentry issue is marked resolved, finds every open Zendesk ticket linked to that crash group and posts the fix release plus a ready-to-send customer update.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue marked resolvedSentry
- ActionRead resolved issue short-ID and fix releaseSentry
- ActionFind open Zendesk tickets linked to the crash groupZendesk
- LogicPer ticket: draft-reply, solve, or note?
- OutputApply fix update and draft customer reply to each ticketZendesk
What it does
Closes the loop with customers when a bug is fixed. The moment a Sentry issue flips to resolved, the workflow finds all open Zendesk tickets tied to that crash group and drops in the resolving release version, a short fix summary, and a draft customer-facing reply so agents can confirm the fix and close out.
When to use it
Use it when crashes generate clusters of tickets and you want to proactively tell affected customers the moment a fix ships, instead of leaving stale tickets open or making them follow up.
How it works
- 1A Sentry issue-resolved webhook triggers the run.
- 2The workflow reads the resolved issue's short-ID and the release that fixed it.
- 3Zendesk is searched for open tickets carrying that issue's tag or short-ID.
- 4A logic step decides per ticket whether to draft-reply, solve, or just note based on ticket status.
- 5Each matched ticket gets the fix release, a summary, and a draft customer update applied accordingly.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.