CUSTOMER SUPPORT
Convert an Intercom support thread into a GitHub bug issue with env metadata
On a new Intercom conversation flagged as a defect, this pulls the customer's app version and device metadata, attaches recent Sentry breadcrumbs.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation flagged as defectIntercom
- ActionGet transcript and contact env attributesIntercom
- ActionPull Sentry breadcrumbs and failing releaseSentry
- LogicDerive severity and GitHub labels from tags/keywords
- ActionOpen GitHub issue from bug templateGitHub
- OutputReply in Intercom with issue numberIntercom
What it does
Bridges Intercom support chats and your GitHub backlog. It reads the conversation, lifts the environment attributes Intercom already collects (app version, browser, OS, plan), enriches with Sentry breadcrumbs around the report time, and opens a GitHub issue using your repository's bug template.
When to use it
Use when engineering lives in GitHub Issues and support lives in Intercom, and you want defect reports filed automatically without copy-paste. Good for product teams shipping a web or mobile app.
How it works
- 1An Intercom conversation is tagged or routed as a defect (trigger).
- 2The flow retrieves the conversation transcript plus contact and custom data attributes from Intercom.
- 3It queries Sentry for the contact's recent events and pulls breadcrumbs and the failing release.
- 4A logic step checks severity from tags and conversation keywords to set the GitHub label set.
- 5It creates a GitHub issue populated with summary, steps, expected vs actual, and an environment table.
- 6It replies inside Intercom with the issue number so the agent can keep the customer updated.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect SentryErrors, performance, releases.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.