Workflow Templates

Overview Stop recording, editing, and posting manually. This workflow takes any topic or idea as input, uses Claude to write a punchy short-form script, ElevenLabs to generate a natural voiceover, and Creatomate to render the finished video with captions and your brand visuals and then stores it in Google Drive and alerts your team. Built for TikTok, Instagram Reels, and YouTube Shorts. How it works Submit a video topic via the built-in form or replace it with a Schedule Trigger to pull topics from a Google Sheet automatically Claude Sonnet writes a 45-60 second script with a strong hook, clear value points, and a call to action ElevenLabs converts the script to a natural-sounding MP3 voiceover in your chosen voice The audio is uploaded to Google Drive and sent to Creatomate, which renders the final video with animated captions and your brand template The workflow waits for Creatomate to finish rendering, then retrieves the completed video file The finished video is uploaded to Google Drive for team access A Slack alert is sent with the Drive link and every run is logged to Google Sheets Setup steps Settings node — Open Configure Brand Settings and fill in your brand name, niche, tone, ElevenLabs Voice ID, Creatomate Template ID, and Drive folder name. This is the only node you need to personalise Claude AI — Add your Anthropic API key to the Claude Sonnet sub-node from console.anthropic.com ElevenLabs — Get your API key from elevenlabs.io and replace YOUR_ELEVENLABS_API_KEY in Generate Voiceover. Find your Voice ID under Voices in ElevenLabs Creatomate — Sign up at creatomate.com, create a short-form video template with Voiceover, Caption, Title, and Brand elements, then add your API key and Template ID Google Drive — Connect your Google account in Upload Audio to Drive and Upload Video to Drive. Create two folders and add their IDs to each node Slack — Connect Slack in Notify Team - Video Ready and set your channel. Right-click and Disable if unused Google Sheets — Create a sheet called Video Log with columns: Timestamp, Video ID, Topic, Platform, Script Preview, Status, Drive Link TEST : Submit a test topic through the form to verify the full pipeline end to end

