Counter-piece opportunities from competitor blog posts

By General Input

Watch a competitor's blog, wait for engagement to settle, and file an Asana brief whenever a post is taking off so your content team can respond.

Integrations

  • BuzzSumo
  • Asana

Type

Agentic Task

Categories

  • Marketing

Build me an agent workflow that watches a competitor's blog and turns breakout posts into counter-piece briefs in Asana. Skip the duds entirely.

Trigger: an RSS poll on the new_item event for a competitor blog feed I configure during setup. I want to be able to add more than one feed if I monitor multiple competitors.

When a new post fires the trigger, the agent should wait roughly four hours so social engagement has time to accumulate. Make this wait duration configurable.

After the wait, call BuzzSumo's Get URL Share Counts on the post URL to get the live Facebook, Twitter, Pinterest, and Reddit engagement. Combine them into a single total. Also call BuzzSumo's Search Articles scoped to the post's topic (use the post title or extracted keywords as the query) over roughly the last 90 days, sorted by engagement, to surface adjacent winning content. Make both the lookback window and the keyword extraction approach reasonable defaults but configurable.

Decision: if the combined share count is below a configurable engagement floor (default something sensible like 500), the agent exits silently. Log nothing, file nothing, send nothing. The whole point is to keep the team's Asana project clean of noise.

If the combined share count is at or above the floor, use Asana's Create a Task operation to file a 'Counter-piece opportunity' task in the content team's project (project gid configurable during setup, with optional section and assignee). The task name should be something like 'Counter-piece: <competitor post title>'. The task description should include the competitor post URL, the current engagement breakdown by network plus the combined total, the top three related high-engagement articles from the BuzzSumo search (title, URL, engagement), a suggested counter-angle that complements or contrasts the competitor framing using the related winners as evidence, and a recommended publish deadline (default seven days out, also configurable).

Be conservative with BuzzSumo Search API calls because the monthly quota is small. One Get URL Share Counts call and one Search Articles call per qualifying post is enough; do not paginate beyond the first page of related articles.

On errors from either service, surface a clear failure rather than filing a partial task. The team would rather see nothing than see a half-written brief.

Related prompts

Explore more prompts
Influencer campaign war room for campaigns still in flightTrack every client call promise until it is actually doneDecide which old blog posts to refresh, merge, or leaveShortlist social amplifiers who actually share your topicCompetitor share of voice board for content planningSee every blocked Asana task and who is holding it upAsana team workload board for your Monday capacity checkWrite every Asana project status update from one deskWeekly UK filing deadline tracker for your client bookWeekly contract renewal radar from Deel to Asana and Slack