CUSTOMER SUPPORT
Notify affected users in Intercom when Sentry flags a regression
When a Sentry issue crosses a user-impact threshold, pulls the affected user identifiers and sends each a tailored Intercom message acknowledging the bug and its status.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry alert: issue crosses user-impact thresholdSentry
- ActionFetch issue detail + affected usersSentry
- LogicKeep identified users, dedupe per issue
- ActionEnrich with plan tier + locale in PostgresPostgres
- OutputSend tailored Intercom messageIntercom
- LogicFlag high-value accounts for human follow-up
What it does
Listens for Sentry alerts on a new or regressed issue, reads the list of affected users Sentry has attached to the event, and proactively messages each real, named customer in Intercom — so the people who actually hit the crash hear from you instead of rage-quitting silently.
When to use it
Reach for this on user-facing crashes and front-end errors where Sentry already captures user context. Ideal right after a deploy regression, when you want to get ahead of the support queue.
How it works
- 1A Sentry alert fires when an issue's affected-user count crosses the threshold.
- 2The flow fetches the issue detail and its affected-user list from Sentry.
- 3A logic step filters to identified users (those with an email or external ID) and dedupes against anyone already messaged for this issue.
- 4Postgres enriches each user with plan tier and locale to choose tone and language.
- 5Intercom sends a tailored message naming the broken action and linking a status note.
- 6A logic step tags high-value accounts for an additional human follow-up flag.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect IntercomConversations, contacts, articles.
- 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.