Overview AI-powered workflow that transforms any article URL into platform-optimized social media posts for LinkedIn, Twitter (X), and Reddit. Uses Mozilla Readability for content extraction, multi-agent AI with RAG from viral LinkedIn post database, and interactive review forms for content refinement before auto-publishing. Key Capabilities: Extracts article content: title, author, text, images, metadata Generates LinkedIn posts using 3-agent system with viral pattern matching Creates Twitter threads under 280 characters with article links Auto-posts to Reddit with AI-selected flairs Interactive review/regeneration workflow with feedback loops Auto-publishes with images or links to all platforms How It Works Stage 1: Article Content Extraction Form Submission: User enters article URL (with basic auth protection) URL Validation: Checks if valid URL format Article Scraping: HTTP request fetches HTML content Readability Parsing: Mozilla Readability extracts: Clean article text (removes ads, navigation, etc.) Title, author, excerpt Word count, site name Featured image (from og:image, twitter:image, or first img tag) Error Handling: Returns user-friendly error if scraping fails Stage 2: LinkedIn Post Generation (3-Agent System) Agent 1: LinkedIn Post Strategist Input**: Extracted article content (title, text, author, excerpt) RAG Process**: Queries Supabase vector database for similar viral LinkedIn posts Analysis**: Identifies patterns, hooks, formatting, engagement triggers Output**: Strategic insights and viral content patterns Agent 2: LinkedIn Post Generator Input**: Article content + strategist insights Process**: Creates post using viral patterns from database Rule**: Must include article URL in post Output**: Draft LinkedIn post Agent 3: LinkedIn Post Formatter Input**: Generated post Process**: Removes extraneous content Applies Sans Serif Bold Unicode for emphasis (𝗯𝗼𝗹𝗱 𝘁𝗲𝘅𝘁) Removes markdown/em dashes Ensures clean formatting Output**: Polished, ready-to-post LinkedIn content Review Loop: User sees formatted post in web form Options: "Regenerate" or "Continue" If regenerate: Provide feedback → Agent creates new version Second review form with same options After 2 iterations or approval, proceeds to image selection Stage 3: Image Handling for LinkedIn Image Preview: Shows extracted article image User Choice: "Yes" → Downloads image, posts with text + image "Continue without Image" → Posts with text + article link preview Auto-Publish: Posts to LinkedIn with selected format Stage 4: Twitter (X) Post Generation Parallel process (runs alongside LinkedIn): Twitter Agent: Creates tweet under 280 characters (including spaces) Must include article URL Uses GPT-4.1 or GPT-5 models Tweet Review Form: User reviews generated tweet Regeneration Loop (if requested): User provides feedback Re-generate Tweet Agent creates new version Second review form Auto-Tweet: Posts with article image attachment Stage 5: Reddit Post Automation Parallel process (runs alongside LinkedIn/Twitter): Subreddit Selection: User picks from dropdown (r/n8n, r/mcp, r/technews) Flair Retrieval: Fetches available flairs for selected subreddit via Reddit API AI Flair Selection: GPT-4o-mini analyzes article title + available flairs Selects most appropriate flair Auto-Post: Submits link post to Reddit with title and selected flair How To Use Prerequisites API Credentials Required OpenAI API: GPT-4.1, GPT-5, GPT-5-mini, GPT-4o-mini access Supabase: Vector database with linkedin_post table (from previous workflow) LinkedIn OAuth2: Developer app with posting permissions Twitter OAuth2: Developer account with tweet permissions Reddit OAuth2: App credentials with submit permissions Basic Auth: For form password protection Setup Steps 1. Configure Form Access Open "On Article Submission" node Set up basic auth credentials for form protection Get form URL from webhook settings 2. Link Vector Database Ensure Supabase vector store has viral LinkedIn posts (use previous workflow to populate) Verify "LinkedIn Post Vector Store" credentials Check "Embedding" node has OpenAI API key 3. Set Up Social Media APIs LinkedIn: Configure "Text + Image" and "Text + Link" nodes Update person parameter with your LinkedIn profile ID Add OAuth2 credentials Twitter: Configure "Tweet" and "Re-generated Tweet" nodes Add Twitter OAuth2 credentials Reddit: Update subreddit list in "Reddit Form" dropdown (customize to your subreddits) Configure "Get Flair", "Reddit Post" nodes with OAuth2 Update subreddit name in "Reddit Post" query parameters 4. Configure AI Models Verify all OpenAI credentials in language model nodes Models used: GPT-4.1, GPT-5, GPT-5-mini (adjust based on your access)

How it works This workflow turns a Google Drive folder into a fully automated YouTube publishing pipeline. Whenever a new video file is added to the folder, the workflow generates all YouTube metadata using AI, uploads the video to your YouTube channel, deletes the original file from Drive, sends a Telegram confirmation, and can optionally post to Instagram and Facebook using permanent system tokens. High-level flow: Detects new video uploads in a specific Google Drive folder. Downloads the file and uses AI to generate: • a polished first-person YouTube description • an SEO-optimized YouTube title • high-ranking YouTube tags Uploads the video to YouTube with the generated metadata. Deletes the original Drive file after upload. Sends a Telegram notification with video details. (Optional) Posts to Instagram & Facebook using permanent system user tokens. Set up steps Setup usually takes a few minutes. Add Google Drive OAuth2 credentials for the trigger and download/delete nodes. Add your OpenAI (or Gemini) API credentials for title/description/tag generation. Add YouTube OAuth2 credentials in the YouTube Upload node. Add Facebook/Instagram Graph API credentials if enabling cross-posting. Replace placeholder IDs (Drive folder ID, Page ID, IG media endpoint). Review sticky notes in the workflow—they contain setup guidance and token info. Activate the Google Drive trigger to start automated uploads.

