Workflow Templates

This workflow allows users to convert a 2D image into a 3D model by integrating multiple AI and web services. The process begins with a user uploading or providing an image URL, which is then sent to a generative AI model capable of interpreting the content and generating a 3D representation in .glb format. The model is then stored and a download link is returned to the user. Main Steps Trigger Node: Initiates the workflow either via HTTP request, webhook, or manual execution. Image Upload or Input: The image is acquired via direct upload or URL input. API Integration: The image is sent to a 3D generation API (e.g., a service like Kaedim, Luma Labs, or a custom AI model). Model Generation: The external API processes the image and creates a 3D model. File Storage: The resulting 3D model is stored in cloud storage (e.g., S3, Google Drive, or a local server). Response to User: A download link for the 3D model is returned to the user via the same communication channel (HTTP response, email, or chat). Advantages Automation**: Eliminates the need for manual 3D modeling, saving time for artists, developers, and designers. AI-Powered**: Leverages AI to generate realistic and usable 3D models from simple 2D inputs. Scalability**: Can be triggered automatically and scaled up to handle many requests via n8n's automation. Integration-Friendly**: Easily extendable with other services like Discord, Telegram, or marketplaces for 3D assets. No-Code Configuration**: Built with n8n’s visual interface, making it editable without programming knowledge. How It Works Trigger: The workflow can be started manually ("When clicking ‘Test workflow’") or automatically at scheduled intervals ("Schedule Trigger"). Data Retrieval: The "Get new image" node fetches data from a Google Sheet, including the model image, product image, and product ID. 3D Image Creation: The "Create 3D Image" node sends the image data to the Fal.run API (Trellis) to generate a 3D model. Status Check: The workflow periodically checks the request status ("Get status" and "Wait 60 sec.") until the job is marked as "COMPLETED." Result Processing: Once completed, the 3D model URL is retrieved ("Get Url 3D image"), the file is downloaded ("Get File 3D image"), and uploaded to Google Drive ("Upload 3D Image"). Sheet Update: The final 3D model URL is written back to the Google Sheet ("Update result"). Set Up Steps Prepare Google Sheet: Create a Google Sheet with columns: IMAGE MODEL and 3D RESULT (empty). Example sheet: Google Sheet Template. Obtain Fal.run API Key: Sign up at Fal.ai and get an API key. Configure the Authorization header in the "Create 3D Image" node with Key YOURAPIKEY. Configure Workflow Execution: Run manually via the Test workflow button. For automation, set up the Schedule Trigger node (e.g., every 5 minutes). Verify Credentials: Ensure Google Sheets, Google Drive, and Fal.run API credentials are correctly set in n8n. Once configured, the workflow processes new entries in the Google Sheet, generates 3D models, and updates the results automatically. Need help customizing? Contact me for consulting and support or add me on Linkedin.

