HumationHuman + Automation
Back to Catalog

Monitor Furusato Nozei market trends with Google News, AI analysis and Slack reporting

飯盛　正幹飯盛　正幹
58 views
2/3/2026
AirtableWebhookAutomationEmailData Integration
Official Page

Analyze Furusato Nozei trends from Google News to Slack

This workflow acts as a specialized market analyst for Japan's "Furusato Nozei" (Hometown Tax) system. It automates the process of monitoring related news, validating keyword popularity via search trends, and delivering a concise, strategic report to Slack.

By combining RSS feeds, AI agents, and real-time search data, this template helps marketers and municipal researchers stay on top of the highly competitive Hometown Tax market without manual searching.

👥 Who is this for?

  • Municipal Government Planners: To track trending return gifts and competitor strategies.
  • E-commerce Marketers: To identify high-demand keywords for Furusato Nozei portals.
  • Content Creators: To find trending topics for blogs or social media regarding tax deductions.
  • Market Researchers: To monitor the seasonality and shifting interests in the Hometown Tax sector.

⚙️ How it works

  1. News Ingestion: The workflow triggers on a schedule and fetches the latest "Furusato Nozei" articles from Google News via RSS.
  2. AI Analysis & Extraction: An AI Agent (using OpenRouter) summarizes the news cluster and identifies the most viable search keyword (e.g., "Scallops," "Travel Vouchers," or specific municipalities).
  3. Data Validation: The workflow queries the Google Trends API (via SerpApi) to retrieve search volume history for the extracted keyword in Japan.
  4. Strategic Reporting: A second AI Agent analyzes the search trend data alongside the keyword to generate a market insight report.
  5. Delivery: The final report is formatted and sent directly to a Slack channel.

🛠️ Requirements

To use this workflow, you will need:

  • n8n (Version 1.0 or later recommended).
  • OpenRouter API Key (or you can swap the model nodes for OpenAI/Anthropic).
  • SerpApi Key (Required to fetch Google Trends data programmatically).
  • Slack Account (with permissions to post to a channel).

🚀 How to set up

  1. Configure Credentials:
    • Add your OpenRouter API key to the Chat Model nodes.
    • Add your SerpApi key to the Google Trends API node.
    • Connect your Slack account in the Send a message node.
  2. Check the RSS Feed:
    • The RSS Read node is pre-configured for "Furusato Nozei" (ふるさと納税). You can leave this as is.
  3. Regional Settings:
    • The workflow is pre-set for Japan (jp / ja). If you need to change this, check the Workflow Configuration and Google Trends API nodes.
  4. Schedule:
    • Enable the Schedule Trigger node to run at your preferred time (default is 9:00 AM JST).

🎨 How to customize

  • Change the Topic: While this is optimized for Furusato Nozei, you can change the RSS feed URL to track other Japanese market trends (e.g., NISA, Inbound Tourism).
  • Swap AI Models: The template uses OpenRouter, but you can easily replace the "Chat Model" nodes with OpenAI (GPT-4) or Anthropic (Claude) depending on your preference.
  • Adjust AI Prompts: The AI prompts are currently in Japanese to match the content. You can modify the system instructions in the AI Agent nodes if you prefer English reports.

n8n Workflow: AI-Powered Google News Analysis and Slack Reporting

This n8n workflow automates the process of monitoring market trends by fetching news from Google News, analyzing it with an AI agent, and reporting the findings to Slack. It's designed to keep you informed about specific topics with intelligent summaries.

What it does

This workflow performs the following steps:

  1. Triggers on Schedule: The workflow starts at a predefined schedule (e.g., daily, hourly).
  2. Fetches Google News RSS: It reads the RSS feed from Google News for a specified search query (e.g., "ふるさと納税" - Furusato Nozei).
  3. Filters News Items: It processes each news item from the RSS feed.
  4. Prepares Data for AI Analysis: It structures the news article title and description into a format suitable for an AI agent.
  5. Analyzes News with AI Agent: An AI agent (powered by OpenRouter Chat Model) analyzes the news content. This agent is configured to summarize the article and provide insights, potentially focusing on market trends or sentiment.
  6. Aggregates AI Responses: It collects all the AI-generated analyses into a single output.
  7. Formats Output: It prepares the aggregated AI analysis for reporting.
  8. Posts to Slack: The summarized and analyzed news is posted to a designated Slack channel, providing concise updates.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google News RSS Feed: Access to a Google News RSS feed for your desired search query.
  • OpenRouter Account & API Key: An account with OpenRouter and an API key to utilize their chat models for AI analysis.
  • Slack Account & Webhook/API Token: A Slack workspace and either a Slack webhook or an API token configured to allow posting messages to a channel.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • OpenRouter Chat Model (ID: 1281):
      • Click on the "AI Agent" node (ID: 1119), then select the "OpenRouter Chat Model" (ID: 1281) within its configuration.
      • You will need to set up an OpenRouter credential. Provide your OpenRouter API Key.
    • Slack (ID: 40):
      • Click on the "Slack" node (ID: 40).
      • Configure your Slack credential. This typically involves providing an OAuth Access Token or a Webhook URL.
      • Specify the target Slack channel where the reports should be posted.
  3. Customize the Workflow:
    • Schedule Trigger (ID: 839): Adjust the schedule to your preferred frequency (e.g., daily, every few hours).
    • RSS Read (ID: 37):
      • Update the "URL" field to the Google News RSS feed URL for your specific search query. For example, if you're monitoring "ふるさと納税 market trends", ensure the URL reflects this.
    • Edit Fields (Set) (ID: 38): Review and adjust how the news data is being prepared for the AI agent if you need different fields or formatting.
    • AI Agent (ID: 1119):
      • Review the "System Message" and "User Message" within the AI Agent node. This is where you instruct the AI on how to analyze the news. For example, you might refine the prompt to specifically ask for market trend analysis, sentiment, or key takeaways.
    • Slack (ID: 40): Customize the message content and formatting that will be sent to Slack.
  4. Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

This workflow will now automatically fetch news, analyze it using AI, and report the insights to your Slack channel on the defined schedule.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601