How it works This workflow automatically publishes Instagram and Facebook posts using Google Sheets as a content calendar. Users add post details to a sheet, and the workflow handles scheduling, image processing, posting, and status updates without manual intervention. Step-by-step Scheduled Trigger The workflow runs automatically at a fixed interval (for example, every 15 minutes) to check for posts that are ready to be published. Configuration & Credentials A configuration step stores reusable values such as spreadsheet ID, sheet name, and platform settings, keeping the workflow easy to customize and secure. Data Retrieval & Filtering Posts are read from Google Sheets and filtered to include only rows marked as “Pending” and scheduled for the current time or earlier. Image Handling If an image link is provided, the workflow downloads the image from Google Drive. If no image is present, the post continues as text-only. Platform Routing Based on the selected platform (Instagram, Facebook, or both), the workflow routes the post to the appropriate publishing path. Social Media Publishing The post is published to Instagram and/or Facebook using the connected business account credentials. Status Update After publishing, the workflow updates the original Google Sheet with the post status (Success or Failed), published timestamp, and error message if applicable.

A robust n8n workflow designed to enhance Telegram bot functionality for user management and broadcasting. It facilitates automatic support ticket creation, efficient user data storage in Redis, and a sophisticated system for message forwarding and broadcasting. How It Works Telegram Bot Setup: Initiate the workflow with a Telegram bot configured for handling different chat types (private, supergroup, channel). User Data Management: Formats and updates user data, storing it in a Redis database for efficient retrieval and management. Support Ticket Creation: Automatically generates chat tickets for user messages and saves the corresponding topic IDs in Redis. Message Forwarding: Forwards new messages to the appropriate chat thread, or creates a new thread if none exists. Support Forum Management: Handles messages within a support forum, differentiating between various chat types and user statuses. Broadcasting System: Implements a broadcasting mechanism that sends channel posts to all previous bot users, with a system to filter out blocked users. Blocked User Management: Identifies and manages blocked users, preventing them from receiving broadcasted messages. Versatile Channel Handling: Ensures that messages from verified channels are properly managed and broadcasted to relevant users. Set Up Steps Estimated Time**: Around 30 minutes. Requirements**: A Telegram bot, a Redis database, and Telegram group/channel IDs are necessary. Configuration**: Input the Telegram bot token and relevant group/channel IDs. Configure message handling and user data processing according to your needs. Detailed Instructions**: Sticky notes within the workflow provide extensive setup information and guidance. Live Demo Workflow Bot: Telegram Bot Link (Click here) Support Group: Telegram Group Link (Click here) Broadcasting Channel: Telegram Channel Link (Click here) Keywords: n8n workflow, Telegram bot, chat ticket system, Redis database, message broadcasting, user data management, support forum automation

Description This n8n workflow automatically publishes posts to Instagram Business accounts and Facebook Pages using Google Sheets as your content calendar. You schedule posts in the sheet, and n8n processes them, uploads media (if any), posts via Meta’s Graph API, and updates the sheet with success/failure. n8n How it Works Google Sheets rows marked “Pending” and due for publishing are picked up by a scheduled trigger. Posts are then routed to the proper social platforms and published via Meta’s Graph API. Finally, n8n writes back the publish status and timestamp to the sheet. n8n 🧠 Step-by-Step 1️⃣ Scheduled Trigger The workflow automatically checks Google Sheets at fixed intervals (e.g., every 15 min) for posts that are ready (status = Pending, publish time reached). 2️⃣ Config & Credentials Store reusable settings including: Google Sheets ID & Sheet name Meta App credentials (App ID, App Secret) Access token for Meta Graph API Instagram Business Account ID Facebook Page ID These configs make the workflow modular and secure. 3️⃣ Setup: Create a Meta (Facebook) App To post via the Graph API, you must first set up a Meta developer app: 🔗 Create App (Meta for Developers): Go here to start: https://developers.facebook.com/docs/development/create-an-app/ Steps: Log in at Meta for Developers. Click Create App and choose Business as the app type. Facebook Developers Add a name and contact email. In the app dashboard, Add Product → choose Instagram Graph API and Facebook Login. 📌 After creation, your app will have an App ID and App Secret in Settings → Basic — save both for n8n. 4️⃣ Link Accounts & Get IDs Before publishing you need: Instagram Business account (not a personal account) Facebook Page linked to that Instagram account Link them in Facebook Page settings → Linked Accounts. Then, generate an access token with permissions (instagram_basic, pages_show_list, etc.) using the Graph API Explorer and your new Meta app. From the token response or via Graph API calls, extract: Facebook Page ID Instagram Business Account ID These go into your n8n nodes for publishing. 5️⃣ Fetch & Filter Posts Read rows from Google Sheets and filter those ready to publish (status = Pending, scheduled time reached). 6️⃣ Image Handling If an image link is present, download or retrieve it (Google Drive or external URL). If not, continue with a text-only post. 7️⃣ Platform Routing Route the post to: Instagram publishing branch Facebook publishing branch (or both depending on the sheet’s platform column) 8️⃣ Posting via Meta Graph API Instagram Use Graph API endpoints to create and publish media containers and then make the publish call. Facebook Use Graph API to post to the Facebook Page feed (via /feed or /photos endpoint). 9️⃣ Update Sheet Status After each attempt, update Google Sheets with: Status (Success/Fail) Published timestamp

