Weekly competitive intelligence report from social listening to Notion and Slack

PromptCreate

Build me a weekly competitive intelligence agent workflow. It should run on a cron trigger every Monday at 7:00 AM America/New_York.

The workflow tracks a configured list of competitor brands. For each competitor, query Infegy Starscape over the past 7 days and call Get Topics Analysis to surface emerging themes with size and sentiment, Download Post Records (capped at a sensible sample, for example the top 500 posts ranked by engagement or reach so the run stays within plan and cost limits), and Generate AI Summary to produce a narrative read on the conversation. From these results, capture for each competitor: share of voice (this competitor's post volume relative to the total across all tracked competitors), week-over-week sentiment trend versus the prior week's pull, top emerging themes, and 3 to 5 standout posts (highest reach or most engaged) with author and link.

After all per-competitor pulls are done, synthesize a single comparative weekly briefing covering: share-of-voice ranking across competitors, week-over-week sentiment movement per competitor (call out the biggest mover up and the biggest mover down), emerging themes per brand with a short narrative on what is driving each, and any noteworthy content, launches, or campaigns competitors ran in the week.

Use Notion's Create a Page operation to drop the briefing as a new dated page in our designated competitive intelligence Notion database. The page title should be something like 'Competitive Intel — Week of [Monday date]'. Fill in the database properties (date, week number, competitors covered) and put the full briefing in the page body with clear section headings.

Once the Notion page exists, use Slack's Send a Message operation to post a short message in our marketing channel with a one-line summary (top mover for the week) and a link to the new Notion page so the team is pinged when the report lands.

The competitor list, the Notion database id, and the Slack channel should be configurable inputs so we can edit them later without rewriting the workflow. Make the post-record sample size and the AI summary tone (for example, neutral analyst vs. punchy marketing) configurable too. Store last week's per-competitor metrics so the next run can compute the week-over-week comparison.

What does this prompt do?

Pulls last week's social conversation for each competitor on your list, including share of voice, sentiment trend versus the prior week, top emerging themes, and standout posts.
Synthesizes the per-competitor pulls into a single ranked briefing so you can see who is winning the conversation, who is moving up or down, and what is driving it.
Saves the briefing as a new page in your competitive intelligence Notion database, dated and ready for the team to comment on.
Posts a link to the new Notion page in your marketing Slack channel so the team knows the weekly read is live.

What do I need to use this?

An Infegy Starscape subscription with API access, plus the list of competitor brands you want tracked.
A Notion workspace with a database where the weekly competitive briefings should live.
A Slack workspace and the channel name where the weekly link should be posted.

How can I customize it?

Change the schedule (for example, Friday afternoon recap instead of Monday morning, or move the time to your marketing lead's timezone).
Edit the competitor list, keyword aliases, and excluded terms so the analysis matches the brands and products you actually care about.
Swap the Notion database, change the page properties that get filled in, or change which Slack channel and message format the team gets pinged with.

FAQs

Do I need a paid Infegy subscription for this to work?

Yes. Infegy Starscape is a paid social listening platform, and you need an active subscription with API access turned on. If you do not see API access in your Infegy account, your account manager can enable it.

Can I track more than a handful of competitors?

Yes. You can add as many competitors to the tracked list as your Infegy plan allows. The briefing will rank them all and call out the biggest movers so the report stays readable.

Will the report appear in Notion automatically every week?

Yes. A new dated page is created in the Notion database you choose every Monday at 7am ET, so the team has a fresh briefing to review before the week starts.

What if I want the alert in a different Slack channel or as a DM?

You can point the Slack message at any channel you have access to, or send it as a direct message to a specific person. Just tell the workflow author who should receive it.

Can I tweak what is in the briefing itself?

Yes. You can adjust which sections appear, how many themes or standout posts are included, and what the comparative ranking emphasizes, like sentiment movement versus raw volume.

Related templates

Partner tier review board for quarterly promotion calls

Work every partner tier decision from one board, with the revenue and commission numbers, clear promotion thresholds, and AI review briefs.

App

Reconcile partner commissions between HubSpot and Introw

Open one board at month end to find every closed deal missing a commission, every commission with no deal behind it, and every amount that does not add up.

App

Artwork desk for the Notion posts still missing an image

Open one screen each Monday to see which upcoming posts still have no image, generate three on-brand options, and file the one you pick.

App

One control room for every Instantly sending mailbox

See warmup status, daily send volume, and bounce risk for every sending account in one grid, with the riskiest mailboxes floating to the top.

App

Partner payout approval queue with Xero bill handoff

Review Introw partner payouts line by line, approve them from one board, raise the matching bill in Xero, and post every approval to Slack.

App

One inbox for every Jira Service Management approval waiting on you

See every access, purchase and leave request waiting on your decision in one screen, approve or decline in place, and send the reason back to the requester.