CUSTOMER SUPPORT
Daily VIP error-budget digest for account reviews
Each morning, rolls up the prior day's Sentry error rates per enterprise account, ranks accounts burning the most error budget.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled weekday-morning run
- ActionQuery Sentry prior-24h events grouped by account tagSentry
- ActionJoin error totals with tier + ARR in SalesforceSalesforce
- LogicScore error-budget burn and rank top movers
- OutputPost prioritized at-risk digest to CSM channelSlack
What it does
Gives the customer-success team a daily, ranked view of which VIP accounts had the worst reliability yesterday, so morning standups start from data instead of inbox surprises.
When to use it
Run this when you want a recurring proactive cadence rather than per-spike alerts — ideal for weekly business reviews and catching slow-burn regressions that never trip a single alert.
How it works
- 1A scheduled trigger runs every weekday morning.
- 2The flow queries Sentry for the prior 24 hours of events grouped by the enterprise `account` tag.
- 3It joins each account's error totals against its tier and contract value pulled from Salesforce.
- 4A logic step computes an error-budget-burn score and ranks accounts, keeping the top movers.
- 5It posts a formatted digest to the CSM channel in Slack listing each at-risk account, its top error, day-over-day change, and the owning CSM.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect SalesforceAccounts, opportunities, cases.
- 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
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.