Goal: Automatically discover recent AI trends, newly published research, AI product launches, developer complaints, and emerging business problems, then turn them into startup opportunity reports.

Build the workflow with these stages:

  1. Schedule Trigger: run every 30 minutes.

  2. Collect recent content from a Google News RSS search feed for AI trends, AI startups, LLMs, AI agents, developer tools, and enterprise AI. Use the RSS Read node or an appropriate supported RSS integration.

  3. Make the source list extensible so I can add official AI company blogs, arXiv feeds, and GitHub releases later.

  4. Parse article titles, original URLs, publication dates, descriptions, and source names.

  5. Filter irrelevant items and skip duplicate URLs. Keep a persistent record of processed articles so the workflow does not analyse the same article repeatedly.

  6. Analyse each new article using an AI model. Return structured JSON containing:

    • title

    • source_url

    • publication_date

    • topic

    • underlying_problem

    • affected_users

    • evidence_from_source

    • potential_solution

    • proposed_MVP

    • likely_customer

    • possible_revenue_model

    • validation_questions

    • opportunity_score from 0 to 100

    • confidence_level

  7. Score opportunities based on evidence of a real problem, severity, frequency, willingness to pay, market relevance, and feasibility for a solo developer.

  8. Store the original article and analysis in a persistent database or n8n Data Table. Avoid overwriting unrelated records.

  9. Send a daily digest of the top five opportunities by email, including original source links and a brief explanation of why each opportunity matters.

  10. Handle unavailable feeds, malformed articles, API failures, and rate limits gracefully. Do not fabricate evidence or treat a news announcement as proof of customer demand.

Use available standard n8n nodes wherever possible. Create a working, testable workflow with valid node connections and configuration. Identify any credentials or API keys I must configure manually. If a feature cannot be configured automatically, explain the exact manual steps instead of pretending it is working.