CUSTOMER SUPPORT
VIP error-spike to CSM heads-up before the ticket
Watches Sentry for error-rate spikes tagged to a named enterprise account, confirms it's above that account's baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry metric alert fires for an account-tagged issueSentry
- ActionPull last-hour event count + 7-day baseline for the accountSentry
- LogicKeep only spikes above 4x baseline and 25 events
- ActionLook up owning CSM and account tier in SalesforceSalesforce
- OutputPost proactive heads-up to the CSM in SlackSlack
What it does
Turns a Sentry issue alert into a proactive customer-success play. When errors spike for a specific VIP account, it pings the account's CSM with a scoped summary so they can reach out before the customer notices.
When to use it
Run this when your top enterprise accounts are tagged on Sentry events (via an `account_id` or `org` tag) and you want CSMs warned of regressions ahead of an inbound complaint.
How it works
- 1Sentry fires a metric-alert webhook for an issue carrying an enterprise `account` tag.
- 2The flow pulls the issue's event count over the last hour and the account's prior 7-day hourly baseline.
- 3A logic step keeps only spikes that exceed 4x baseline and 25 events, dropping noise.
- 4It looks up the account's owning CSM and tier in Salesforce.
- 5It posts a threaded Slack message to the CSM with the error title, affected endpoint, spike multiple, and a Sentry deep link, framed as a get-ahead-of-it nudge.
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.