CUSTOMER SUPPORT
Attach Sentry crash context to new Zendesk tickets
When a Zendesk ticket is created, finds the matching Sentry issue and attaches the crash group, breadcrumb trail, and affected-user count as an internal note so agents triage…
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket createdZendesk
- ActionBuild Sentry query from ticket text and requester
- ActionFetch matching Sentry issue, breadcrumbs, affected usersSentry
- LogicConfident match found?
- OutputPost internal note and tag ticket sentry-linkedZendesk
What it does
Every new Zendesk support ticket is enriched with the engineering context behind the bug. The workflow searches Sentry for the issue that matches the reporter or error fingerprint, then posts an internal note containing the crash group title, stack-frame summary, recent breadcrumb trail, and how many users are affected.
When to use it
Use it when your support team handles app-crash and error reports and currently has to ping engineering or dig through Sentry by hand. It collapses that back-and-forth into a single automatic note on the ticket.
How it works
- 1A new Zendesk ticket triggers the run.
- 2The ticket subject, body, and requester email are parsed to build a Sentry search query (error text, release, user email).
- 3Sentry is queried for the best-matching issue; the workflow pulls the crash group, latest event breadcrumbs, and the affected-user count.
- 4A filter checks whether a confident match was found.
- 5If matched, an internal note with the assembled context is added to the Zendesk ticket and it is tagged `sentry-linked`.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SentryErrors, performance, releases.
- 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
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.
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.
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.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.