What it is- I wanted to create a simple, easy-to-use, MCP server for your Discord bot(s). How to set up- Literally all you do is select your bot auth (or crease a new Discord Bot auth if you havn't entered your key in n8n before) and that's IT! How to use it- You can now ask your bot to do things via any MCP client, including from within N8N workflows! Note: If you need an example, you can check out my simple quickstart Discord MCP Server that uses 4o to send messages to channels on your server and users who are members of the server the bot is in. Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator.. All 100% free? Join the community

Create, iterate, and share! Transform a single image through multiple scenes while maintaining consistency. ✨ What this workflow does This template showcases FLUX.1 Kontext - Black Forest Labs' in-context image generation model that excels at maintaining character features across multiple transformations. Combined with the Upload Post community node for effortless multi-platform social media posting, you can create and share compelling visual stories instantly. The workflow demonstrates FLUX Kontext's core strength: character consistency across multiple image generations. Starting with a single input image, it: 🖼️ Loads an initial character image (example: a cute animal mascot) 📝 Defines multiple scene transformation prompts 🔄 Iteratively generates new scenes while preserving exact character features 🎯 Maintains visual consistency by reusing binary data from previous generations 📱 Auto-posts the complete transformation series to multiple social platforms simultaneously 🚀 Key Features: The Consistency Advantage Character Preservation**: FLUX Kontext's signature feature - maintains character features and style across transformations (requires specific prompting techniques) Iterative Context Building**: Each generation uses the previous image as context, creating visual continuity Binary Data Reuse**: Smart workflow design that feeds output from one generation as input to the next Multi-Scene Storytelling**: Transform your character across different environments while keeping them recognizable One-Click Multi-Platform Posting*: Upload Post eliminates the tedious process of posting to each platform individually 📱 Why use Upload Post? Posting the same content to TikTok, Instagram, LinkedIn, YouTube, Facebook, X (Twitter), and Threads individually is time-consuming and error-prone. The Upload Post service* simplifies this process: ✅ Connect once, post everywhere: Link all your social media accounts to Upload Post ✅ Single API call: Post to multiple platforms with one simple node ✅ No more platform juggling: Skip the endless switching between apps and dashboards ✅ Consistent timing: All platforms get your content simultaneously ✅ Trusted by 3,751+ users: Proven solution for content creators and marketers Instead of spending 30+ minutes manually posting to each platform, Upload Post does it all in seconds with a single n8n node! 🛠️ Prerequisites Required Accounts: Black Forest Labs API: Create account at dashboard.bfl.ai Get your API key for FLUX Kontext Pro access Upload Post Account: Sign up at upload-post.com* Connect your social media profiles (TikTok, Instagram, LinkedIn, YouTube, Facebook, X/Twitter, Threads) Get API credentials for automated posting Free tier available: 10 uploads/month 💡 Perfect For: Character Designers** maintaining brand character integrity across scenes Social Media Managers** creating engaging visual story series without manual posting Brand Marketers** ensuring character consistency across campaigns Storytellers** building visual narratives with consistent protagonists Agencies** managing multiple client accounts efficiently 🔧 Customization Options: Modify transformation prompts** to create your own character journey Adjust iteration steps** Change initial character image** Configure social platform targeting** (choose which platforms to post to) Customize post content** and formatting Experiment with different consistency scenarios** \ Affiliate link*

AI-Powered Product Research & SEO Content Automation Skip the guesswork and manual effort — this n8n flow automates the entire process of researching your product's online competition and generating high-quality SEO content. Whether you're launching a new product or optimizing existing listings, this workflow leverages real-time web data and AI-driven copywriting to deliver: 📈 Search-optimized metadata (Title, Description, Keywords) 🛍️ Engaging product descriptions tailored for marketing 📊 Auto-organized output ready for use in your content or e-commerce platform All of this happens with just one product title input! 🧠 How It Works • User submits a product title via a form. • The workflow uses Google Custom Search to gather real-time competitor content based on that title. • Titles, snippets, and keywords are extracted from the search results. • This information is sent to a language model (Google Gemini via LangChain) to generate: SEO-optimized metadata (Title, Description, Keywords) A compelling product description tailored for marketing • The AI-generated content is then parsed and organized into two categories: SEO data and product content. • The structured output is saved automatically into a connected Google Sheet for easy access or further automation. 🛠️ What Problems Does This Solve? Manual competitor research and writing SEO content from scratch can be: Time-consuming** Inconsistent in quality** Not optimized for search engines** Hard to scale for multiple products** This workflow automates the entire research + writing + structuring process. ✅ Key Benefits Instant Content Creation**: Generate polished SEO content in seconds. Competitor-Aware**: Pulls in real-time data from the web for relevant, market-aligned content. Scalable**: Easily repeat the process for multiple product titles with minimal effort. Data Centralization**: Stores everything in Google Sheets—great for collaboration or syncing with other tools. Customizable**: Easily extend or modify the workflow to include translations, publishing, or social media automation. ⚙️ Set-Up Steps • Connect Google Custom Search API with a valid API key and search engine ID (CX). • Connect and configure Google Gemini or LangChain with access credentials. • Provide access to a Google Sheet with columns for storing SEO and product data. • Estimated setup time: ~15–25 minutes depending on API access and sheet setup. 🚀 Let’s Get You Started with Automating Your LinkedIn Posts! Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!

Docker Registry Cleanup Template This template is designed to automatically clean up old image tags in the Docker registry and perform garbage collection. Features List all images in the registry Preserve the last 10 tags for each image (latest tag is always preserved) Delete old tags Email notification for Successful/Excused cancellation Registry garbage collection automation Failure notification in error conditions Prerequisites Docker Registry v2 API access Basic Authentication credentials SMTP email settings (for notifications) SSH node installed on n8n (for garbage collection) Installation 1. Identity Information Add the following credentials in n8n: HTTP Basic Auth**: For Registry access SSH Private Key**: For Garbage collection command Email SMTP**: For notifications 2. Set Variables Replace your-registry-url with your actual registry URL on all nodes: ‘url": ‘https://your.registry.com/v2/_catalog’. Customisation Retention Policy: Set the number of tags to be retained by changing the slice(0, 10) value in the Identify Tags to Remove node Schedule: Change the frequency of operation at the Trigger node Notification Content: Customise email templates according to your needs Notes Check DELETE operations before running in a test environment Make sure that the registry is not in read-only mode The registry may need to be put into maintenance mode for garbage collection Step Details: Retrieving image information:** The workflow starts by fetching a list of images and their associated tags from the Docker registry. Filtering and sorting:** The retrieved tags are then filtered and sorted based on specific criteria, such as creation date and tag name. Deleting old tags:** The workflow identifies old or unused tags and attempts to delete them from the registry. Sending notifications:** The workflow sends email notifications to inform the user about the status of the cleanup process, including any errors or successes. Executing additional cleanup tasks:** Finally, the workflow executes an SSH command on the Docker registry server to perform additional cleanup tasks, such as garbage collection. TL;DR In summary, this n8n template provides a robust and automated solution for managing and cleaning up Docker registries. By regularly running this workflow, users can ensure that their registry remains organized and efficient, and avoid running out of storage space.-

Functionality This workflow automates the handling of incoming emails by summarizing their content, generating appropriate responses, and validating the responses through a "Human-in-the-Loop" system. It integrates with IMAP email services (e.g., Gmail, Outlook) and uses AI models to streamline the email response process. The workflow ensures that all AI-generated responses are reviewed by a human before being sent, maintaining a high level of professionalism and accuracy. This approach is particularly useful for businesses that receive a high volume of emails and need to respond quickly while ensuring quality control. How It Works Email Trigger: The workflow starts with the Email Trigger (IMAP) node, which monitors an email inbox for new messages. When a new email arrives, it triggers the workflow. Email Preprocessing: The Markdown node converts the email's HTML content into plain text for easier processing by the AI models. Email Summarization: The Email Summarization Chain node uses an AI model (OpenAI) to generate a concise summary of the email. The summary is limited to 100 words and is written in a professional tone. Email Response Generation: The Write email node uses an AI model (OpenAI) to draft a professional response to the email. The response is based on the email content and is limited to 100 words. Human-in-the-Loop Approval: The Set Email text node prepares the drafted response for approval. The Approve Email node sends the drafted response to a human approver (e.g., an internal email address) for review. The email includes: The original message. The AI-generated response. The Approved? node checks if the response has been approved by the human reviewer. If approved, the workflow proceeds to send the response; otherwise, it stops. Sending the Response: The Send Email node sends the approved response back to the original sender. Key Features Automated Email Summarization**: Summarizes incoming emails to provide a quick overview of the content. AI-Powered Response Generation**: Drafts professional responses to emails using AI. Human-in-the-Loop Approval**: Ensures all AI-generated responses are reviewed and approved by a human before being sent. IMAP Integration**: Works with IMAP email services like Gmail and Outlook. Efficient Email Management**: Reduces the time and effort required to handle incoming emails while maintaining high-quality responses. This workflow is ideal for businesses looking to automate their email response process while maintaining control over the quality of outgoing communications. It leverages AI to handle repetitive tasks and ensures that all responses are reviewed by a human, providing a balance between automation and human oversight. Need help customizing? Contact me for consulting and support or add me on Linkedin.

The n8n Nostr Community Node is a tool that integrates Nostr functionality into n8n workflows, allowing users to interact with the Nostr protocol seamlessly. It provides both read and write capabilities and can be used for various automation tasks. Disclaimer This node is ideal for self-hosted n8n setups, as ++community nodes are not supported on n8n cloud++. It opens up exciting possibilities for integrating workflows with the decentralized Nostr protocol. n8n Community Node for Nostr n8n-nodes-nostrobots Features Write Operations**: Send notes and events (kind1) to the Nostr network. Read Operations**: Fetch events based on criteria such as event ID, public key, hashtags, mentions, or search terms. Utility Functions**: Convert events into different formats like naddr or nevent and handle key transformations between bech32 and hex formats. Trigger Events**: Monitor the Nostr network for specific mentions or events and trigger workflows automatically. Use Cases Automating note posting without exposing private keys. Setting up notifications for mentions or specific events. Creating bots or AI assistants that respond to mentions on Nostr. Installation Install n8n on your system. Add the Nostr Community Node to your instance. Configure your credentials using a Nostr secret key (supports bech32 or hex formats).

Transform static digital assets into dynamic, self-updating powerhouses that stay relevant for years to come! This workflow solves a common problem: once you publish forms, emails, or templates, their content becomes frozen in time. Users discovering them months later see outdated information, missed opportunities, and stale offers. Stop losing opportunities to stale content – make your digital assets work harder and stay fresher, automatically! Here's how it works: 🔗 Stable embed links mean your original assets never need updating 🔄 Dynamic URL redirects that automatically point to the latest pages 🖼️ Auto-updating images that showcase fresh offers or content 📅 Scheduled updates keep everything current without manual intervention Perfect for: Workflow sticky notes that become evergreen marketing billboards Registration forms with current promotions Email signatures with latest offers Website banners that stay seasonally relevant Any digital asset you want to "future-proof" The magic: Set it up once, embed the stable URLs/images in your content, then forget about it. Years later, users will still see fresh, as current information automatically pulled from your workflow. Requirements: Free accounts with GitHub (image storage) and shorten.rest (URL redirects). Both can be swapped for your preferred services. Follow me on LinkedIn for more tips on AI automation and n8n workflows!

Sync Notion Contacts to Google Contacts with Group Labels Overview Seamlessly transfer your Notion contacts to Google Contacts with organized group labels, simplifying your CRM management. This n8n workflow automates syncing contacts from a Notion database to Google Contacts, applying group labels based on Notion properties. It triggers on new or updated contacts, ensuring your Google Contacts are always organized without manual effort. ✨ Key Features 🔄 Automatic Sync: Updates Google Contacts when Notion entries are added or modified. 🏷️ Group Organization: Assigns labels to contacts based on Notion’s property_buy field. ✅ Duplicate Prevention: Marks synced contacts in Notion with a checkbox. 🛠️ Flexible Customization: Add fields like email in the “Map Notion Contact Fields” node. 📡 Community Nodes: Leverages Notion and Google Contacts nodes for integration. 📋 Prerequisites Required Credentials Notion API Token:** Set up OAuth2 in n8n. Get your token from Notion’s API settings. Google Contacts OAuth2:** Configure in n8n. See n8n’s Google Contacts guide. Notion Database:** Must include name, phone, labels (property_buy), and an “Added to Contacts” checkbox. Self-Hosted n8n:** Required for community nodes. 🔄 Workflow Process Trigger: Activates on new or updated Notion database entries. Fetch Data: Retrieves contact details (name, phone, labels) from Notion. Map Fields: Organizes data in the “Map Notion Contact Fields” node. Verify Groups: Checks for existing Google Contact groups; creates new ones if needed. Sync Contacts: Adds contacts to Google Contacts with labels. Update Notion: Marks contacts as synced. Result: Organized, labeled contacts in Google Contacts, updated automatically. 📊 Output Data Structure Name:** Contact’s first name from Notion. Phone:** Contact’s phone number. Group Labels:** Assigned from Notion’s property_buy field. Sync Status:** Notion checkbox updated to confirm sync. 💡 Pro Tips Real-Time Updates:** Set the Notion Trigger node to check every minute for faster syncing. Expand Fields:** Add email or other fields in the “Map Notion Contact Fields” node. Clean Labels:** Use consistent Notion labels for better Google Contacts organization. Test Small:** Start with a small dataset to verify setup. 🆘 Troubleshooting Authentication Issues:** Verify Notion and Google Contacts OAuth2 credentials. Sync Failures:** Ensure Notion database ID and field names match the workflow. Group Errors:** Check that property_buy labels are valid. 👨‍💻 Creator Information 👤 Created by: Dan Rahimi 🌐 Website: DanRahimi.com 📧 Email: Fa.Danial@gmail.com 📺 YouTube: @DanRahimi 👥 LinkedIn: Dan-Rahimi 🤝 Support & Contributions Enjoyed this workflow? Support my work or explore more: ☕ Buy Me a Coffee 📚 AI Automation Courses: Visit DanRahimi.com for more articles and tutorials about AI automation. Disclaimer: This workflow uses community nodes and requires a self-hosted n8n instance.

This workflow listens for incoming book request emails, extracts the user's intent using the Ollama LLM, queries book data (title, summary, details) via an API, and sends a personalized recommendation email. Ideal for automated book suggestions using LLMs and structured APIs, great for newsletters, reading clubs, and educational bots. How It Works Email Request: Triggers the workflow when a new email with a book request is received. Analyze Email with Ollama: Extracts user intent and book preferences using the Ollama LLM. Create Book Search Query: Generates a query based on the analyzed intent. Book Search API: Fetches book data (title, summary, details) from an API. Check API Response: Validates the API response for book availability. Handle No Book Found: Manages cases where no suitable book is found. Extract Book Summary: Pulls the summary from the API response. Wait for Summary Response: Pauses to ensure summary data is ready. Retrieve Book Details: Gathers additional book details. Format Book Data: Structures the book information for the recommendation. Enhance Data with Code: Refines the data using custom code. Generate Email Content: Creates a personalized email recommendation. Send Email: Delivers the recommendation to the user. How to Use Import the workflow into n8n. Configure email credentials for the Email Request node. Set up Ollama LLM API credentials and endpoint. Configure the Book Search API with appropriate credentials and endpoint. Test with a sample email requesting a book recommendation. Adjust the Generate Email Content node for custom email templates if needed. Ensure the Send Email node is linked to a valid email service. Requirements Email service API credentials (e.g., Gmail, SMTP) Ollama LLM API access Book Search API credentials Customizing This Workflow Modify the Analyze Email with Ollama node to refine intent extraction for specific genres. Adjust the Book Search API query to target different book databases. Customize the Generate Email Content node to include additional details like author bios.

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Description This workflow automates the creation of structured eBooks by generating chapters, table of contents, and content using Google Gemini Flash 2.0. Overview This n8n workflow allows users to input a topic or outline, which is then processed by Google Gemini Flash 2.0 to generate chapter titles, structured table of contents, and detailed section-wise content. The final output is formatted and exported into a Google Document, ready for review and further publishing. Who This Workflow Is For Authors & Writers** Save time by auto-generating chapter ideas, summaries, and full-length content based on a topic or outline—great for fiction and nonfiction alike. Content Marketers** Rapidly create downloadable eBooks, whitepapers, or lead magnets for campaigns without relying on long production cycles. Educators & Course Creators** Convert your syllabus, course modules, or learning outcomes into structured, well-formatted educational eBooks. Agencies & Freelancers** Offer AI-powered eBook creation as a value-added service to clients in need of fast, professional content. Entrepreneurs & Coaches** Turn your knowledge, frameworks, or training material into publish-ready books to promote your brand or monetize content. Technical Writers & Documentarians** Generate structured documentation or guides from outlines, simplifying the technical writing process with the help of AI. Tools Used n8n**: Orchestrates input handling, AI processing, formatting, and export. Google Gemini Flash 2.0**: Generates high-quality, structured content, including chapters, summaries, and body text. Google Docs**: Used to compile and format the full eBook in a collaborative document. Google Drive / Email**: Optional nodes for storing or delivering the final output. How to Install Import the Workflow**: Download and import the .json file into your n8n instance. Configure Gemini Flash 2.0**: Add your API key and set the desired creativity, length, and tone options. Provide Input**: Use a webhook or manual trigger to define the eBook topic or structure. Customize Format**: Modify prompts or Gemini instructions to match your eBook format, voice, or domain (e.g., fiction, business, technical). Export to Google Docs**: Authenticate and configure the Google Docs node to write the output chapter-wise into a new or existing document. Optional Distribution**: Connect to Google Drive or Gmail to store or send the final eBook. Use Cases Writers & Authors**: Quickly draft entire eBooks based on minimal input. Marketers**: Generate lead magnets, guides, and product documentation at scale. Educators**: Produce structured learning materials or course eBooks. Agencies**: Offer eBook creation services powered by AI. Entrepreneurs**: Turn knowledge into content assets without hiring ghostwriters. Connect with Me Email: ranjancse@gmail.com LinkedIn: https://www.linkedin.com/in/ranjan-dailata/ Get Bright Data: Bright Data (Supports free workflows with a small commission) #n8n #automation #ebookcreation #googleai #geminiflash #aiwriting #gdocs #contentautomation #ebookworkflow #nocode #contentmarketing #gemini #aiwriter #automatedpublishing #aicontent #bookcreation #geminiworkflow #ebookgenerator #gptalternative #flash20 #geminiflash2 #authorautomation #educationalcontent #aiinmarketing #n8nworkflow

About this AI Agent This workflow is designed to automate web interactions by simulating a human user, using a combination of the Agent node and AI tools powered by Airtop. How does this workflow works? Form Submission Trigger: The workflow starts with a form submission trigger node named "On form submission". This node collects user instructions for the web AI agent, including a prompt and an optional Airtop profile name for sites requiring authentication. AI Agent: The core of the workflow is the "AI Agent" node, which uses a smart web agent to manage a remote web browser. It is designed to fulfill user requests by interacting with the browser through various tools. Browser Session Management Start Browser: The "Start browser" node initiates a new browser session and window. It is essential for obtaining the sessionId and windowId required for subsequent operations. Session and Window Management: The workflow includes nodes for creating and managing browser sessions and windows, such as "Session" and "Window". Web Interaction Tools: Load URL: This node loads a specified URL into the browser window. Query: The "Query" node allows the agent to ask questions and extract information from the current web page. Click: This node simulates clicking on elements within the web page. Type: The "Type" node types text into specified elements on the page. Session Termination: The "End session" node is used to terminate the browser session once the tasks are completed. Output Handling Structured Output Parser: This node processes the agent's results into a structured format. Output: The final results are set and prepared for output. Slack Integration: Although currently disabled, there is a "Slack" node intended to send messages to a Slack channel, potentially for notifications or live view URLs. Seting up your agent Airtop API Credentials: Users must have valid Airtop API credentials to interact with the web browser tools. This includes nodes like "Click", "Query", "Load URL", "End session", "Type", "Session", and "Window". Slack API Credentials (Optional): If users want to enable Slack notifications, they need to configure Slack OAuth2 credentials. The Slack node is currently disabled but can be used to send messages to a Slack channel. Anthropic API Credentials: The "Claude 3.5 Haiku" node requires Anthropic API credentials. Users need to have access to this API to utilize the language model features.