Product

Auto-Create Linear Issues from Reddit, Twitter & LinkedIn Mentions

Bug reports and feature requests get posted in public every day, and most never reach your team. Here's how to automatically turn actionable product mentions into Linear issues using Octolens, Linear, and MCP.

Auto-create Linear issues from Reddit, Twitter, and LinkedIn mentions with Octolens

Someone could be reporting a bug about your product on Reddit, asking for a feature on X, or mentioning broken behavior on LinkedIn.

The problem is that this feedback often never makes it into the tool your product and engineering teams actually use.

For many SaaS teams, that tool is Linear.

In this tutorial, I'll show you how to automatically turn actionable product mentions into Linear issues using Octolens, Linear, and MCP.

The workflow is simple:

Product mention → AI classification → Linear issue

You can use it to catch bug reports, feature requests, and other product feedback from public conversations without manually checking Reddit, Twitter/X, LinkedIn, Hacker News, GitHub, and other sources.

Watch the walkthrough
What this workflow does

This automation checks new product mentions, filters out noise, and creates Linear issues only for actionable feedback.

It can:

  • Pull new product mentions from the past 24 hours
  • Classify each mention as a bug, feature request, or skip
  • Ignore praise, general chatter, competitor comparisons, and unrelated posts
  • Check whether the issue already exists in Linear
  • Create a new Linear issue with the original source link and context
  • Post a short summary of what was created

The goal is not to turn every mention into a ticket.

The goal is to make sure real product feedback does not get lost in social feeds.

Step 1: Track your product name in Octolens

Start by adding your product name as a keyword in Octolens.

Octolens monitors public mentions across sources like Reddit, Twitter/X, LinkedIn, Hacker News, GitHub, YouTube, podcasts, news, and more.

For this workflow, start simple. Track your product name first.

Later, you can add:

  • Common misspellings
  • Feature names
  • Competitor names
  • Pain-point keywords
  • Product category terms

But the first version should stay focused.

Step 2: Connect Octolens and Linear through MCP

Next, connect the Octolens MCP and Linear MCP in your MCP-compatible client.

In the video, I use Claude Cowork, but the same workflow can work with any MCP-compatible setup.

The assistant needs access to two things:

  1. Octolens mentions
  2. Linear issue creation

Once both are connected, the assistant can pull new mentions, decide whether they are actionable, check for duplicates, and create Linear issues.

Step 3: Schedule the recurring task

Create a recurring task that runs once per day.

Daily is usually enough. You catch feedback while it is still fresh, but you avoid flooding Linear with low-quality tickets.

The task should:

  1. Pull new mentions from the past 24 hours
  2. Classify each mention
  3. Skip anything that is not actionable
  4. Check whether the issue already exists
  5. Create new Linear issues for bugs and feature requests
  6. Return a short summary

I recommend leaving assignee and priority empty.

The automation should capture the signal. A human should still triage ownership and urgency.

Copy-paste prompt

Replace {PRODUCT_NAME} with your product name and {LINEAR_TEAM_ID} with your Linear team ID.

Every day, do the following:
1. Run `list_mentions_context` to refresh filter syntax and keyword IDs.
2. Pull all mentions from the past 24 hours matching the keyword "{PRODUCT_NAME}".
3. For each mention, classify it into exactly one bucket:
- bug — describes broken behavior, an error, a regression, or something not working
- feature_request — asks for a capability the product doesn't have, or expresses a clear unmet need
- skip — everything else, including praise, general chatter, competitor comparisons, and unrelated discussion
4. Drop everything classified as "skip".
5. For each remaining mention, search Linear for an existing issue whose description contains the source URL. If found, skip it because it is already tracked.
6. For each new actionable mention, create a Linear issue in team {LINEAR_TEAM_ID}:
Title:
8–12 word summary, prefixed with [Bug] or [Feature]
Description:
> {original quote, trim to ~500 chars if longer}
**Source:** {url}
**Author:** {authorName} (@{author})
**Platform:** {source}
**Posted:** {timestamp}
Labels:
"social-listening" plus either "bug" or "feature-request"
No assignee, no priority — leave for human triage.
7. Post a summary in chat:
- Mentions checked: N
- Actionable: N (X bugs, Y feature requests)
- Already tracked: N
- New issues created: bullet list with Linear issue URLs
If there are no new actionable mentions, just say "No new actionable mentions today" and exit cleanly.