TICKET MANAGEMENT
Attach Intercom bug reports to the matching GitHub umbrella issue
When an Intercom conversation is tagged as a bug, this matches it to an open GitHub umbrella issue, links the conversation as evidence, updates the reported-by count.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged as bugIntercom
- ActionSearch open GitHub umbrella issuesGitHub
- LogicBranch: matched an umbrella issue?
- ActionComment on GitHub umbrella + update reported-by countGitHub
- ActionEscalate unmatched report to triage channelSlack
- OutputReply in Intercom that bug is trackedIntercom
What it does
Turns repeat Intercom bug reports into structured signal on a single GitHub issue. Each matched conversation is attached to the umbrella as a fresh data point, and the issue body keeps a running count of how many users have reported it.
When to use it
Use it when your team tracks bugs in GitHub but hears about them in Intercom. It bridges the two so engineers see real user volume on an issue without anyone copy-pasting conversation transcripts.
How it works
- 1An Intercom conversation tagged 'bug' triggers the flow.
- 2The flow extracts the reported symptom and searches open GitHub issues carrying the umbrella label.
- 3A branch decides: a confident title or body match links to that umbrella; no match escalates to a triage channel instead of guessing.
- 4On a match it adds a comment to the GitHub issue with the Intercom link and bumps the reported-by tally in the issue body.
- 5It replies in Intercom with a short note that the bug is logged and being worked on.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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 Ticket Management workflows
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
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.