Who is this template for? This template is ideal for small businesses, agencies, and solo professionals who want to automate appointment scheduling and caller follow-up through a voice-based AI receptionist. If you’re using tools like Google Calendar, Airtable, and Vapi (Twilio), this setup is for you. What problem does this workflow solve? Manual call handling, appointment booking, and email coordination can be time-consuming and prone to errors. This workflow solves that by automating the receptionist role: answering calls, checking calendar availability, managing appointments, and storing call summaries—all without human intervention. What this workflow does This Agent Receptionist manages inbound voice calls and scheduling tasks using Vapi and Google Calendar. It checks availability, books or updates calendar events, sends email confirmations, and logs call details into Airtable. The workflow includes built-in logic for slot management, email triggers, and storing call transcripts. Setup Instructions Duplicate Airtable Base: Use this Airtable base templateBASE LINK Import Workflow: Load provided JSON into your n8n instance. Credentials: Connect your Google Calendar and Airtable credentials in n8n. Activate Workflow: Enable workflow to get live webhook URLs. Vapi Configuration: Paste provided system prompt into Vapi Assistant. Link the appropriate webhook URLs from n8n (GetSlots, BookSlots, UpdateSlots, CancelSlots, and end-of-call report). Disclaimer Optimized for cloud-hosted n8n instances. Self-hosted users should verify webhook and credential setups.

