Automate Singapore COE Price Analysis & Purchase Timing with GLM-4.5 AI Predictions

Introduction Automates Singapore COE price tracking, predicts trends using AI, and recommends optimal car purchase timing. Scrapes LTA data biweekly, analyzes historical trends, forecasts next 6 bidding rounds, and sends alerts when buying windows appear—saving time and identifying cost-saving opportunities.

How it Works Biweekly trigger scrapes LTA COE data → processes historical trends → AI predicts 6-month prices → compares current vs forecast → generates buy/wait recommendations → alerts sent via Gmail or Telegram.

Setup Steps Add NVIDIA/OpenAI API credentials in n8n Connect Google Sheets for data storage Authenticate Gmail/Telegram for notifications Schedule trigger for Wednesdays 8PM SGT Configure alert thresholds in conditional nodes

Workflow Schedule Trigger → HTTP Request (Scrape LTA) → Data Processing → Google Sheets (Store) → AI Prediction → Analysis Engine → Conditional Logic → Gmail/Telegram Notification

Workflow Steps Scraping: Extract COE prices from OneMotoring Processing: Calculate moving averages, volatility, seasonal trends Storage: Save to Google Sheets with timestamps Prediction: AI forecasts next 6 bidding rounds Analysis: Compare current vs predicted prices, generate recommendation Notification: Alerts via email/Telegram

Prerequisites NVIDIA/OpenAI API key, Google account (Sheets), Gmail/Telegram for notifications, basic COE category knowledge

Use Cases First-time buyers monitoring price dips, fleet managers timing bulk purchases

Customization Add economic indicators, integrate car loan calculators, track parallel imported car prices

Benefits Saves hours of manual monitoring, captures 10–15% price dips, provides data-driven purchase timing (potential $5K–$15K savings)

0
Downloads
1
Views
8.72
Quality Score
intermediate
Complexity
Author:Cheng Siong Chin(View Original →)
Created:11/15/2025
Updated:11/16/2025

🔒 Please log in to import templates to n8n and favorite templates

Workflow Visualization

Loading...

Preparing workflow renderer

Comments (0)

Login to post comments