Workflows· Research & Knowledge Management

    The Competitor Trail

    A daily workflow that collects new competitor posts from RSS feeds and turns them into a prioritized trend report for the content team.

    researchinganalyticalautomating

    Description

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    The workflow starts daily at a fixed time, for example 9:00 a.m., alternatively on a weekly cadence.

    02Automated

    03Automated

    04Automated

    05Automated

    06Result

    Key
    PersonAutomatedResultApproval

    Requirements and operations

    Requirements

    • RSS reader Feedly, Inoreader or a similar tool for the competitors' blogs and newsrooms.
    • Storage location Notion, Drive or Confluence for the daily reports.
    • Team chat (optional) Slack or Teams for alerts on particularly relevant findings.
    • LLM access API key for OpenAI, Claude or Gemini.

    Testing

    • Test run Test the workflow manually with real competitor feeds before you go live.
    • Feed fetch Check whether all configured feeds load correctly.
    • Report quality Assess whether the insights are structured, relevant and backed by traceable scores.
    • Edge cases Test days with no new posts, duplicates, paywalled sources and weekends.

    Go-live

    • Approve to start Activate the workflow only once feeds and report run cleanly.
    • Source list Define the source list initially and maintain it monthly, adding new sources and removing inactive ones.
    • Refine Review report quality over the first two weeks and adjust the prompt accordingly.
    • Filter Filter out pure PR updates without substantive content.

    Common issues

    • No new articles Validate the feed URLs or extend the time filter to 48 hours.
    • Analysis too shallow Refine the prompt or choose a stronger model.
    • Report not saved Check the write permissions in the storage tool.
    • Duplicates distort trends Add deduplication based on URL or title.

    Builder Prompt

    GOAL
    Build a workflow that fetches new posts from the RSS feeds of defined competitors every day, analyzes the content by AI for topic, positioning, feature and format, aggregates trends across multiple posts, and generates a structured competitor report at the designated storage location. Optionally, an alert should also be triggered in the team chat for particularly relevant findings.
    
    Adapt the structure to the concepts of your automation tool (for example nodes, steps, zaps or agent actions). While doing so, preserve the trigger logic, the sequence and the data flow.
    
    TRIGGER
    Type: time based, daily at 9:00 a.m., alternatively weekly.
    
    STEPS (sequential)
    1. Fetch RSS feeds: load all configured competitor feeds, filter for posts from the last 24 hours, and remove duplicates based on URL or title.
    2. AI step: content analysis and trends. Insert the working prompt "Content Analysis and Trends" exactly as given (see the Working Prompts section). Result: a structured report with top insights including a relevance score from 1 to 5.
    3. Save: file the report with the date in the title at the designated storage location (Notion, Drive or Confluence).
    4. Branch (optional): if the report contains an insight with a relevance score of 5 out of 5, also send an alert to the team chat with the top findings and the link to the report.
    
    PROMPT GUIDANCE
    There is a fixed working prompt for the analysis step, see the Working Prompts section. Insert it unchanged and in full into step 2.
    
    DATA FLOW
    Step 1 to step 2: deduplicated posts (title, source, link, teaser or full text) as input for the feed items placeholder in the working prompt.
    System to step 2: the current date as input for the corresponding placeholder in the working prompt.
    Step 2 to steps 3 and 4: the finished report and the relevance scores it contains, as the basis for the optional alert branch.
    
    ERROR HANDLING
    No new articles: validate the feed URLs or extend the time filter to 48 hours. On days without new posts, file a short notice report instead of aborting the run without a result.
    Duplicates distort the trends: enforce deduplication from step 1, based on URL or title.
    Paywalled sources: analyze only the title and teaser, and mark the affected finding in the report as limited.
    Analysis too shallow: refine the focus areas in the working prompt or choose a stronger model. Filter out pure PR updates without substantive content.
    Report not saved: check the write permissions at the storage location.
    
    PLACEHOLDER CONVENTION
    All placeholders in square brackets in the working prompt are variables. The feed items and the current date are mapped dynamically, as described in the data flow. The three focus areas are not dynamic: set these yourself as the strategic areas of observation before activation. List all placeholders that require manual configuration separately at the end.
    
    SELF CHECK BEFORE COMPLETION
    Check, before you report the workflow as finished:
    1. Are all steps connected correctly, including the 24 hour filter, deduplication and the optional alert branch at a relevance score of 5 out of 5?
    2. Is the working prompt inserted in full and unchanged, and are the placeholders for feed items and date mapped correctly?
    3. Is the report filed with the date in the title at the correct location?
    4. Are all points listed that require manual configuration: the source list including monthly maintenance, the storage location with write permissions, the alert channel, the three focus areas and the LLM access?

    Working prompts

    Prompt: Content Analysis and Trends

    Analyzes new competitor posts for topics, developments and trends, and returns a prioritized report with a relevance score.

    You are a strategic content analyst. Analyze the following new articles from competitors and create a structured report. Where sufficient information is not available for individual points, mark the affected statement as an assumption instead of presenting it as established fact.
    
    New articles from the last 24 hours:
    [RSS_FEED_ITEMS]
    
    Analyze the following aspects:
    1. Main topics and content focus areas
    2. New product features or announcements
    3. Recognizable content strategies and formats
    4. Industry trends and market developments
    5. Tone and target audience approach
    
    Create a report with the following structure:
    
    Competitor Content Report, [DATE]
    
    Top Insights: the three to five most important findings as bullet points
    
    Topic Overview: categorized listing of the main topics
    
    New Developments: product announcements, features, strategic moves
    
    Identified Trends: overarching patterns and industry trends
    
    Recommendations: concrete suggestions for the content team
    
    Focus on:
    [FOCUS_AREA_1]
    [FOCUS_AREA_2]
    [FOCUS_AREA_3]
    
    Rate the relevance of each insight on a scale of 1 to 5 and prioritize the report accordingly.

    JSON export

    Setup

    Two routes lead to the same result. Pick the one that fits your setup.

    Suitable when you want to build the workflow in your own automation tool.

    1. Open your workflow tool, for example n8n, Make, Zapier or Langdock.
    2. Create a new workflow and give it a name.
    3. Choose the AI-assisted build option if your tool offers one.
    4. Paste the builder prompt from above in full.
    5. Check the result against the step sequence in this document, then add your access credentials and channels.

    Suitable when you want to take the workflow over unchanged.

    1. Download the JSON file from the JSON export section.
    2. Open the workflow area of your tool and create a new workflow.
    3. Give it a name and confirm.
    4. Open the menu on the workflow name and choose to import a JSON file.
    5. Upload the file, then add your own access credentials.
    6. Run a test before you activate the workflow.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call