ReportingRuns weekly
Octolens+Slack

Weekly competitor insights in Slack

A weekly competitor digest in Slack: launches, complaints, switching talk, and openings for you — every claim backed by a linked mention.

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

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 weekly recurring task (Monday mornings) using the playbook below. Competitors: {COMPETITORS}. Slack channel: {SLACK_CHANNEL}.

What it does

  • Computes weekly mention volume, sentiment, and platform mix per competitor
  • Reads the top mentions to find what actually happened — launches, complaints, switching talk
  • Surfaces openings: pain points and alternative-seeking you could act on
  • Backs every claim with short quotes and links
  • Posts the digest to your Slack channel (or chat if Slack isn't connected)
  • Stays under 500 words — quiet weeks get one line, not padding
Mentions come from every platform Octolens monitors:RedditRedditX (Twitter)X (Twitter)LinkedInLinkedInHacker NewsHacker NewsGitHubGitHubYouTubeYouTubeBlueskyBlueskyStack OverflowStack OverflowTikTokTikTokDEV.toDEV.toNewsNewsNewslettersNewslettersPodcastsPodcastsWebWeb

Delivers: A weekly Slack digest of competitor activity with evidence links, a volume table with deltas, and concrete openings for your team.

Inputs

PlaceholderRequiredDescriptionExample
{COMPETITORS}RequiredCompetitor names tracked as keywords in OctolensCompetitorOne, CompetitorTwo
{SLACK_CHANNEL}RequiredThe Slack channel to post the digest in#competitive-intel

How your agent runs it

  1. 1

    Map the keywordsLoads the analytics schema and resolves competitor keyword IDs.

    analytics_contextlist_keywords
  2. 2

    Run the numbersWeekly mentions, sentiment, and platform breakdown per competitor, with deltas.

    analytics
  3. 3

    Read the top mentionsFinds launches, recurring complaints, switching talk, and wins in each competitor's week.

    list_mentions
  4. 4

    Find the openingsComplaints and alternative-seeking become suggested next steps for your team.

  5. 5

    Post to SlackDelivers the digest to your channel via your Slack tool — or in chat if none is connected.

    slack_post

Tools used

  • analytics_contextOctolens MCPAnalytics schema and valid filter values
  • analyticsOctolens MCPWeekly competitor volume, sentiment, and platform SQL
  • list_keywordsOctolens MCPResolve competitor keyword IDs
  • list_mentionsOctolens MCPTop competitor mentions of the week, by relevance
  • slack_postYour MCP clientPost the digest (Slack MCP or your client's Slack integration)

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.

Weekly competitor insights in Slack — playbook
Every week, do the following:
1. Call analytics_context to load the analytics schema, then list_keywords to
   map keyword IDs for the competitors: {COMPETITORS}.
2. Using the analytics tool, compute for the last 7 full days vs the 7 days
   before: mentions per competitor, sentiment split, and platform breakdown.
3. For each competitor, call list_mentions (last 7 days, sorted by relevance)
   and read the top mentions. Identify what actually happened this week:
   - launches and announcements
   - recurring complaints (pricing, reliability, missing features)
   - switching talk and alternative-seeking
   - notable praise or wins
4. Build the digest:
   **Competitor insights — week of {date}**
   1. One-line takeaway: the single most useful thing that happened
   2. Per competitor (2-4 bullets each): what happened, with 1-2 short
      quotes and links as evidence
   3. Openings for us: complaints or switching talk we could act on,
      each with a suggested next step
   4. Volume table: competitor | mentions | Δ vs last week | sentiment
5. Post the digest to the Slack channel {SLACK_CHANNEL} using your Slack
   tool. If no Slack tool is connected, post the digest in chat instead and
   say so.
Keep it under 500 words. Quotes over adjectives — every claim needs a
linked mention behind it. If a competitor had a quiet week, one line is
enough.
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