Automatically update n8n version
🔄 n8n Workflow: Check and Update n8n Version
This workflow automatically checks if the local n8n version is outdated and, if so, creates a file to signal an update is needed.
🖥️ Working Environment
- Operating System: Ubuntu 24.04
- n8n Installation: Docker container
📁 Project Directory Structure
n8n/ ├── check_update.txt ├── check-update.sh ├── compose.yml ├── update_n8n.cron
🧾 File Descriptions
check_update.txt
Contains a single word:
true: Update is neededfalse: No update required
check-update.sh
#!/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
if grep -q "true" /home/sysadmin/n8n/check_update.txt; then
# Place your update logic here
echo "Update needed - please insert update logic"
echo true > /home/sysadmin/n8n/check_update.txt
fi
Purpose:
- Checks the contents of
check_update.txt - If it contains
true, executes update logic (currently a placeholder) - Resets
check_update.txttotrue
update_n8n.cron
SHELL=/bin/sh
10 5 * * * /bin/sh /home/sysadmin/n8n/check-update.sh
Purpose:
- Runs the
check-update.shscript daily at 5:10 AM - Uses
/bin/shas the shell environment
🧩 n8n Workflow Breakdown
1. Schedule Trigger 🕓
- Purpose: Triggers the workflow every day at 5:00 AM
- Node Type: Schedule Trigger
2. Get the latest n8n version 🌐
- Purpose: Fetches the latest version of n8n from npm
- Endpoint:
https://registry.npmjs.org/n8n/latest - Node Type: HTTP Request
3. Get Local n8n version 🖥️
- Purpose: Retrieves the currently running n8n version
- Endpoint:
http://192.168.100.18:5678/rest/settings - Node Type: HTTP Request
4. If 🔍
- Purpose: Compares the local and latest versions
- Condition: If not equal → update is needed
5. SSH1 🧾
- Purpose: Writes the result to a file on the host via SSH
- Logic:
echo "{{ $('If').params.conditions ? 'false' : 'true' }}" > check_update.txt
Effect: Updates check_update.txt with "true" if an update is needed, "false" otherwise.
🛠️ Setting up Crontab on Ubuntu
1. Register the cron job with:
crontab update_n8n.cron
2. Verify that your cron job is registered:
crontab -l
✅ Result
- 5:00 AM – n8n workflow checks versions and writes result to
check_update.txt - 5:10 AM – Cron runs
check-update.shto respond to update flag
n8n Workflow: Automatic n8n Version Update Placeholder
This n8n workflow serves as a foundational structure, demonstrating the use of core n8n nodes for scheduling, making HTTP requests, applying conditional logic, and executing SSH commands. While the directory name suggests an "automatic n8n version update," the provided JSON does not explicitly implement that logic. Instead, it offers a template that could be extended for such a purpose.
What it does
This workflow outlines a sequence of operations without specific configurations for an actual n8n update. It includes the following steps:
- Triggers on a Schedule: The workflow starts based on a predefined schedule.
- Makes an HTTP Request: It is set up to perform an HTTP request, which could be used to fetch information (e.g., latest n8n version from an API).
- Applies Conditional Logic: An "If" node is included, allowing for branching logic based on the outcome of previous steps (e.g., "If a new version is available...").
- Executes SSH Commands: An SSH node is present, indicating the capability to run commands on a remote server, which would be essential for performing an actual update.
Prerequisites/Requirements
- n8n Instance: An active n8n instance to host and run the workflow.
- SSH Credentials: If the SSH node is to be used for remote execution, appropriate SSH credentials (e.g., private key or username/password) configured in n8n.
- API Endpoints: If the HTTP Request node is intended to fetch data, knowledge of the relevant API endpoints.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Schedule Trigger: Adjust the "Schedule Trigger" node to your desired frequency for checking updates.
- Configure HTTP Request (Optional): If you intend to fetch version information, configure the "HTTP Request" node with the appropriate URL and authentication.
- Configure If Node (Optional): Set up the conditions in the "If" node to evaluate whether an update is necessary based on the data from the HTTP request.
- Configure SSH Node (Optional): If you plan to use this workflow for actual updates, configure the "SSH" node with your server's credentials and the commands required to update n8n (e.g.,
npm update -g n8nor Docker commands). - Activate the Workflow: Once configured, activate the workflow to enable scheduled execution.
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.
By Ranjan DailataTwo-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.
By Matt@VeraisonLabsGenerate 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
By Daniel Nkencho