ProductRuns daily
Octolens+Linear

Turn mentions into Linear issues

Catch bug reports and feature requests posted in public — on Reddit, X, LinkedIn, Hacker News, GitHub — and file them as Linear issues automatically.

Prefer a walkthrough? Read the full tutorial with video

Set it up

1. Connect the Octolens MCP — add the server URL in your client and sign in. OAuth, no API key. Per-client instructions · docs. Also connect the Linear MCP.

MCP server URL
https://app.octolens.com/api/mcp/v2

2. Hand your agent the playbook — hit Copy below (it grabs the instruction plus the full playbook), fill in the placeholders, and paste it into your agent. Pasting the playbook instead of describing the idea makes the agent run this exact workflow rather than improvise its own.

Instruction + full playbook
Set up a daily recurring task using the playbook below. Product name: "{PRODUCT_NAME}". Linear team: {LINEAR_TEAM_ID}.

What it does

  • Pulls new product mentions from the past 24 hours
  • Classifies each mention as a bug, feature request, or skip
  • Ignores praise, general chatter, competitor comparisons, and unrelated posts
  • Checks whether the issue already exists in Linear before creating anything
  • Creates Linear issues with the original quote, source link, and context
  • Posts a short summary of what it created
Mentions come from every platform Octolens monitors:RedditRedditX (Twitter)X (Twitter)LinkedInLinkedInHacker NewsHacker NewsGitHubGitHubYouTubeYouTubeBlueskyBlueskyStack OverflowStack OverflowTikTokTikTokDEV.toDEV.toNewsNewsNewslettersNewslettersPodcastsPodcastsWebWeb

Delivers: New Linear issues for every actionable piece of public product feedback — deduplicated, labeled, and left unassigned for human triage.

Inputs

PlaceholderRequiredDescriptionExample
{PRODUCT_NAME}RequiredYour product name as tracked in OctolensAcme
{LINEAR_TEAM_ID}RequiredThe Linear team the issues should be created inENG

How your agent runs it

  1. 1

    Confirm the keywordThe agent checks that your product name is tracked in Octolens and grabs its keyword ID.

    list_keywords
  2. 2

    Pull fresh mentionsFetches every mention from the past 24 hours that matched the keyword.

    list_mentions
  3. 3

    Classify each mentionBuckets every mention as bug, feature_request, or skip — praise, chatter, and competitor comparisons get skipped.

  4. 4

    Check for duplicatesSearches Linear for an existing issue containing the mention's source URL, so nothing gets filed twice.

    list_issues
  5. 5

    Create the issuesFiles a Linear issue per actionable mention — original quote, source link, author, platform — labeled but unassigned.

    create_issue
  6. 6

    Report backPosts a summary: mentions checked, bugs vs feature requests, duplicates skipped, and links to the new issues.

Tools used

  • list_keywordsOctolens MCPList every monitored keyword with IDs, platforms, tag, and status
  • list_mentionsOctolens MCPFetch collected mentions with filtering and pagination
  • list_issuesLinear MCPSearch existing Linear issues to dedupe against the source URL
  • create_issueLinear MCPCreate the Linear issue with quote, source link, and labels

All 23 Octolens MCP tools are documented on the MCP page and in the docs.

The full playbook

Replace the placeholders, then paste this into your agent as a recurring task.

Turn mentions into Linear issues — playbook
Every day, do the following:
1. Call list_keywords to confirm "{PRODUCT_NAME}" is tracked in Octolens and get its keyword ID.
2. Call list_mentions to pull all mentions from the past 24 hours matching that keyword.
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.
7-day free trial

Give your agents context on what happens online

API, webhooks, and MCP on every plan. If you're paying us anything, you own your data.

No credit card required · API access on all plans · Cancel anytime