Automated gold price threshold alerts via LINE with web scraping
Gold Price Alert
This workflow template, "Gold Price Alert," is designed to monitor gold prices at regular intervals and send real-time notifications via LINE when the price exceeds a specified threshold. By leveraging the power of web scraping and automated alerts, this template ensures you stay informed about significant changes in gold prices without manual intervention.
Whether you're an investor, trader, or simply someone interested in tracking gold prices, this workflow provides a reliable and customizable solution for staying updated.
Who Is This Template For?
- Investors & Traders: Who want to monitor gold prices and receive alerts when the price reaches a specific threshold.
- Financial Analysts: Looking for automated tools to track commodity prices. Businesses: Operating in industries where gold prices impact operations or profitability.
- Automation Enthusiasts: Seeking to build workflows that combine web scraping, data processing, and messaging platforms.
What Problem Does This Workflow Solve?
Tracking gold prices manually can be time-consuming and prone to oversight, especially if you’re monitoring multiple sources or need alerts for specific thresholds.
This workflow solves that problem by:
- Automatically checking gold prices every 6 hours using a schedule trigger.
- Extracting the latest price from a trusted source (e.g., Gold Traders Association ).
- Sending instant notifications via LINE when the price exceeds a predefined threshold (e.g., 52,300 THB).
- Reducing the need for constant manual checks while ensuring timely updates.
What This Workflow Does
- Scheduled Trigger: The workflow is triggered every 6 hours to check the current gold price.
- Fetch Webpage Content: It retrieves the HTML content of the webpage displaying the latest gold prices.
- Extract Price Data: Using CSS selectors, the workflow extracts the relevant price data (e.g., buying price) from the HTML content.
- Filter Prices: The extracted price is converted into a numeric format and compared against a predefined threshold (e.g., 52,300 THB). Alerts are only sent if the price exceeds this value.
- Send Notification via LINE: If the condition is met, the workflow sends a notification to your LINE account with the current gold price.
Setup Guide
Pre-Requisites
- Access to the LINE Developers Console to configure your API Access Token
- Basic knowledge of HTML and CSS selectors for extracting data from webpages.
- Familiarity with n8n workflows and JSON formatting.
Step-by-Step Setup
- Configure the Schedule Trigger: Set the interval to 6 hours or adjust it based on your preference.
- Set Up Webpage Fetching: Update the URL in the HTTP Request node to point to the webpage containing the gold price data.
- Extract Price Data: Use the HTML Extractor node to specify the CSS selector for the price element (e.g., #DetailPlace_uc_goldprices1_lblBLBuy).
- Set Price Threshold: Modify the threshold value in the If node to match your desired alert level (e.g., 52,300 THB).
- Configure LINE Push API: Replace the placeholder to field in the Send Line Message node with your LINE user ID to ensure notifications are sent to the correct account.
Test the Workflow:
- Run the workflow manually to verify that it fetches the price, evaluates the condition, and sends notifications correctly.
How to Customize This Workflow to Your Needs
- Change the Interval: Adjust the schedule trigger to check prices more or less frequently (e.g., hourly or daily).
- Monitor Multiple Prices: Extend the workflow to extract and compare additional price points (e.g., selling price, international rates).
- Integrate Other Platforms: Replace the LINE notification with integrations for Telegram, email, or SMS.
- Expand Use Cases: Adapt the workflow to track other commodities or financial indicators by modifying the webpage URL and CSS selectors.
Why Use This Template?
- Real-Time Alerts: Stay informed about significant changes in gold prices without manual intervention.
- Customizable Thresholds: Set your own price thresholds to receive alerts tailored to your needs.
- Easy Integration: Seamlessly integrates with LINE for quick setup and minimal maintenance.
- Scalable: Easily extend the workflow to monitor multiple data points or integrate with other platforms.
Automated Gold Price Threshold Alerts via LINE with Web Scraping
This n8n workflow automates the process of monitoring gold prices from a web source and sending alerts to a LINE messaging channel if the price falls below a predefined threshold. It's designed to keep you informed about significant price movements without manual checking.
What it does
This workflow performs the following steps:
- Schedules Execution: The workflow runs automatically at regular intervals (e.g., every hour, daily) as configured by the
Schedule Triggernode. - Fetches Gold Price Data: It makes an HTTP request to a specified URL (likely a gold price tracking website or API) to retrieve the latest gold price information.
- Parses HTML Content: The retrieved HTML content is then processed to extract the relevant gold price data using the
HTMLnode. This typically involves using CSS selectors to pinpoint the exact element containing the price. - Evaluates Price Threshold: An
Ifnode checks if the extracted gold price is below a certain predefined threshold. - Sends LINE Alert (Conditional): If the gold price is indeed below the threshold, the workflow would typically proceed to send a notification to a LINE messaging channel. (Note: The provided JSON does not include a LINE node, but based on the directory name, this would be the logical next step in a complete implementation.)
Prerequisites/Requirements
To fully utilize this workflow, you will need:
- n8n Instance: A running instance of n8n (self-hosted or cloud).
- Web Scraping Target: A publicly accessible website or API that provides current gold prices. You will need to identify the specific URL and the CSS selector for the gold price element.
- LINE Account & Channel (Implied): If you intend to send alerts to LINE, you will need a LINE Developers account, a LINE Messaging API channel, and the necessary channel access token and user ID(s) or group ID(s). (This part is inferred from the directory name as the provided JSON does not contain a LINE node).
Setup/Usage
- Import the Workflow:
- Download the provided JSON content.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure the Schedule Trigger:
- Open the "Schedule Trigger" node.
- Set your desired interval for the workflow to run (e.g., every 1 hour, every day at a specific time).
- Configure the HTTP Request Node:
- Open the "HTTP Request" node.
- Set the
URLto the gold price website or API you want to scrape. - Ensure the request method is appropriate (usually GET).
- Configure the HTML Node:
- Open the "HTML" node.
- You will need to configure the
CSS Selectorto accurately extract the gold price from the HTML response of the HTTP Request. This is crucial for the workflow to function correctly. - Test the node with sample data to ensure it extracts the price as expected.
- Configure the If Node:
- Open the "If" node.
- Set the condition to compare the extracted gold price (from the HTML node's output) against your desired threshold. For example,
{{ $json.goldPrice < 1800 }}if your threshold is $1800.
- Add LINE Notification Node (Recommended):
- Connect the "True" output of the "If" node to a new LINE node (or a similar messaging node like Slack, Telegram, Email, etc., depending on your preference).
- Configure the LINE node with your LINE Channel Access Token and the recipient ID(s) to send the alert message.
- Craft the message content to include the current gold price and the alert reason.
- Activate the Workflow: Once all configurations are complete, activate the workflow in n8n.
The workflow will now automatically check the gold price at your specified intervals and send an alert if it drops below your set threshold.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.