Track changes of product prices
This workflow automatically tracks changes on specific websites, typically in e-commerce where you want to get information about price changes.
Prerequisites
- Basic knowledge of HTML and JavaScript
Nodes
- Execute Command nodes create a file named
kopacky.jsonin the/data/folder (Make sure that n8n has the permissions to make changes to the folder in your setup) and clean data. - Cron node triggers the workflow at regular intervals (default is 15 minutes), depending on how often you want to crawl URLs of your watchers.
- Function Item node (Change me) adds the URL watchers. You can put as many URLs (watchers) as you want by changing the JavaScript code in the node. There are four properties for each watcher:
|Property|Meaning| |-|-| |slug|Unique identifier for the watcher.| |link|URL of the website where you want to track changes.| |selector|CSS selector of the HTML tag, where your price is placed. You can use browser web tools to get a specific selector.| |currency|Currency code in which your price is set.|
- Function Item node (Init item) saves all required data from each watcher to the
kopacky.jsonfile. - HTTP Request node fetches data from the website.
- HTML Extract node extracts the required information from the webpage.
- Send Email nodes (NotifyBetterPrice) send you an email when there is an issue with getting the price, and when a better price is available (this could happen if the website is down, your tracking product is not available anymore, or the owner of the website changed the selector or HTML).
- IF nodes filter the incoming data and route the workflow.
- Move Binary Data nodes convert the JSON file to binary data.
- Write Binary File nodes write the product prices in the file.
NOTE: This is the first (beta) version of this workflow, so it could have some issues. For example, there is an issue with getting content of those websites, where the owner of the website blocks any calls from unknown foreign services - it's typical protection against crawlers.
n8n Workflow: Basic Workflow Template
This n8n workflow serves as a foundational template, demonstrating a variety of core n8n nodes and their potential connections. While the provided JSON defines a collection of nodes, it does not explicitly connect them into a functional flow. This README describes the individual components and their general purpose, which can be combined to build more complex automations.
What it does
This workflow showcases several fundamental n8n nodes, each designed for a specific purpose in an automation pipeline:
- Cron: Triggers the workflow at scheduled intervals (e.g., daily, hourly, specific days).
- Send Email: Sends email notifications.
- Execute Command: Runs shell commands on the n8n host server.
- Function Item: Allows for custom JavaScript code execution to transform or manipulate data.
- HTTP Request: Makes requests to external APIs or web services.
- If: Implements conditional logic to route data based on specified criteria.
- Read Binary File: Reads binary file content from the n8n host server.
- Start: The initial trigger for manual execution or when the workflow is called by another process.
- Write Binary File: Writes binary data to a file on the n8n host server.
- Convert to/from binary data: Facilitates conversion between binary and non-binary data types.
- HTML Extract: Extracts specific data from HTML content using CSS selectors.
Prerequisites/Requirements
- n8n Instance: An active n8n instance to import and run the workflow.
- SMTP Server (for Send Email): If you intend to use the "Send Email" node, you will need access to an SMTP server and its credentials.
- External APIs (for HTTP Request): If utilizing the "HTTP Request" node, access to the target API and any necessary authentication (e.g., API keys, tokens) will be required.
- File System Access (for Read/Write Binary File, Execute Command): The "Read Binary File", "Write Binary File", and "Execute Command" nodes interact with the file system of the server hosting n8n. Ensure appropriate permissions and paths are configured.
Setup/Usage
-
Import the Workflow:
- In your n8n instance, go to "Workflows".
- Click "New" or "Import from JSON".
- Paste the provided JSON content into the import dialog.
-
Configure Nodes:
- Cron: Set your desired schedule for the workflow to run automatically.
- Send Email: Configure the SMTP credentials, recipient, sender, subject, and body of the email.
- Execute Command: Specify the command to be executed. Be cautious when using this node as it can interact with your server's operating system.
- Function Item: Write your custom JavaScript code to process data as needed.
- HTTP Request: Define the URL, method (GET, POST, etc.), headers, and body for your API requests.
- If: Define the conditions for routing data.
- Read Binary File: Specify the path to the binary file you want to read.
- Write Binary File: Specify the path and filename for the output binary file.
- HTML Extract: Provide the HTML content (e.g., from an HTTP Request) and the CSS selectors to extract specific elements.
- Convert to/from binary data: Configure how you want to handle binary data conversion.
-
Connect Nodes:
- Currently, the nodes in the provided JSON are not connected. Drag connection lines between the output of one node and the input of another to build your desired automation logic. For example:
- Connect "Cron" to "HTTP Request" to periodically fetch data.
- Connect "HTTP Request" to "HTML Extract" to parse the response.
- Connect "HTML Extract" to "If" to make decisions based on extracted data.
- Connect "If" (true branch) to "Send Email" to send an alert if a condition is met.
- Currently, the nodes in the provided JSON are not connected. Drag connection lines between the output of one node and the input of another to build your desired automation logic. For example:
-
Activate the Workflow: Once configured and connected, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
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.