This workflow template, "Personal Assistant to Note Messages and Extract Namecard Information" is designed to streamline the processing of incoming messages on the LINE messaging platform. It integrates with powerful tools like Microsoft Teams , Microsoft To Do , OneDrive , and OpenRouter.ai to handle tasks such as saving notes, extracting namecard information, and organizing images. Whether you’re managing personal productivity or automating workflows for teams, this template offers a versatile and customizable solution. By leveraging this workflow, you can automate repetitive tasks, improve collaboration, and enhance efficiency in handling LINE messages. Who Is This Template For? This template is ideal for: Professionals: Who want to save important messages, extract data from namecards, or organize images automatically. Teams: Looking to integrate LINE messages into tools like Microsoft Teams and Microsoft To Do for better collaboration. Developers: Seeking to build intelligent workflows that process text, images, and other inputs from LINE. Business Owners: Who need to manage customer interactions, follow-ups, and task tracking efficiently. What Problem Does This Workflow Solve? Managing incoming messages on LINE can be time-consuming, especially when dealing with diverse input types like text, images, and namecards. This workflow solves that problem by: Automatically identifying and routing different message types (text, images, namecards) to appropriate actions. Extracting structured data from namecards and saving it for follow-up tasks. Uploading images to OneDrive and saving text messages to Microsoft Teams or Microsoft To Do for easy access. Sending real-time feedback to users via LINE to confirm that their messages have been processed. What This Workflow Does Receive Messages via LINE Webhook: The workflow is triggered whenever a user sends a message (text, image, or other types) to the LINE bot. Display Loading Animation: A loading animation is displayed to reassure the user that their request is being processed. Route Input Types: The workflow uses a Switch node to determine the type of input: Text Starting with "T": Adds the message as a task in Microsoft To Do. Plain Text: Saves the message in Microsoft Teams under a designated channel (e.g., "Notes"). Images: Identifies whether the image is a namecard, handwritten note, or other content, then processes accordingly. Unsupported formats trigger a polite response indicating the limitation. Process Namecards: *Images * If the image is identified as a namecard, the workflow extracts structured data (e.g., name, email, phone number) using OpenRouter.ai and saves it to Microsoft To Do for follow-up tasks. Save Images to OneDrive: Images are uploaded to OneDrive, renamed based on their unique message ID, and linked in Microsoft Teams for reference. Send Feedback via LINE: The workflow replies to the user with confirmation messages, such as "[ Task Created ]" or "[ Message Saved ]." Setup Guide Pre-Requisites Access to the LINE Developers Console to configure your webhook and bot. Accounts for Microsoft Teams , Microsoft To Do, and OneDrive with API access. An OpenRouter.ai account with credentials to access models like GPT-4o. Basic knowledge of APIs, webhooks, and JSON formatting. Step-by-Step Setup 1) Configure the LINE Webhook: Go to the LINE Developers Console and set up a webhook to receive incoming messages. Copy the Webhook URL from the Line Webhook node and paste it into the LINE Console. Remove any "test" configurations when moving to production. 2) Set Up Microsoft Integrations: Connect your Microsoft Teams, Microsoft To Do, and OneDrive accounts to the respective nodes in the workflow. 3) Set Up OpenRouter.ai: Create an account on OpenRouter.ai and obtain your API credentials. Connect your credentials to the OpenRouter nodes in the workflow. Test the Workflow: Simulate sending text, images, and namecards to the LINE bot to verify that all actions are processed correctly. How to Customize This Workflow to Your Needs Add More Actions: Extend the workflow to handle additional input types or integrate with other tools. Enhance Image Processing: Use advanced OCR tools to improve text extraction from complex images. Customize Feedback Messages: Modify the reply format to include emojis, links, or other formatting options. Expand Use Cases: Adapt the workflow for specific industries, such as sales or customer support, by tailoring the actions to relevant tasks. Why Use This Template? Versatile Automation: Handles multiple input types (text, images, namecards) with ease. Seamless Integration: Connects LINE messages to popular productivity tools like Microsoft Teams and To Do. Structured Data Extraction: Extracts and organizes data from namecards, saving time and effort. Real-Time Feedback: Keeps users informed about the status of their requests with instant notifications.

Personal Portfolio CV Rag Chatbot - with Conversation Store and Email Summary Target Audience This template is perfect for: Individuals looking to create a working professional and interactive personal portfolio chatbot. Developers interested in integrating RAG Chatbot functionality with conversation storage. 1. Description Create a stunning Personal Portfolio CV with integrated RAG Chatbot capabilities, including conversation storage and daily email summaries. 2.Features: Training: Setup Ingestion stage Upload your CV to Google Drive and let the Drive trigger updates to read your resume cv and convert it into your vector database (RAG purpose). Modify any parts as needed. Chat & Track: Use any frontend/backend interface to call the chat API and chat history API. Reporting Daily Chat Conversations: Receive daily automatic summaries of chat conversations. Data stored via NocoDB. 3.Setup Guide: Step-by-Step Instructions: Ensure all credentials are ready. Follow the notes provided. Ingestion: Upload your CV to Google Drive. The Drive triggers RAG update in your vector database. You can change the folder name, files and indexname of the vector database accordingly. Chat: Use any frontend/backend interface to call the chat API (refer to the notes for details) . [optional] Use any frontend/backend interface to call the update chat history API (refer to the notes for details). 3.Tracking Chat: Get daily automatic summaries of chat conversations.Format email conversations report as you like. You are ready to go!

