SUMMARIZATION
Cluster Intercom Themes into Linear Feature Issues
Clusters the week's Intercom conversations into feature-request themes and creates or updates a deduplicated Linear issue per theme, linking back the source conversations.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull tagged Intercom conversations (7d)Intercom
- ActionCluster into feature-request themesOpenAI
- ActionSearch Linear for matching issueLinear
- LogicBranch: update existing vs create new
- OutputCreate or update Linear issue with evidenceLinear
What it does
It turns raw support chatter into structured product backlog. The flow clusters the week's Intercom conversations into distinct feature-request themes, then for each theme either creates a new Linear issue or updates an existing one, attaching the conversation count and customer quotes so the backlog reflects real demand.
When to use it
Use it when feature requests are scattered across hundreds of conversations and never make it into the tracker, or when the same request keeps getting re-filed. It keeps one canonical Linear issue per theme and grows its evidence over time.
How it works
- 1A weekly schedule starts the run.
- 2Pull Intercom conversations from the last 7 days tagged as requests or questions.
- 3An OpenAI step clusters them into feature-request themes with titles and summaries.
- 4For each theme, search Linear for an existing matching issue by title similarity.
- 5Branch: if a match exists, append the new evidence as a comment and bump a demand count; otherwise create a new issue.
- 6Write conversation permalinks and quote snippets into each issue body.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 Summarization workflows
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Escalate blockers from Loom standups to Slack
Transcribes each new Loom standup video, uses AI to detect blockers and dependencies.
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.