Generate logos and images with consistent visual styles using Imagen 3.0
This n8n template allows you to use AI to generate logos or images which mimic visual styles of other logos or images. The model used to generate the images is Google's Imagen 3.0. With this template, users will be able to automate design and marketing tasks such as creating variants of existing designs, remixing existing assets to validate different styles and explore a range of designs which would have been otherwise too expensive and time-consming previously. How it works A form trigger is used to capture the source image to reference styles from and a prompt for the target image to generate. The source image is passed to Gemini 2.0 to be analysed and its visual style and tone extracted as a detailed description. This visual style description is then combined with the user's initial target image prompt. This final prompt is given to Imagen 3.0 to generate the images. A quick webpage is put together with the generated images to present back to the user. If the user provided an email address, a copy of this HTML page will be sent. How to use Ensure the workflow is live to share the form publicly. The source image must be accessible to your n8n instance - either a public image of the internet or within your network. For best results, select a source image which has strong visual identity as these will allow the LLM to better describe it. For your prompt, refer to the imagen prompt guide found here: https://ai.google.dev/gemini-api/docs/image-generationimagen-prompt-guide Requirements Gemini for LLM and Imagen model. Cloudinary for image CDN. Gmail for email sending. Customising this workflow Feel free to swap any of these out for tools and services you prefer. Want to fully automate? Switch the form trigger for a webhook trigger!
By JimleukDownload recently liked songs automatically with Spotify
Purpose This workflow enables you to listen to your recent favorites in very hight quality offline without sacrificing all of your storage. How it works This workflow automatically creates a playlist in Spotify named "Downloads" which periodically gets updated so it always contains only a defined amount of the latest liked songs. This enables only the Downloads playlist to set for automatic downloading and thus free up space on the device. Setup The workflow is ready to go. Just select your Spotify credentials and activate the workflow. In Spotify just enable automatic downloads on the automatically created Downloads folder after the first workflow run. Current limitations This setup currently supports a maximum of 50 songs in the Downloads Playlist. This is due to the paylod limits defined by Spotify encountered in the Get liked songs node. Implementing batching would solve the issue.
By MarioMulti-channel workflow error alerts with Telegram, Gmail & messaging apps
The Error Notification workflow is designed to instantly notify you whenever any other n8n workflow encounters an error, using popular communication channels like Telegram and Gmail—with optional support for Discord, Slack, and WhatsApp. 💡 Why Use Error Notification workflow? Immediate Awareness: Get instant alerts when workflows fail, preventing unnoticed errors and downtime. Multi-Channel Flexibility: Notify your team via Telegram, Gmail, and optionally Slack, Discord, or WhatsApp. Detailed Context: Receive rich error information including the error message, node name, time, and execution link for quicker fixes. Easy Integration: Built with native n8n nodes and customizable code, simple to adopt without complex setup. Open Source & Free: Use and adapt this workflow at no cost, making professional error monitoring accessible. ⚡ Who Is This For? n8n Workflow Developers: Quickly spot and respond to automation issues in development or production. Operations Teams: Maintain uptime and swiftly troubleshoot errors across multiple workflows. Small to Medium Businesses: Gain professional error alerting without expensive monitoring tools. Automation Enthusiasts: Enhance your automation reliability with real-time failure notifications. ❓ What Problem Does It Solve? This workflow embedd error detection and notification directly within your n8n instance. It automates the process of catching errors as they occur, compiling meaningful context, and delivering it instantly via your preferred messaging platforms. This drastically reduces your response time to issues and streamlines error management, improving your automation reliability and operational confidence. 🔧 What This Workflow Does ⏱ Trigger: Listens for any error generated in your n8n workflows using the n8n Error Trigger node. 📎 Step 2: Executes a Code node that formats a detailed error message capturing workflow name, error node, description, timestamp, and an execution URL. 🔍 Step 3: Sends the formatted error notification to multiple communication channels: Telegram and Gmail by default, plus optionally Discord, Slack, and WhatsApp (disabled by default). 💌 Step 4: Delivers rich, parsed HTML-formatted messages to ensure error readability and immediate actionability. 🔐 Setup Instructions Import the provided .json file into your n8n instance (Cloud or self-hosted). Set up credentials: Gmail OAuth credentials for sending emails via Gmail node Telegram API credentials for Telegram notifications (Optional) Discord Webhook URL credential for Discord notifications (Optional) Slack Webhook credential for Slack notifications (Optional) WhatsApp connection credentials (if enabled) Customize the Code node if needed to adjust the error message format or target chat IDs. Update the chat IDs and recipient details in each notification node according to your channels. Test the workflow by manually triggering an error in another workflow to verify proper notifications. 🧩 Pre-Requirements Active n8n instance (cloud or self-hosted) with version supporting Error Trigger node Telegram bot credentials and chat ID (Optional) Gmail, Discord, Slack, or WhatsApp accounts and webhook credentials if you want to use those channels 🛠️ Customize It Further Enable and configure additional notification nodes like Slack or WhatsApp to fit your team's communication style. Customize the error message template in the Code node to include extra metadata or format it differently (e.g., markdown). Integrate with incident management tools via webhook nodes or create tickets automatically on error. 🧠 Nodes Used Error Trigger Code Telegram Gmail Discord (disabled) Slack (disabled) WhatsApp (disabled) Sticky Note (for description) 📞 Support Made by: khaisa Studio Tag: notification,error,monitoring,workflow,automation,alerts Category: Monitoring & Alerts Need a custom? Need a custom? contact me on LinkedIn or Web
By Khairul MuhtadinRun Apache Airflow DAG and retrieve XCom value
Run Apache Airflow DAG and Retrieve XCom Value What this workflow does This workflow integrates the Apache Airflow API DAGRun and XCom. It enables n8n to trigger Airflow DAGs and retrieve the execution results. Preparation: Update Airflow API Link Prefix Navigate to the airflow-api node. Update the prefix of the Airflow API link in the format: http(s)://ip:port. Example: https://airflow.example.com Configure Authentication Go to the Airflow: dag_run node. Update the Basic Auth credentials with your Airflow username and password. Repeat this step for Airflow: dagrun - state and Airflow: dagrun - get result nodes. Security Note: Using Basic Authentication requires storing credentials in plaintext. If possible, consider using API Keys or Tokens for enhanced security. An example is setting Airflow's API Authentication to basic\_auth. Choose other authentication methods if needed. Ensure the user account has the following permissions: can create on DAG Runs, can read on DAG Runs, can read on XComs, can edit on DAGs, and can read on DAGs. How to Use: To execute this workflow, use the Execute Sub-workflow node with the following input parameters: dag\_id: The DAG ID (name) in Airflow that you want to trigger. task\id: The Task ID (name) from which you want to retrieve the XCom return\value. conf: Input data for the Airflow DAG run. wait: Delay (in seconds) between each Airflow: dag_run - state check. wait\time: The maximum time (in seconds) to wait for Airflow: dagrun - state before returning an error. Output: The workflow returns the XCom result from Airflow: dag_run - get result. The XCom return_value is stored in the value field.
By Antonio CheongSend daily real estate construction updates via Gmail & WhatsApp with Google Sheets
This n8n template demonstrates how to create an automated construction progress notification system for real estate companies. The workflow triggers daily at 8:00 AM IST to check a Google Sheet for contractor construction reports, automatically processes the data, and sends comprehensive project updates to buyers via email and WhatsApp. Perfect for real estate developers wanting to maintain transparent communication with buyers and ensure timely project status updates. Good to know Daily automated monitoring ensures no construction updates are missed Multi-channel communication (Email + WhatsApp) reaches buyers through their preferred method Smart filtering system only processes today's reports for relevant updates Comprehensive logging tracks all notification activities for audit purposes Built-in alert system notifies administrators when contractors fail to submit reports Handles multiple projects and contractors simultaneously without data conflicts How it works Daily Monitoring Workflow System triggers automatically every day at 8:00 AM IST to check for new construction reports Google Sheet configuration is set with Sheet ID, sheet name, and today's date for filtering All construction data is read from the designated Google Sheet containing contractor submissions Advanced filtering isolates only today's reports based on the Date column for processing Report Processing Workflow System checks if any construction reports were submitted for the current date If reports are found: Detailed notifications are prepared and sent to all registered buyers If no reports are found: Alert notifications are sent to administrators about missing submissions All project data is compiled into comprehensive summaries with progress percentages and status updates Notification Distribution Workflow Email notifications contain detailed construction summaries with all project information WhatsApp messages provide concise updates with key progress indicators and status Messages are personalized with project names, completion percentages, and contractor details Multiple recipients receive notifications simultaneously through both communication channels Activity Logging Workflow All notification activities are logged with precise timestamps and recipient information Success logs record project count, recipient numbers, and delivery confirmation Warning logs capture instances when no reports are found for administrative follow-up Complete audit trail maintains compliance and tracking for project management Google Sheet Structure Construction Reports Sheet Date - Report submission date (DD/MM/YYYY format) Project_Name - Name of the construction project Contractor_Name - Name of the responsible contractor Location - Project location or site address Progress_Percentage - Current completion percentage (0-100%) Status - Current project status (On Track, Delayed, Completed, etc.) Work_Description - Detailed description of today's construction activities Issues - Any problems or challenges encountered (optional) Budget_Status - Financial status update (On Budget, Over Budget, Under Budget) Next_Milestone - Upcoming project milestone or target date How to use Import the workflow into your n8n instance and configure Google Sheets integration Set up your Google Sheet with the required column structure for construction reports Configure email SMTP settings for professional construction update delivery Set up WhatsApp Business API for instant mobile notifications to buyers Add buyer email addresses and WhatsApp numbers to the notification recipient lists Contractors submit daily reports to the Google Sheet before 8:00 AM for same-day processing System automatically processes and distributes updates to all registered buyers Monitor logs for delivery confirmation and missing report alerts Requirements Google Sheets account for construction report data storage and management Email service integration (Gmail, SMTP, or corporate email system) WhatsApp Business API account for mobile messaging capabilities n8n instance with Google Sheets, Email, and WhatsApp connectors properly configured Valid credentials for all integrated services (Google OAuth, SMTP, WhatsApp API) Customising this workflow Construction update automation can be adapted for different project types and development scales Try popular use-cases such as weekly progress summaries, milestone notifications, or emergency construction alerts The workflow can be extended to include photo attachments from construction sites, weather impact assessments, and safety compliance reporting Integration possibilities include CRM systems for buyer management, project management tools for contractor coordination, and financial systems for budget tracking Notification scheduling can be adjusted for different time zones, multiple daily updates, or project-specific timing requirements Advanced features can include buyer feedback collection, contractor performance ratings, and automated delay notifications with mitigation plans
By Oneclick AI SquadMonitor construction stock & send low inventory alerts with Google Sheets
Description Automates stock maintenance for real estate (e.g., construction materials, office supplies). Monitors stock levels, processes additions/deductions, and sends low-stock alerts via email. Uses Google Sheets for data storage and n8n for workflow automation. Essential Information Daily workflow to check and update stock levels. Stores data in a Google Sheet for easy access and analysis. Sends email notifications for low-stock items based on predefined thresholds. Supports dynamic stock updates via API or form input (configurable). System Architecture Stock Monitoring Pipeline: Daily Stock Check: Triggers daily to initiate stock monitoring. Fetch Stock Data: Retrieves current stock levels from Google Sheet. Update Stock Levels: Processes stock additions or deductions. Alert Generation Flow: Check Low Stock: Identifies items below threshold. Send Email Alert: Notifies stakeholders of low-stock items. Data Management: Update Google Sheet: Saves updated stock levels and timestamps. Implementation Guide Import the workflow JSON into n8n. Configure Google Sheets credentials and specify sheet ID. Set up SMTP credentials for email alerts. Test stock update and low-stock alert processes. Monitor email delivery and adjust thresholds as needed. Technical Dependencies Google Sheets API for stock data storage and retrieval. SMTP service for sending low-stock email alerts. n8n for workflow automation and orchestration. Optional: Web form or API for dynamic stock updates. Database & Sheet Structure Stock Inventory Sheet (StockInventory): Columns: item, quantity, threshold, last_updated, unit Example: Cement, 100, 20, 2025-07-29T08:00:00Z, Bags Customization Possibilities Modify Update Stock Levels node to integrate with a form or API for real-time updates. Adjust Check Low Stock node to set custom thresholds per item. Customize email alert format in Send Email Alert node. Add error-handling nodes for invalid stock updates. Integrate with a dashboard tool for visual stock monitoring.
By Oneclick AI SquadProcess & summarize PDFs from email & messaging apps with OpenAI GPT
Process PDFs from Gmail, Outlook, Telegram and WhatsApp with OpenAI Transform PDF documents into actionable insights automatically across multiple platforms. This workflow monitors emails and messaging platforms for PDF attachments, extracts content, and delivers AI-powered summaries. Who's it for Business professionals, teams, and organizations needing automated PDF analysis from emails and messaging platforms. Perfect for processing contracts, reports, invoices, and documents requiring quick review. How it works Monitors Gmail and Outlook for PDF attachments while receiving PDFs via Telegram bot and WhatsApp Business API. Uses OpenAI to extract text and generate structured summaries with executive overviews, key points, important details, insights, and document type identification. Automatically routes summaries back to original senders. Requirements Gmail/Outlook OAuth2 credentials Telegram Bot API token via @BotFather WhatsApp Business API account OpenAI API key How to set up Configure API credentials in respective nodes, update configuration variables for phone numbers and notification settings, then test with sample PDFs. How to customize Modify AI models, customize prompts, adjust response formatting, extend file support, add notification channels, or integrate with external systems. Perfect for automating document workflows across communication channels.
By papcyCreate dynamic API Gateway with HTTP Router and workflow orchestration
Overview This workflow provides a universal webhook endpoint that dynamically routes incoming requests to different subflows. It allows you to manage multiple API-like endpoints from a single entry point, while ensuring proper error handling and consistent responses. How it works Webhook Receiver – A single URL accepts requests. Method Detection – Branches capture the request method. Route Resolver – Matches the action parameter and method against your route configuration. Execute Subflow – If valid, the matching workflow is executed. Error Handling – If invalid, the workflow responds with a clear status code and JSON error. About the action parameter The action query parameter is the key that controls routing: In your Routes Config, every route is defined with an action name, a list of allowed HTTP methods, and the target subflow ID. When a request comes in, the workflow looks up the provided action in this config. If the action is valid and the method is allowed, the corresponding subflow is executed. If not, the workflow returns a structured error. In other words: Config side → map action → subflow ID Request side → send ?action=... → determines which subflow runs This makes action both the mapping key in the configuration and the control key for triggering the correct logic. Setup steps Import the workflow into n8n. Define your routes in the Routes Config node. Each route contains: action name allowed HTTP methods target subflow ID --- This workflow is useful if you want to: Expose multiple clean API endpoints without creating many Webhook nodes Ensure consistent error handling across all endpoints Keep your n8n setup more structured and maintainable --- 👉 A practical solution to turn n8n into a flexible and maintainable API gateway.
By Sven RösserCreate & upload AI videos to YouTube with Kling 2.5 & auto-SEO
++What it is++ An automated workflow for creating Kling 2.5 videos and posting them to YouTube. The workflow is divided into three main phases: Create Kling 2.5 Video Wait for Video Processing Post to YouTube ++Create Kling 2.5 Video++ This phase handles the initial video creation based on user input. Type Prompt: A form trigger allows the user to input details for the video, including: Prompt: A simple scenario for the video. Video Style: (e.g., Dialogue, Monologue, Advertisement, Documentary) Aspect Ratio: (e.g., 16:9, 9:16, 1:1) Videography (AI Refinement): Refines the user’s prompt into a detailed “script-to-screen” format suitable for video generation. FAL.AI Request: The refined prompt is sent to the Fal.ai Kling 2.5 model via an HTTP request to generate the video. Store Data: Details of the video request, including the date requested, the refined prompt, and the request URL, are stored in a Google Sheet. ++Wait for Video Processing++ Wait 5 mins: The workflow pauses for 5 minutes. This waiting period is necessary as it typically takes 3–5 minutes for the video to be ready after the generation request. ++Post to YouTube++ This phase focuses on generating YouTube SEO details and uploading the video. YT Video SEO (AI Generation): An AI agent (using OpenRouter’s OpenAI GPT-5 Mini model) acts as a YouTube SEO specialist and viral content strategist. It generates the following details for the YouTube video: Video Title: A compelling title (less than 6 words). Video Description: A detailed description. Video Tags: Relevant tags to maximize discoverability. The AI agent is configured to follow guidelines for virality and YouTube’s tag limits. Structured Output: Parses the structured JSON output from the AI agent. Get Keywords: Extracts and formats the video tags into a comma-separated list suitable for YouTube. Fetch Video Credentials: Fetches the video URL and other credentials from Fal.ai. Download Video: Downloads the generated video file. Post on YouTube: The video is uploaded to YouTube using the generated title, description, and tags. ++Setup++ To run this workflow, you need to set up credentials in n8n for: OpenRouter: Generate API key from your OpenRouter account. (Tutorial) Google Sheets: Uses OAuth 2.0. Connect by authenticating your Google account. YouTube Data API: Configure credentials to allow posting videos to YouTube (Follow this section of another Tutorial).
By Ari NakosINST - the n8n installer: deploy workflows with automatic credential mapping
INST: The n8n Workflow Installer This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute. That's right, now you can package up dozens of workflows and send your client(s) a single workflow to run, that will create them all and auto-assign all the credentials. This workflow installs 3 files when you run it, demonstrating the functionality. Just make your own mods to the system, repackage it, and you are ready to go! --- Requirements An n8n instance with API access enabled and an access key Optional: GitHub and OpenAI access keys --- What This Workflow Does Installs 3 additional workflows, demonstrating the functionality One of the workflows is a packager, that you configure for your own needs Two example workflows demonstrate functionality, and can be deleted --- Step-by-Step Setup Run the Workflow This will get the example and tool workflows on your instance. Package Your Content Configure the packager, then run it to produce a base64-compressed version of your files. Customize the Installer Make your own copy of the installer, and set the base64 payload. Deploy the Installer Export your installer script. Now, anyone you send it to will get all your packaged workflows when they execute it. --- How to Use This Workflow This workflow is meant to be reused and adapted. You can: Integrate it into a deployment pipeline Turn it into a subworkflow for dynamic installs Extend it to include triggers, permission settings, or test runs If you frequently deploy or share n8n assets, this installer gives you a repeatable way to do it with confidence.
By WyethCoordinate move-out cleaning and repair tasks with Google Sheets, Slack, email and Claude
Who this is for Property management companies managing frequent tenant move-outs across multiple units. What this workflow does Automatically schedules and coordinates move-out cleaning and repair tasks, sends vendor instructions, notifies internal teams, tracks completions, and logs everything for reporting. How it works Cron triggers workflow before lease end. AI generates personalized move-out instructions and checklists. Vendors and property management teams are notified. Completion updates logged in Google Sheets. Optional AI suggests follow-up actions for delays. How to set up Connect tenant data, configure Cron, Slack, Email, and Task Manager credentials. Customize AI prompts and verify notification flows. Requirements Google Sheets Email & Slack credentials AI Node access Task Manager (Trello/Asana/etc.) Built by QuarterSmart. Created by Hyrum Hurst.
By Hyrum Hurst