Who is this for? This workflow template is ideal for marketers, designers, content creators, and developers who need to generate custom text-based images dynamically. Whether you want to create social media graphics, placeholder images, or text-based LinkedIn carousels, this workflow provides a simple, no-code solution using an API that requires no authentication. What problem does this workflow solve? Creating text-based images often requires design software or complex integrations with graphic tools. This workflow eliminates that hassle by allowing users to generate images with custom text, font styles, colors, and background colors using a simple HTTP request. It’s perfect for automating image generation without relying on external tools or manual effort. What this workflow does This workflow leverages an HTTP request to a free API that generates text-based images dynamically. Here's what it enables you to do: Define custom image text Set image dimensions (width x height) Choose a background color and text color using hex codes Select a font family and font size Specify the image format (PNG, JPG, or WebP) The generated image can be used immediately, making it ideal for automating content creation workflows. Setup Open the workflow in n8n. Modify the Set node to define your preferred image properties: text: The message displayed on the image. size: Image dimensions (e.g., 500x300 pixels). backgroundColor: Hex color code for the background. textColor: Hex color code for the text. fontFamily: Select from available font options (e.g., Pacifico, Ubuntu). fontSize: Define the text size. type: Choose the image format (PNG, JPG, or WebP). Execute the workflow to generate an image. The HTTP request returns the generated image, ready for use. How to customize this workflow 1. Adjust the Set node values to match your desired design. 2. Use dynamic data for text, allowing personalized images based on user input. 3. Automate image delivery by adding email or social media posting nodes. 4. Integrate this workflow into larger automation sequences, such as content marketing pipelines.

This workflow automates the management of DigitalOcean Droplet snapshots by listing all droplets, filtering based on the number of snapshots, and deleting excess snapshots before creating new ones. It ensures your droplet snapshots stay organized and within a manageable limit, preventing unnecessary storage costs due to an excess of snapshots. Who is this for? This workflow is perfect for users managing DigitalOcean Droplets and looking to automate the process of snapshot creation and cleanup to save on storage costs and maintain efficient resource management. It’s useful for DevOps teams, cloud administrators, or any developer leveraging DigitalOcean for their infrastructure. What problem is this workflow solving? When managing multiple DigitalOcean Droplets, snapshots can quickly accumulate, taking up space and increasing storage costs. Manually deleting and creating snapshots can be time-consuming and inefficient. This automation solves this problem by automating the snapshot management process, ensuring that no more than a defined number of snapshots are kept per droplet. What this workflow does Runs every 48 hours: The workflow is triggered by a cron node that runs every 48 hours, ensuring timely snapshot management. List all droplets: The workflow retrieves all droplets in the DigitalOcean account. Retrieve snapshots: For each droplet, the workflow retrieves a list of existing snapshots. Filter snapshots: If the number of snapshots exceeds 4, the workflow filters for snapshots that need to be deleted. Delete snapshots: Excess snapshots are automatically deleted based on the filter criteria. Create new snapshot: After cleaning up, the workflow creates a new snapshot for each droplet, ensuring that backups are always up-to-date. Setup DigitalOcean API Key: You’ll need to configure the HTTP Request nodes with your DigitalOcean API key. This key is required for authenticating requests to list droplets, retrieve snapshots, delete snapshots, and create new ones. Snapshot Threshold: By default, the workflow is set to keep no more than 4 snapshots per droplet. This can be adjusted by modifying the filter node conditions. Set Execution Frequency: The cron node is set to run every 48 hours, but you can adjust the timing to suit your needs. How to customize this workflow Adjust Snapshot Limit**: Change the value in the filter node if you want to keep more or fewer snapshots. Modify Run Frequency**: The workflow runs every 48 hours by default. You can change the frequency in the cron node to run more or less often. Enhance with Notifications**: You can add a notification node (e.g., Slack or email) to alert you when snapshots are deleted or created. Workflow Summary This workflow automates the management of DigitalOcean Droplet snapshots by keeping the number of snapshots under a defined limit, deleting the oldest ones, and ensuring new snapshots are created at regular intervals.

How it works Collects articles from your preferred RSS feeds. Rates and tags each article using an AI model (e.g., QWEN 14B-s4), filtering for relevance and quality. Summarizes high-rated articles with a language model (e.g., Gemma3 4B) for quick, digestible reading. Checks for duplicates to avoid sending the same article twice. Formats and sends the top articles as an HTML newsletter via Gmail, using OAuth2 authentication. Stores records in a Postgres database, tracking which articles have been sent and their ratings. Requirements Postgres Account AI Models (if you work localy use Ollama) In the cloud you have to change Ollama node to your prefered Model Node RSS Feed of your desire Google Auth2, if you want to use Gmail Recommendations Use n8n local version for this workflow Here are some more informations: https://github.com/falks-ai-workbench/n8n_newsletter