Browse 13,012 Workflows

By Miha

This n8n template turns a small, targeted HubSpot list into tailored outreach. It scans each contact’s recent Gmail conversations, builds a lightweight persona with AI (tone, goals, pain points, decision style), then drafts a concise sales email aligned to your offer—saved to Gmail as a reviewable draft. Perfect for SDRs and founders who want personalization at scale without writing from scratch. This template was originally created by Jim Le. How it works Manual trigger** starts a controlled run. HubSpot search** pulls a focused list of contacts (e.g., hs_buying_role = DECISION_MAKER). Batch loop** processes contacts one by one. Gmail fetch** grabs up to 20 recent threads from each contact. AI persona extraction** (Information Extractor + Gemini) analyzes messages to capture: decision-making style, communication preferences, goals/motivations pain points, work style, personality traits, buying behavior, values, market awareness Variables node* sets core fields (first name, last name, email) and the *offer** you want to pitch. AI email generation* (Gemini) mirrors the contact’s tone and priorities; outputs *subject* + *HTML body**. Gmail draft** is created for the contact so a rep can skim, tweak, and send. How to use Connect HubSpot on the “Get Contacts” node and refine the filter to your segment. Connect Gmail on both read and draft nodes (same account recommended). Add Gemini key to both Gemini nodes. In Variables, update product_to_sell with your offer and confirm the contact field mappings. (Optional) Tweak the persona attributes or the email prompt for tone/length/CTA. Click Test workflow. Review drafts in Gmail, edit if needed, then send. Requirements HubSpot** (OAuth2) for contact targeting Gmail** (read + draft) Google Gemini** (API key) for persona + copy generation Notes & customization Tighter targeting:** Change the HubSpot filter (e.g., industry, territory, lifecycle stage) to keep the list small and measurable. Richer inputs:** Increase Gmail limit or include received/sent filters to capture more context (mind rate limits). Brand voice:** Add a short style guide to the email generator’s system prompt (e.g., sentence length, jargon rules, sign-off). Offer variants:** Replace product_to_sell per segment, or branch by industry to load different value props. Compliance & privacy:** Limit stored outputs to essentials; avoid copying sensitive content from threads verbatim. Auto-send option:** Swap the draft step for “send email” if you want hands-off delivery for known segments. An n8n automation workflow template by Miha.

By Miha

This n8n template auto-enriches brand-new HubSpot contacts with company details. Each day it finds contacts created in the last 24 hours (skipping free email domains), researches the company from the contact’s email domain, and writes back clean fields—no manual lookup needed. Perfect for GTM teams that want better segmentation and faster personalization from day one. How it works A daily schedule trigger starts the workflow. HubSpot: Get recently created/updated contacts** pulls the newest records. A filter keeps only contacts: created within the last 24 hours whose email domain doesn’t contain gmail.com (adjust as needed). An AI research agent (Gemini + SerpAPI): extracts the company domain from the contact’s email searches the web and returns structured JSON: company_name, industry, headquarters_city, headquarters_country, employee_count, website, linkedin, description HubSpot: Add company info** updates the contact with the enriched fields. How to use Connect HubSpot on both HubSpot nodes (OAuth2). Connect SerpAPI (paste your API key). Connect Google Gemini (Google AI Studio API key). (Optional) Edit the agent prompt to fetch more/different fields. (Optional) Tweak the filter to include/exclude other domains. Activate the workflow to run daily. Requirements HubSpot** (OAuth2) for reading/updating contacts SerpAPI** for web search results Google Gemini** for company profiling and structured output Notes & customization Free domains:** Add more exclusions (e.g., yahoo.com, outlook.com) to reduce false positives. Confidence gating:** Require website + LinkedIn before writing to HubSpot, or route low-confidence results for manual review. Field mapping:** Extend the update step with additional properties (e.g., industry tags, HQ timezone). Frequency:** Switch the trigger to hourly for faster enrichment on high-volume inbound. Data hygiene:** Normalize employee count ranges and country names to your CRM picklists. An n8n automation workflow template by Miha.

By 1Shot API

Automated Savings with 1Shot API and Aave Protocol With the increasing popularity of stablecoins like USDC, its becoming easier to pay for everyday items with crypto thanks to debit cards from issuers like MetaMask. These solutions work by processing payments on traditional payment rails then pulling the stablecoin out of your onchain account to cover the cost of the purchase. One downside is that if a stablecoin like USDC is simply sitting in your onchain account, you are missing out on competitive savings rates offered by decentralized protocols like Aave. Often the APY offered by these onchain lending protocols is much higher than those offered by traditional banks while maintaining a low-risk profile for high-quality assets like USDC or mUSD. Ideally your balance would automatically stay in something like Aave when you don't need it and automatically refill your onchain account used for payments when it gets low. This workflow, powered by 1Shot API, does just that. It also sends you real time Telegram notifications about your account balance and savings every time your account rebalances. Aave Protocol This workflow integrates the Aave lending protocol to generate savings APY on your excess USDC funds on the Base network. When your holdings in your primary Metamask smart account exceed a threshold you set, it will deposit them into the Aave Lending Pool. This results in your account receiving aBasUSDC, a deposit receipt token used to withdraw your savings at a later time. When your account drops below a refill-threshold you set, it will exchange the aBasUSDC back to USDC and put in back into your primary account so that you can spend it. Setup Instructions This workflow will automatically balance your USDC funds on Base network so that you keep funds you aren't using in Aave to earn interest and automatically move funds out of savings back into your wallet when funds get low. Create a free 1Shot API account. Generate an API key & secret and use these to create a credential for the 1Shot API node's. Click the trigger on the subworkflow to automatically import the required smart contract functions and provision a 1Shot API server wallet on Base that will relay your transactions when you are not online. Input the contract method IDs from 1Shot API into the "Savings Config" node. Set your saving thresholds in the "Savings Config" node. Create a Telegram bot and use the bot's API key to generate a credential for the Telegram nodes. Get your chat id with the bot and input it into the "Savings Config" node. Configure your desired schedule in the "Schedule" trigger node (like every 24 hours) Activate the workflow. An n8n automation workflow template by 1Shot API.

By Yves Tkaczyk

Use cases Ensure that the calls to the workflow's webhook are (a) originating from the correct GitHub repository and (b) haven't been tampered with. How it works When a secret is provided in a GitHub webhook configuration, a x-hub-signature-256 header is added to the webhook. Compute HMAC256 computes the HMAC256 signature similarly to how it was computed by GitHub. Validate HMAC256 tests for the equality of the computed value and the value provided by the header. If the values are equal then 200 is returned to GitHub and the workflow continues If the values are NOT equal then 401 is returned and the workflow ends. Note: The Stop and Error step is optional and can be removed. Removing it means that the workflow completes successfully while still returning 401 to GitHub. This means that you will not be able to easily track malicious or incorrect calls to your webhook from n8n. How to use Add the steps (1) and (2) of the workflow to your current workflow receiving webhook calls from GitHub. Update the Secret field in the Compute HMAC256 node with the same value as the secret stored in the Secret field in the GitHub webhook definition. Requirements GitHub account and repository. GitHub webhook setup with a Secret key. Key can be of any length and should be generated with a key or password generator. Who’s it for Developers or DevOps engineers who want to ensure secure webhook communication between GitHub and n8n. How to customize the workflow This is a building block for your own workflow. If you use this workflow as a base, replace step (3) with your own business logic. You can modify the Stop and Error node to log unauthorized requests or trigger alerts. ⚠️ Warning The secret is stored in plain text in the workflow. You should take this into consideration if the workflow is committed to source control or shared in any other way. Need Help? Reach out on LinkedIn or Ask in the Forum!. An n8n automation workflow template by Yves Tkaczyk.

By Avkash Kakdiya

How it works This workflow captures new subscribers from a Mailchimp list and extracts their key details. It then enriches the subscriber data using AI, predicting professional attributes and assigning a lead score. Based on the score, high-value leads are identified, and all leads are synced into HubSpot and Pipedrive. For top-priority leads, the workflow automatically creates new deals in Pipedrive for sales follow-up. Step-by-step Step-by-step 1. Capture subscriber data Mailchimp Subscriber Trigger** – Detects new signups in a Mailchimp list. Extract Subscriber Data** – Normalizes payload into clean fields like name, email, and timestamp. 2. Enrich with AI Lead Enrichment AI** – Uses AI to infer company, role, industry, intent, LinkedIn, and lead score. Parse & Merge Enrichment** – Merges AI output with subscriber info and sets defaults if parsing fails. 3. Qualify leads High-Value Lead Check** – Filters leads with a score ≥70 to flag them as priority. Create High-Value Deal** – Opens a new deal in Pipedrive for high-value leads. 4. Sync to CRMs HubSpot Contact Sync** – Updates enriched lead data in HubSpot CRM. Pipedrive Person Create** – Adds lead as a person in Pipedrive. Why use this? Automatically enrich raw Mailchimp subscribers with valuable professional insights. Score and qualify leads instantly for prioritization. Keep HubSpot and Pipedrive updated with enriched lead records. Automate deal creation for high-value opportunities, saving sales team effort. Build a seamless pipeline from marketing signups to CRM-ready opportunities. An n8n automation workflow template by Avkash Kakdiya.

By LukaszB

UX & SEO Website Analyst (Airtop + OpenAI + Gmail) This workflow automatically analyzes a website for UX and SEO quality. It uses Airtop for realistic web scraping, OpenAI for structured evaluation of metadata (title, description, and overall SEO signals), and Gmail to send professional reports. What it does Scrapes website content and metadata through an Airtop session. Evaluates SEO and UX factors (strengths, weaknesses, recommendations) with OpenAI. Generates a clear, structured report. Sends the report automatically via Gmail. Use cases Marketing agencies auditing client websites. Freelancers offering SEO/UX review services. Businesses monitoring their own website performance. Requirements Airtop account** with API access. OpenAI API key**. Gmail credentials** connected in n8n. How it works Start the flow with a target website URL. Airtop opens a session and scrapes metadata naturally. OpenAI analyzes and scores the title, description, and overall quality. Gmail sends a formatted report to your chosen recipient. Set up steps Connect Airtop, OpenAI, and Gmail credentials in n8n. Provide the target URL to analyze. Run the workflow and review the email report. Keep detailed instructions inside sticky notes in the workflow. An n8n automation workflow template by LukaszB.

By Yaron Been

This workflow automatically converts static images into dynamic videos using AI-powered animation. It saves you hours of video editing by transforming product photos, marketing images, or any static visuals into engaging video content perfect for social media and advertising campaigns. Overview This workflow automates the entire image-to-video generation process using the WAN-VIDEO 2.5 model via Replicate API. Simply provide an image URL and a text prompt describing the desired motion, and the workflow handles the video creation, status monitoring, and delivery of your animated content - typically ready in 30-120 seconds. Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Powers the WAN-VIDEO 2.5 AI model for image-to-video generation Status Monitoring**: Automated checking system with intelligent retry logic Error Handling**: Built-in resilience with comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Get Replicate API Key: Sign up at replicate.com and copy your API token Configure API Token: Replace the placeholder in the "Set API Token" node Add Your Image: Update the seed image URL in the "Add Seed Image and Prompt" node Customize Prompt: Write your desired video motion description and run the workflow Use Cases E-commerce Teams**: Animate product photos for dynamic social media ads Content Creators**: Transform static images into engaging video content for TikTok/Instagram Marketing Agencies**: Create eye-catching video ads from client product photos Educational Content**: Bring diagrams and infographics to life with motion Social Media Managers**: Generate video content at scale from existing image libraries Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ ROASPIG**: Check out ROASPIG.com for scalable media generation and automation solutions #n8n #automation #ai #videogeneration #imagetovideo #replicate #contentcreation #socialmediacontent. An n8n automation workflow template by Yaron Been.

By Incrementors

AI-Powered Keyword Cannibalization Detection Workflow Overview This is an advanced n8n automation workflow designed to detect and analyze keyword cannibalization issues across multiple client websites using Google Search Console data and artificial intelligence. The system provides real-time monitoring and comprehensive reporting to help SEO professionals identify and resolve internal competition between pages ranking for the same keywords. Core Components 1. Automated Monitoring System Real-time trigger:** Monitors Google Sheets for keyword changes every minute Multi-client support:** Handles up to 4 different client websites simultaneously Intelligent routing:** Automatically directs each client's data through dedicated processing paths 2. Data Collection & Processing GSC Integration:** Fetches 30 days of search performance data from Google Search Console API Comprehensive metrics:** Collects keyword rankings, page URLs, positions, clicks, impressions, and CTR Data transformation:** Groups raw API responses by keywords for structured analysis Cross-referencing:** Matches target keywords from Google Sheets with actual GSC performance data 3. AI Analysis Engine GPT-4o powered:** Uses advanced AI to analyze keyword competition patterns Risk categorization:** Automatically classifies cannibalization risk as: High Risk: 5+ pages competing for the same keyword Moderate Risk: 3+ pages ranking in top 10 positions Low Risk: 2 pages with one clearly dominating No Risk: Single page ranking for the keyword Intelligent reasoning:** Provides detailed explanations for each risk assessment 4. Comprehensive Reporting Automated output:** Saves analysis results back to Google Sheets Detailed insights:** Includes risk levels, reasoning, observations, and actionable remediation steps Performance tracking:** Complete keyword performance metrics for client reporting Status tracking:** Identifies which keywords are ranking vs. missing from search results. An n8n automation workflow template by Incrementors.

By Anna Bui

Automatically monitor LinkedIn posts from your community members and create AI-powered content digests for efficient social media curation. This template is perfect for community managers, content creators, and social media teams who need to track LinkedIn activity from their network without spending hours manually checking profiles. It fetches recent posts, extracts key information, and creates digestible summaries using AI. Good to know API costs apply** - LinkedIn API calls ($0.01-0.05 per profile check) and OpenAI processing ($0.001-0.01 per post) Rate limiting included** - Built-in random delays prevent API throttling issues Flexible scheduling** - Easy to switch from daily schedule to webhook triggers for real-time processing Requires API setup** - Need RapidAPI access for LinkedIn data and OpenAI for content processing How it works Daily profile scanning** - Automatically checks each LinkedIn profile in your Airtable for posts from yesterday Smart data extraction** - Pulls post content, engagement metrics, author information, and timestamps AI-powered summarization** - Creates 30-character previews of posts for quick content scanning Duplicate prevention** - Checks existing records to avoid storing the same post multiple times Structured storage** - Saves all processed data to Airtable with clean formatting and metadata Batch processing** - Handles multiple profiles efficiently with proper error handling and delays How to use Set up Airtable base** - Create tables for LinkedIn profiles and processed posts using the provided structure Configure API credentials** - Add your RapidAPI LinkedIn access and OpenAI API key to n8n credentials Import LinkedIn profiles** - Add community members' LinkedIn URLs and URNs to your profiles table Test the workflow** - Run manually with a few profiles to ensure everything works correctly Activate schedule** - Enable daily automation or switch to webhook triggers for real-time processing Requirements Airtable account** - For storing profile lists and managing processed posts with proper field structure RapidAPI Professional Network Data API** - Access to LinkedIn post data (requires subscription) OpenAI API account** - For intelligent content summarization and preview generation LinkedIn profile URNs** - Properly formatted LinkedIn profile identifiers for API calls Customising this workflow Change monitoring frequency** - Switch from daily to hourly checks or use webhook triggers for real-time updates Expand data extraction** - Add company information, hashtag analysis, or engagement trending Integrate notification systems** - Add Slack, email, or Discord alerts for high-engagement posts Connect content tools** - Link to Buffer, Hootsuite, or other social media management platforms for direct publishing Add filtering logic** - Set up conditions to only process posts with minimum engagement thresholds Scale with multiple communities** - Duplicate workflow for different LinkedIn communities or industry segments. An n8n automation workflow template by Anna Bui.

By Avkash Kakdiya

How it works This workflow automatically syncs new Productboard features into Linear as issues and notifies the team via Telegram. It starts on a schedule, fetches Productboard features through API requests, and transforms the raw data into clean, structured fields. Newly created features are filtered, then inserted into Linear, and a success message is sent to Telegram for confirmation. Step-by-step 1. Trigger and fetch data Schedule Trigger** – Starts the workflow at predefined intervals. HTTP Request to Productboard** – Pulls the latest features from the Productboard API. 2. Transform and clean data Code (Transform Features)** – Strips HTML, formats dates, and extracts clean fields like name, description, status, owner, and link. 3. Filter for new items If (Filter New Features)** – Compares createdAt with today’s date, allowing only new features to proceed. 4. Create issues in Linear Create Linear Issue** – Opens a new Linear issue using the feature’s name and description. 5. Notify via Telegram Success Notification (Telegram)** – Sends a confirmation message once the sync is successful. Why use this? Automates the sync of Productboard features into Linear without manual copying. Ensures only new features are captured, preventing duplicates. Keeps your team updated instantly through Telegram notifications. Saves time by standardizing data and formatting before inserting into Linear. Creates a smooth handoff from product planning to engineering execution. An n8n automation workflow template by Avkash Kakdiya.

By Avkash Kakdiya

How it works This workflow consolidates data from five different systems — Google Sheets, PostgreSQL, MongoDB, Microsoft SQL Server, and Google Analytics — into a single master Google Sheet. It runs on a scheduled trigger three times a week. Each dataset is tagged with a unique source identifier before merging, ensuring data traceability. Finally, the merged dataset is cleaned, standardized, and written into the output Google Sheet for reporting and analysis. Step-by-step 1. Trigger the workflow Schedule Trigger** – Runs the workflow at set weekly intervals. 2. Collect data from sources Google Sheets Source** – Retrieves records from a specific sheet. PostgreSQL Source** – Extracts customer data from the database. MongoDB Source** – Pulls documents from the defined collection. Microsoft SQL Server** – Executes a SQL query and returns results. Google Analytics** – Captures user activity and engagement metrics. 3. Tag each dataset Add Sheets Source ID** – Marks data from Google Sheets. Add PostgreSQL Source ID** – Marks data from PostgreSQL. Add MongoDB Source ID** – Marks data from MongoDB. Add SQL Server Source ID** – Marks data from SQL Server. Add Analytics Source ID** – Marks data from Google Analytics. 4. Merge and process Merge** – Combines all tagged datasets into a single structure. Process Merged Data** – Cleans, aligns schemas, and standardizes key fields. 5. Store consolidated output Final Google Sheet** – Appends or updates the master sheet with the processed data. Why use this? Centralizes multiple data sources into a single, consistent dataset. Ensures data traceability by tagging each source. Reduces manual effort in data cleaning and consolidation. Provides a reliable reporting hub for business analysis. Enables scheduled, automated updates for up-to-date visibility. An n8n automation workflow template by Avkash Kakdiya.

By IranServer.com

Automated Blog Content Generation from Google Trends to WordPress This n8n workflow automatically generates SEO-friendly blog content based on trending topics from Google Trends and publishes it to WordPress. Perfect for content creators, bloggers, and digital marketers who want to stay on top of trending topics with minimal manual effort. Who's it for Content creators** who need fresh, trending topic ideas Bloggers** looking to automate their content pipeline Digital marketers** wanting to capitalize on trending searches WordPress site owners** seeking automated content generation SEO professionals** who want to target trending keywords How it works The workflow operates on a scheduled basis (daily at 8:45 PM by default) and follows this process: Trend Discovery: Fetches the latest trending searches from Google Trends for a specific country (Iran by default) Content Research: Performs Google searches on the top 3 trending topics to gather detailed information AI Content Generation: Uses OpenAI's GPT-4o model to create SEO-friendly blog posts based on the trending topics and search results Structured Output: Ensures the generated content has proper title and content structure Auto-Publishing: Automatically creates draft posts in WordPress The AI is specifically prompted to create engaging, SEO-optimized content without revealing the automated sources, ensuring natural-sounding blog posts. How to set up Install required community node: n8n-nodes-serpapi for Google Trends and Search functionality Configure credentials: SerpApi: Sign up at serpapi.com and add your API key OpenAI: Add your OpenAI API key for GPT-4o access WordPress: Configure your WordPress site credentials Customize the country code: Change the "Country" field in the "Edit Fields" node (currently set to "IR" for Iran) Adjust the schedule: Modify the "Schedule Trigger" to run at your preferred time Test the workflow: Run it manually first to ensure all connections work properly Requirements SerpApi account** (for Google Trends and Search data) OpenAI API access** (for content generation using GPT-4o) WordPress site** with API access enabled How to customize the workflow Change target country**: Modify the country code in the "Edit Fields" node to target different regions Adjust content quantity**: Change the limit in the "Limit" node to process more or fewer trending topics Modify AI prompt**: Edit the prompt in the "Basic LLM Chain" node to change writing style or focus Schedule frequency**: Adjust the "Schedule Trigger" for different posting frequencies Content status**: Change from "draft" to "publish" in the WordPress node for immediate publishing Add content filtering**: Insert additional nodes to filter topics by category or keywords. An n8n automation workflow template by IranServer.com.

By panyanyany

Overview This workflow uses the Defapi API with Google's Gemini AI to transform digital photos into authentic Polaroid-style vintage photographs. Upload your photos, provide a creative prompt, and get AI-generated vintage effects with that distinctive instant camera charm. Input: Digital photos + creative prompt + API key Output: Polaroid-style vintage photographs The system provides a simple form interface where users submit their images, prompt, and API key. It automatically processes requests through Defapi API, monitors generation status, and delivers the final vintage photo output. Ideal for photographers, content creators, and social media enthusiasts looking to add vintage charm to their digital photos. Prerequisites A Defapi account and API key: Sign up at Defapi.org An active n8n instance (cloud or self-hosted) with HTTP Request and form submission capabilities Digital photos for transformation (well-lit photos work best) Basic knowledge of AI prompts for vintage photo generation Example prompt: Take a picture with a Polaroid camera. The photo should exhibit rich saturation and vintage color cast, with soft tones, low contrast, and vignetting. The texture features distinct film grain. Do not change the faces. Replace the background behind the two people with a white curtain. Make them close to each other with clear faces and normal skin color. Setup Instructions Obtain API Key: Register at Defapi.org and generate your API key. Store it securely. Configure the Form: Set up the "Upload 2 Images" form trigger with: Image 01 & Image 02 (file uploads), API Key (text field), and Prompt (text field). Test the Workflow: Click "Execute Workflow" in n8n Access the form URL, upload two photos, enter your prompt, and provide your API key The workflow processes images, sends the request to Defapi API, waits 10 seconds, then polls until generation is complete Handle Outputs: The final node displays the generated image URL for download or sharing. Workflow Structure The workflow consists of the following nodes: Upload 2 Images (Form Trigger) - Collects user input: two image files, API key, and prompt Convert to JSON (Code Node) - Converts uploaded images to base64 and formats data Send Image Generation Request to Defapi.org API (HTTP Request) - Submits generation request Wait for Image Processing Completion (Wait Node) - Waits 10 seconds before checking status Obtain the generated status (HTTP Request) - Polls API for completion status Check if Image Generation is Complete (IF Node) - Checks if status equals 'success' Format and Display Image Results (Set Node) - Formats final image URL output Technical Details API Endpoint**: https://api.defapi.org/api/image/gen (POST request) Model Used: google/gemini (Gemini AI**) Status Check Endpoint**: https://api.defapi.org/api/task/query (GET request) Wait Time**: 10 seconds between status checks Image Processing**: Uploaded images are converted to base64 format for API submission Authentication**: Bearer token authentication using the provided API key Specialized For**: Polaroid-style vintage photography and instant camera effects Customization Tips Enhance Prompts**: Include specifics like vintage color cast, film grain texture, vignetting, lighting conditions, and atmosphere to improve AI photo quality. Specify desired saturation levels and contrast adjustments. Photo Quality**: Use well-lit, clearly exposed photos for best results. The AI can simulate flash effects and vintage lighting, but quality input produces better output. Note that generated photos may sometimes be unclear or have incorrect skin tones - try multiple generations to achieve optimal results. An n8n automation workflow template by panyanyany.

By Václav Čikl

Description: This sophisticated workflow automates personalized email campaigns for musicians and band managers. The system processes contact databases, analyzes previous Gmail conversation history, and uses AI to generate contextually appropriate emails tailored to different contact categories (venues, festivals, media, playlists). Key Features: Multi-category support**: Bookers, festivals, media, playlist curators Conversation context analysis**: Maintains relationship history from Gmail AI-powered personalization**: Custom prompts for each contact type Multi-language support**: Localized content and prompts Gmail integration**: Automatic draft creation with signatures Bulk processing**: Handle hundreds of contacts efficiently Use Cases: Album/single promotion campaigns Tour booking automation Festival submission management Playlist pitching campaigns Media outreach automation Venue relationship management Perfect For: Independent musicians and bands Music managers and booking agents Record labels with multiple artists PR agencies in music industry Festival organizers (for artist outreach) Required Setup: 1. Credentials & APIs: Gmail OAuth2** (read messages + create drafts permissions) Google Sheets API** (for AutomatizationHelper configuration) OpenAI API** or compatible LLM (for content generation) 2. Required Files: Contact Database** (CSV): Your venue/media/festival contacts AutomatizationHelper** (Google Sheets): Campaign configuration, prompts, links 3. Example Data: 📁 Download Example Files The folder contains: Sample contact database (CSV) AutomatizationHelper template (CSV + Google Sheets) Detailed setup instructions (README) Data Structure: Contact Database Fields: venue_name - Organization name category - booker/festival/media/playlisting email_1 - Primary email (required) email_2 - Secondary email (optional, for CC) active - active/inactive (for filtering) language - EN/DE/etc. (for localization) AutomatizationHelper Fields: LANGUAGE - Language code CATEGORY - Contact type LATEST_SINGLE - Spotify/Apple Music link LATEST_VIDEO - YouTube/Vimeo link EPK - Electronic Press Kit URL SIGNATURE - HTML email signature PROMPT - AI prompt for this category SUBJECT - Email subject template Setup Instructions: Step 1: Prepare Your Data Download example files from the Google Drive folder Replace sample data with your real contacts and band information Customize AI prompts for your communication style Update signature with your contact details Step 2: Configure APIs Set up Gmail OAuth2 credentials in n8n Configure Google Sheets API access Add OpenAI API key for content generation Step 3: Import & Configure Workflow Import the workflow JSON Connect your credentials to respective nodes Update Google Sheets URL in AutomatizationHelper node Test with a small contact sample first Step 4: Customize & Run Adjust AI prompts in AutomatizationHelper for your style Update contact categories as needed Run workflow - drafts will be created in Gmail for review Tips: Start small**: Test with 5-10 contacts first Review drafts**: Always review AI-generated content before sending Update regularly**: Keep your AutomatizationHelper current with latest releases Monitor responses**: Track which prompts work best for different categories Language mixing**: You can have contacts in multiple languages Important Notes: Emails are created as Gmail drafts - manual review recommended Respects Gmail API rate limits automatically Conversation history analysis works best with existing email threads HTML signatures are automatically added (Gmail API limitation workaround) Handles multiple languages simultaneously Maintains conversation context across campaigns Generates unique content for each contact Template Author: Questions or need help with setup? Email: xciklv@gmail.com LinkedIn: https://www.linkedin.com/in/vaclavcikl/. An n8n automation workflow template by Václav Čikl.

By Blukaze Automations

This n8n template creates an intelligent AI-powered travel agent that can assist with travel planning and send email confirmations. The agent can extract user requests, plan travel itineraries by fetching real-time data on flights, accommodations, and activities, and then communicate this information by sending a customized email. Use Cases Quickly plan a trip by providing your destination and dates. Get real-time flight and accommodation details for a planned vacation. Receive a summary of your travel plans directly in your inbox. A personal travel planner available on-the-go. Good to Know This template uses Google Gemini for AI reasoning. The Planner Agent can break down complex travel requests and make multiple API calls to gather all the necessary information. The Email Agent crafts a professional and personalized email to send to the user. How it Works Incoming Message Trigger: The workflow begins when a new message is received from a user. Extract User Request: The user's message is sent to a Gemini Chat Model which identifies the user's intent and extracts key details like destination, dates, and interests. Planner Agent: The extracted information is passed to the Planner Agent. This agent, powered by Gemini, determines what information is needed and then calls a series of sub-agents to gather: Activities: Fetches information about local attractions and things to do. Flight Booking: Retrieves flight details and pricing. Accommodation Details: Looks for hotels, rentals, and other lodging options. Accommodations: Gathers general information about accommodations. Email Agent: Once the Planner Agent has collected all the necessary information, it’s handed over to the Email Agent. This agent uses a second Gemini Chat Model to format a clear and professional email containing the full travel itinerary. Send Message: The final email is sent to the user, providing a comprehensive travel plan. How to Use Clone this workflow into your n8n instance. Connect your accounts as required. You will need credentials for your email service and any APIs you want to use for fetching travel data (e.g., flight booking, accommodation, and activities). Modify the nodes with your specific credentials and API endpoints. Run the workflow and start receiving automated travel plans. Requirements Google Gemini account for AI reasoning. Email integration (e.g., Gmail, Outlook). Serp API keys for travel-related services (optional, depending on your setup). Customizing This Workflow Add more integrations (e.g., a hotel booking service like Booking.com, a restaurant reservation system) for extended functionality. Modify the AI prompts in the agent nodes to fine-tune the personality or focus of the travel agent. Connect the final output to a different messaging service like Telegram or Slack instead of email. An n8n automation workflow template by Blukaze Automations.

By Jitesh Dugar

1. Who's It For Ad agencies needing automated lead capture. Sales teams fighting fraud and scoring leads. B2B SaaS companies nurturing prospects. Marketing pros boosting sales pipelines. 2. How It Works Captures leads via Webhook from forms. Validates emails with Verifi Email node. Checks IP for fraud using IP Lookup. Scores leads (0-100) with Function node. Logs data in Google Sheets. Alerts sales via Slack for high scores. Sends welcome email via Gmail. Tracks email opens for engagement. Follows up after 24 hours if unopened. Updates engagement scores. Generates weekly report (leads, scores, avg.). Emails report to sales head. Offers: fraud-proofing, AI scoring, nurturing, reporting. 3. How to Set Up 1.* Link form to *Webhook** (POST to https://[your-n8n-url]/webhook/lead-capture). 2.* Install *Verifi Email** node (npm install n8n-nodes-verifiemail) on self-hosted n8n. 3.* Add credentials: *Verifi Email, **Slack, Gmail, Google Sheets. 4.* Set up *Set User Config** (e.g., score, channel, email). 5.* Adjust *Weekly Report** cron (default: Mondays 00:00 IST). 6.** Test with sample data (e.g., {"email": "test@example.com", "ip": "8.8.8.8"}). Requirements Self-hosted n8n (for Verifi Email). Credentials: Verifi Email key, Slack token, Gmail, Google Sheets. Node.js* and *npm** for installation. Form to send data to Webhook. Core Features Fraud Detection**: Email and IP validation. Lead Scoring**: AI-driven quality assessment. Automated Nurturing**: Personalized emails. Real-Time Alerts**: Slack notifications. Weekly Reporting**: Performance insights. Use Cases & Applications Sales Teams**: Streamline lead follow-ups. Marketing**: Enhance campaign tracking. B2B SaaS**: Automate prospect nurturing. Agencies**: Deliver client-ready reports. Key Benefits Efficiency**: Automates manual tasks. Accuracy**: Reduces fraud with validation. Scalability**: Handles multiple leads. Insight**: Weekly performance data. Customization Options Adjust scoring in Function node. Edit email templates in Gmail. Add attachments via File node. Change cron schedule. Integrate CRM with HTTP Request. Important Disclaimers For educational use only. Validate with your risk tolerance. Seek professional advice before use. Account for market volatility. An n8n automation workflow template by Jitesh Dugar.

By Jose Cuartas

Sync Gmail emails to PostgreSQL with S3 attachment storage Automated Gmail Email Processing System Who's it for Businesses and individuals who need to: Archive email communications in a searchable database Backup email attachments to cloud storage Analyze email patterns and communication data Comply with data retention policies Integrate emails with other business systems What it does This workflow automatically captures, processes, and stores Gmail emails in a PostgreSQL database while uploading file attachments to S3/MinIO storage. It handles both individual emails (via Gmail Trigger) and bulk processing (via Schedule Trigger). Key features: Dual processing: real-time individual emails + scheduled bulk retrieval Complete email metadata extraction (sender, recipients, labels, timestamps) HTML to plain text conversion for searchable content Binary attachment processing with metadata extraction Organized S3/MinIO file storage structure UPSERT database operations to prevent duplicates How it works Email Capture: Gmail Trigger detects new emails, Schedule Trigger gets bulk emails from last hour Parallel Processing: Emails with attachments go through binary processing, others go directly to transformation Attachment Handling: Extract metadata, upload to S3/MinIO, create database references Data Transformation: Convert Gmail API format to PostgreSQL structure Storage: UPSERT emails to database with linked attachment information Requirements Credentials needed: Gmail OAuth2 (gmail.readonly scope) PostgreSQL database connection S3/MinIO storage credentials Database setup: Run the provided SQL schema to create the messages table with JSONB fields for flexible data storage. How to set up Gmail OAuth2: Enable Gmail API in Google Cloud Console, create OAuth2 credentials PostgreSQL: Create database and run the SQL schema provided in setup sticky note S3/MinIO: Create bucket "gmail-attachments" with proper upload permissions Configure: Update authenticatedUserEmail in transform scripts to your email Test: Start with single email before enabling bulk processing How to customize Email filters**: Modify Gmail queries (in:sent, in:inbox) to target specific emails Storage structure**: Change S3 file path format in Upload node Processing schedule**: Adjust trigger frequencies based on email volume Database fields**: Extend PostgreSQL schema for additional metadata Attachment types**: Add file type filtering in binary processing logic Note: This workflow processes emails from the last hour to avoid overwhelming the system. Adjust timeframes based on your email volume and processing needs. An n8n automation workflow template by Jose Cuartas.

By Jaruphat J.

⚠️ Note: All sensitive credentials should be set via n8n Credentials or environment variables. Do not hardcode API keys in nodes. Who’s it for Marketers, creators, and automation builders who want to generate UGC-style ad images automatically from a Google Sheet. Ideal for e‑commerce SKUs, agencies, or teams that need many variations quickly. What it does (Overview) This template turns a spreadsheet row into ad images ready for campaigns. Zone 1 — Create Ad Image**: Reads product rows, downloads image, analyzes it, generates prompts, appends results back into Google Sheet. Zone 2 — Create Image (Fal nano‑banana)**: Generates ad image variations, polls Fal.ai API until done, uploads to Drive, and updates sheet with output URLs. Requirements Fal.ai API key** (env: FAL\_KEY) Google Sheets / Google Drive** OAuth2 credentials OpenAI (Vision/Chat)** for image analysis A Google Sheet with columns for product and output Google Drive files set to Anyone with link → Viewer so APIs can fetch them How to set up Credentials: Add Google Sheets + Google Drive (OAuth2), Fal.ai (Header Auth with Authorization: Key {{\$env.FAL\_KEY}}), and OpenAI. Google Sheet: Create sheets with the following headers. Sheet: product product_id | product_name | product_image_url | product_description | campaign | brand_notes | constraints | num_variations | aspect_ratio | model_target | status Sheet: ad_image scene_ref | product_name | prompt | status | output_url Import the workflow: Use the provided JSON. Confirm node credentials resolve. Run: Start with Zone 0 to verify prompt-only flow, then test Zone 1 for image generation. Zone 1 — Create Ad Image (Prompt-only) Reads product row, normalizes Drive link, analyzes image, generates structured ad prompts, appends to ad_image sheet. Zone 2 — Create Image (Fal nano‑banana) Reads product row, converts Drive link, generates image(s) with Fal nano‑banana, polls until complete, uploads to Drive, updates sheet. Node settings (high‑level) Drive Link Parser (Set) {{ (() => { const u = $json.product || ''; const q = u.match(/[?&]id=([\-\w]{25,})/); const d = u.match(/\/d\/([\-\w]{25,})/); const any = u.match(/[\-\w]{25,}/); const id = q?.[1] || d?.[1] || (any ? any[0] : ''); return id ? 'https://drive.google.com/uc?export=view&id=' + id : ''; })() }} How to customize the workflow Adjust AI prompts to change ad style (luxury, cozy, techy). Change aspect ratio for TikTok/IG/Shorts (9:16, 1:1, 16:9). Extend Sheet schema for campaign labels, audiences, hashtags. Add distribution (Slack/LINE/Telegram) after Drive upload. Troubleshooting JSON parameter needs to be valid JSON** → Ensure expressions return objects, not strings. 403 on images** → Make Drive files public (Viewer) and convert links. Job never completes* → Check status_url, retry with -fast models or off‑peak times. Template metadata Uses:** Google Sheets, Google Drive, HTTP Request, Wait/If/Switch, Code, OpenAI Vision/Chat, Fal.ai models (nano‑banana) Visuals Workflow Diagram Example Product Image Product Image - nano Banana. An n8n automation workflow template by Jaruphat J..

By Mariela Slavenova

This template enriches a lead list by analyzing each contact’s company website and auto-generating a single personalized cold-email opener. Drop a spreadsheet into a Google Drive folder → the workflow parses rows, fetches website content via Jina AI, uses OpenAI to check if the site contains valid business info, then calls Anthropic to craft a one-liner. It writes both the website summary and personalized opener back to Google Sheets, and finally sends you a Telegram confirmation with the file link. What it does Turns a CSV/Google Sheet of leads into tailored cold-email openers. For each lead, the workflow fetches the company website, writes a 300-word business summary, then crafts a one-sentence, emotionally engaging opening line. Results are written back to the same Sheet, and you get a Telegram ping when processing finishes. How it works (high-level) Trigger: Watches a Google Drive folder. When a new Sheet is added, the flow starts. Parse: Reads rows (expects columns like First Name, Last Name, Email, domain). Enrich: An AI Agent calls Jina “r.jina.ai/{url}” to fetch page markdown, then produces a structured website summary. Validate: An OpenAI step checks if the fetched content is a real business page (hasWebsite: true/false). Personalize: • If true → Anthropic crafts a bespoke opener using the summary. • If false → Fallback prompt creates a strong opener using domain + universal lead-gen pains. Update: Writes websiteSummary and personalization back to the Sheet (matching on domain). Notify: Sends a Telegram message with the file name + link when done. What you need • Google Drive (folder to watch) • Google Sheets (the uploaded Sheet to enrich) • Jina HTTP header auth (for the markdown fetch tool) • OpenAI (JSON check for website validity) • Anthropic (Claude Sonnet 4 for copy quality) • Telegram Bot (to receive completion alerts) Inputs & expected schema • A Google Sheet with at least: First Name, Last Name, Email, domain • Optional columns are preserved; rows are processed in batches. Outputs • New/updated columns per row: • websiteSummary — concise, structured business overview • personalization — a single, high-impact opening sentence • Telegram confirmation with file name and link. Customization tips • Tweak the system prompts for tone or length. • Add scoring (e.g., ICP fit) before personalization. • Expand validation (e.g., handle multi-page sites or language detection). • Swap/parallel LLMs to balance quality, cost, and speed. Nodes & key logic • Google Drive Trigger → Google Drive (Download) → Spreadsheet File (parse) → Split in Batches • LangChain Agent with: HTTP Tool (Jina) + Think • OpenAI (JSON validator) → If (website present?) • Anthropic Chat (with + without website branches) • Edit Fields (Set) → Google Sheets (Update) → Telegram Great for Sales teams, SDRs, and founders who want fast, high-quality personalization at scale without manual research. Need help customizing? Contact me for consulting and support: LinkedIn. An n8n automation workflow template by Mariela Slavenova.

By Amit Mehta

Automated Social Media Content Publishing Factory + System Prompt Composition This workflow is a powerful automation for creating and publishing social media content. It uses AI to generate content and images based on external prompts and schemas, and routes the final posts to various social media platforms. How it Works This workflow operates as a "Content Publishing Factory". It generates platform-optimized content for platforms like LinkedIn, Instagram, Facebook, X (Twitter), Threads, and YouTube Shorts. A key feature is its dynamic system prompt and output schema composition, which pulls content from external Google Docs to ensure consistency. The workflow can also create images to match the content and send the final draft for approval via email before publishing. Use Cases Centralized Content Management**: Store and manage all system prompts and schemas in Google Docs for easy team collaboration and version control. Brand Consistency**: Ensure a consistent brand voice across all social media platforms by centralizing brand guidelines and content rules. Automated Publishing**: Automate content creation, image generation, and publishing, reducing manual effort and design bottlenecks. Fact-checking and Contextual Relevance**: Incorporate real-time research and fact-checking into content to ensure accuracy and relevance. Setup Instructions Google Docs: Create two Google Docs: one for the social media schema and one for the system prompt, and update the respective node IDs in the workflow. API Credentials: Provide credentials for the following services: OpenAI: For the AI agents and content creation. SerpAPI: For the web search tool to perform research. Gmail: For sending content for approval and notifications. Google Drive: For archiving images and final posts. Social Media Platforms: You'll need credentials for the platforms you wish to publish to (X, Instagram, Facebook, LinkedIn, etc.). Image Hosting: The workflow uses imgbb.com to host generated images, requiring an API key. Workflow Logic Routing Agent: The Social Media Router Agent receives a user prompt and uses a toolWorkflow node to route the request to the appropriate content generation workflow. Prompt & Schema Composition: The workflow fetches the system prompt and platform-specific schemas from Google Docs, parses them, and composes a dynamic prompt for the AI agent. Content Creation: The Social Media Content Creator agent uses the composed prompt and a web search tool to generate platform-optimized content and an image suggestion. Image Generation & Archiving: The workflow generates an image from the AI suggestion using an external service and archives both the image and the final post content in Google Drive. Approval Process: The draft content is sent to a Gmail address for approval. Publishing: If the content is approved, the Social Media Publishing Router node directs the content to the correct publishing node for the specified platform (e.g., X Post, Instagram Image, Facebook Post, etc.). Node Descriptions | Node Name | Description | |-----------|-------------| | When chat message received | A trigger node that initiates the workflow based on a chat message. | | Social Media System Prompt | A Google Docs node that retrieves the main system prompt for the AI agent. | | Social Media Schema | A Google Docs node that retrieves the JSON schema for each social media platform's output. | | Social Media Content Creator | An AI agent that generates content based on user prompts, system prompts, and schemas, using a web search tool for research. | | pollinations.ai1 | An HTTP Request node that generates an image from a text prompt using an external service. | | Gmail User for Approval | Sends a draft of the social media post for approval and pauses the workflow until a decision is made. | | Social Media Publishing Router | A Switch node that routes the workflow to the correct publishing node based on the user's selected platform. | | X Post, Instagram Post, Facebook Post, LinkedIn Post | These nodes publish the final, approved content to their respective social media platforms. | Customization Tips You can replace the pollinations.ai image generation service with any other online service that produces an image file. Replace the gpt-4o and gpt-4o-mini models with other LLMs and web search tools to suit your needs. Adjust the content and parameters for each social media platform to better fit your brand and audience. Suggested Sticky Notes for Workflow Start Here**: "Update all Social Media Platform Credentials as required. Adjust parameters and content for each platform to suit your needs". External System Prompt and Schema**: "Create Google Doc for the Social Media Schema and copy the provided schema. Update the Google Doc ID in the Social Media Schema node.". Create Post Image**: "Replace pollinations.ai with any online image generation service that produces an image file you can download". Social Media Content Creator**: "Replace Chat model with other LLMs and test out the results. Add more tools or try other web search tools to suit your use case." Testing Tips Start the workflow with a manual trigger and verify that the social media content and a related image are generated and sent for approval via Gmail. Approve the content in the Gmail email to test the publishing side of the workflow. Check the specified social media accounts to confirm that the post was published correctly. Suggested Tags & Categories SocialMedia Automation AI ContentCreation Publishing GoogleDocs OpenAI. An n8n automation workflow template by Amit Mehta.

By Amit Mehta

N8N Workflow: Printify Automation - Update Title and Description - AlexK1919 This workflow automates the process of getting products from Printify, generating new titles and descriptions using OpenAI, and updating those products. How it Works This workflow automatically retrieves a list of products from a Printify store, processes them to generate new titles and descriptions based on brand guidelines and custom instructions, and then updates the products on Printify with the new information. It also interacts with Google Sheets to track the status of the products being processed. The workflow can be triggered both manually or by an update in a Google Sheet. Use Cases E-commerce Automation**: Automating content updates for a Printify store. Marketing & SEO**: Generating SEO-friendly or seasonal content for products using AI. Product Management**: Batch-updating product titles and descriptions without manual effort. Setup Instructions Printify API Credentials: Set up httpHeaderAuth credentials for Printify to allow the workflow to get and update products. OpenAI API Credentials: Provide an API key for OpenAI in the openAiApi credentials. Google Sheets Credentials: The workflow requires two separate Google Sheets credentials: one for the trigger (googleSheetsTriggerOAuth2Api) and another for appending/updating data (googleSheetsOAuth2Api). Google Sheets Setup: You need a Google Sheet to store product information and track the status of the updates. The workflow is linked to a specific spreadsheet. Brand Guidelines: The Brand Guidelines + Custom Instructions node must be updated with your specific brand details and any custom instructions for the AI. Workflow Logic Trigger: The workflow can be triggered manually or by an update in a Google Sheet when the upload column is changed to "yes". Get Product Info: It fetches the shop ID and then a list of all products from Printify. Process Products: The product data is split, and the workflow loops through each product. AI Content Generation: For each product, the Generate Title and Desc node uses OpenAI to create a new title and description based on the original content, brand guidelines, and custom instructions. Google Sheets Update: The workflow appends the product information and a "Product Processing" status to a Google Sheet. It then updates the row with the newly generated title and description, and changes the status to "Option added". Printify Update: The Printify - Update Product node sends a PUT request to the Printify API to apply the new title and description to the product. Node Descriptions | Node Name | Description | |-----------|-------------| | When clicking 'Test workflow' | A manual trigger for testing the workflow. | | Google Sheets Trigger | An automated trigger that starts the workflow when the upload column in the Google Sheet is updated. | | Printify - Get Shops | Fetches the list of shops associated with the Printify account. | | Printify - Get Products | Retrieves all products from the specified Printify shop. | | Brand Guidelines + Custom Instructions | A Set node to store brand guidelines and custom instructions for the AI. | | Generate Title and Desc | An OpenAI node that generates a new title and description based on the provided inputs. | | GS - Add Product Option | Appends a new row to a Google Sheet to track the processing status of a product. | | Update Product Option | Updates an existing row in the Google Sheet with the new product information and status. | | Printify - Update Product | A PUT request to the Printify API to update a product with new information. | Customization Tips You can swap out the Printify API calls with similar services like Printful or Vistaprint. Modify the Brand Guidelines + Custom Instructions node to change the brand name, tone, or specific instructions for the AI. Change the number of options the workflow should generate by modifying the Number of Options node. You can change the OpenAI model used in the Generate Title and Desc node, for example, from gpt-4o-mini to another model. Suggested Sticky Notes for Workflow "Update your Brand Guidelines before running this workflow. You can also add custom instructions for the AI node." "You can swap out the API calls to similar services like Printful, Vistaprint, etc." "Set the Number of Options you'd like for the Title and Description" Required Files 1V1gcK6vyczRqdZC_Printify_Automation_-Update_Title_and_Description-_AlexK1919.json: The main n8n workflow export for this automation. The Google Sheets template for this workflow. Testing Tips Run the workflow with the manual trigger to see the flow from start to finish. Change the upload column in the Google Sheet to "yes" to test the automated trigger. Verify that the new titles and descriptions are correctly updated on Printify. Suggested Tags & Categories Printify OpenAI. An n8n automation workflow template by Amit Mehta.

By dongou

Fetch user-specific research papers from arXiv on a daily schedule, process and structure the data, and create or update entries in a Notion database, with support for data delivery Paper Topic**: single query keyword Update Frequency**: Daily updates, with fewer than 20 entries expected per day Tools**: Platform: n8n, for end-to-end workflow configuration AI Model: Gemini-2.5-Flash, for daily paper summarization and data processing Database: Notion, with two tables — Daily Paper Summary and Paper Details Message: Feishu (IM bot notifications), Gmail (email notifications) 1. Data Retrieval arXiv API The arXiv provides a public API that allows users to query research papers by topic or by predefined categories. arXiv API User Manual Key Notes: Response Format: The API returns data as a typical Atom Response. Timezone & Update Frequency: The arXiv submission process operates on a 24-hour cycle. Newly submitted articles become available in the API only at midnight after they have been processed. Feeds are updated daily at midnight Eastern Standard Time (EST). Therefore, a single request per day is sufficient. Request Limits: The maximum number of results per call (max_results) is 30,000, Results must be retrieved in slices of at most 2,000 at a time, using the max_results and start query parameters. Time Format: The expected format is [YYYYMMDDTTTT+TO+YYYYMMDDTTTT], TTTT is provided in 24-hour time to the minute, in GMT. Scheduled Task Execution Frequency**: Daily Execution Time**: 6:00 AM Time Parameter Handling (JS)**: According to arXiv’s update rules, the scheduled task should query the previous day’s (T-1) submittedDate data. 2. Data Extraction Data Cleaning Rules (Convert to Standard JSON) Remove Header Keep only the 【entry】【/entry】 blocks representing paper items. Single Item Each 【entry】【/entry】 represents a single item. Field Processing Rules 【id】【/id】 ➡️ id Extract content. Example: 【id】http://arxiv.org/abs/2409.06062v1【/id】 → http://arxiv.org/abs/2409.06062v1 【updated】【/updated】 ➡️ updated Convert timestamp to yyyy-mm-dd hh:mm:ss 【published】【/published】 ➡️ published Convert timestamp to yyyy-mm-dd hh:mm:ss 【title】【/title】 ➡️ title Extract text content 【summary】【/summary】 ➡️ summary Keep text, remove line breaks 【author】【/author】 ➡️ author Combine all authors into an array Example: [ "Ernest Pusateri", "Anmol Walia" ] (for Notion multi-select field) 【arxiv:comment】【/arxiv:comment】 ➡️ Ignore / discard 【link type="text/html"】 ➡️ html_url Extract URL 【link type="application/pdf"】 ➡️ pdf_url Extract URL 【arxiv:primary_category term="cs.CL"】 ➡️ primary_category Extract term value 【category】 ➡️ category Merge all 【category】 values into an array Example: [ "eess.AS", "cs.SD" ] (for Notion multi-select field) Add Empty Fields github huggingface 3. Data Processing Analyze and summarize paper data using AI, then standardize output as JSON. Single Paper Basic Information Analysis and Enhancement Daily Paper Summary and Multilingual Translation 4. Data Storage: Notion Database Create a corresponding database in Notion with the same predefined field names. In Notion, create an integration under Integrations and grant access to the database. Obtain the corresponding Secret Key. Use the Notion "Create a database page" node to configure the field mapping and store the data. Notes "Create a database page"** only adds new entries; data will not be updated. The updated and published timestamps of arXiv papers are in UTC. Notion single-select and multi-select fields only accept arrays. They do not automatically parse comma-separated strings. You need to format them as proper arrays. Notion does not accept null values, which causes a 400 error. 5. Data Delivery Set up two channels for message delivery: EMAIL and IM, and define the message format and content. Email: Gmail GMAIL OAuth 2.0 – Official Documentation Configure your OAuth consent screen Steps: Enable Gmail API Create OAuth consent screen Create OAuth client credentials Audience: Add Test users under Testing status Message format: HTML (Model: OpenAI GPT — used to design an HTML email template) IM: Feishu (LARK) Bots in groups Use bots in groups. An n8n automation workflow template by dongou.

By Avkash Kakdiya

How it works This workflow captures idea submissions from a webhook and enriches them using AI. It extracts key fields like Title, Tags, Submitted By, and Created date in IST format. The cleaned data is stored in a Notion database for centralized tracking. Finally, a confirmation message is posted in Slack to notify the team. Step-by-step Step-by-step 1. Capture and process submission Webhook** – Receives idea submissions with text and user ID. AI Agent & OpenAI Model** – Enrich and structure the input into Title, Tags, Submitted By, and Created fields. Code** – Extracts clean data, formats tags, and prepares the entry for Notion. 2. Store in Notion Add to Notion** – Creates a new database entry with mapped fields: Title, Submitted By, Tags, Created. 3. Notify in Slack Send Confirmation (Slack)** – Posts a confirmation message with the submitted idea title. Why use this? Centralizes idea collection directly into Notion for better organization. Eliminates manual formatting with AI-powered data structuring. Ensures consistency in tags, submitter info, and timestamps. Provides instant team-wide visibility via Slack notifications. Saves time while keeping idea management streamlined and transparent. An n8n automation workflow template by Avkash Kakdiya.

By Avkash Kakdiya

How it works This workflow automatically classifies and routes new or updated Linear issues using AI. When an issue is created or updated, its title and description are analyzed by an OpenAI-powered classifier. The workflow then determines the correct team, routes the issue through the right path, and updates it in Linear. This ensures accurate, consistent triaging and removes the need for manual assignment. Step-by-step 1. Trigger and validation Linear Trigger** – Detects new or updated issues in Linear. Filter New Issues Only** – Ensures the issue has a valid title. If (Create or Update)** – Confirms the action is either create or update. 2. AI classification OpenAI Chat Model** – Provides language model capabilities for classification. AI Agent (Bug Classifier)** – Uses issue title and description to assign a team ID. 3. Routing logic Engineering Router** – Checks if classification output is Engineering. Product Router** – Checks if classification output is Product. Design Router** – Checks if classification output is Design. Default Router** – Fallback if no match is found. 4. Update Linear issue Assign to Engineering** – Updates team assignment in Linear. Assign to Product** – Updates team assignment in Linear. Assign to Design** – Updates team assignment in Linear. Assign to Default** – Assigns to fallback team if no match. Why use this? Automates issue triage, eliminating manual team assignment. Speeds up bug resolution by instantly routing to the right team. Ensures consistency in bug categorization using AI-driven analysis. Scales effortlessly with growing issue volume. Reduces human error in issue management. An n8n automation workflow template by Avkash Kakdiya.

By Ruslan Elishev

🤖 Telegram Bot with Dynamic Multi-Level Menu System What This Workflow Does Ever wanted to build a Telegram bot with professional-looking menus that actually work? This n8n workflow creates an interactive bot with dynamic inline keyboards, multi-level navigation, and smart button routing - all without writing complex code from scratch. The bot features a clean separation between your menu structure and business logic. This means you can change your menus anytime without breaking the underlying functionality. Think of it like WordPress menus but for Telegram bots - you define the navigation, and the workflow handles everything else. Your bot will respond with personalized messages, remember user context, handle button clicks smoothly (no annoying loading spinners!), and route different actions to specialized handlers. Whether users are rating your service, checking their subscription status, or navigating through settings, everything just works. 🚀 Getting Started in 3 Minutes Step 1: Get Your Bot Token Head over to Telegram and chat with @BotFather. Create a new bot (or use an existing one) and grab that token. In the workflow, find the purple "Set Bot Token" node and replace [!!! YOUR_BOT_TOKEN_HERE !!!] with your actual token. Step 2: Activate the Magic Save the workflow, click on "Production" tab, and you'll see a webhook URL. Toggle the workflow to Active. That's it - your bot is live! Step 3: See It In Action Message your bot on Telegram. Type /start and watch your beautiful menu appear. Click around, explore the buttons - everything is already set up and working. 🎨 Making It Yours Want to Add Your Own Menus? Open the workflow and look for the sticky note titled "📖 COMPLETE GUIDE: ADDING MENUS & ACTIONS". I've written step-by-step instructions right there in the workflow. You'll find exact examples showing how to add a contact menu, subscription status checker, or whatever you need. The beauty is in the simplicity - menus are just text and buttons. No complicated logic mixed in. Check the "📚 REAL EXAMPLES" sticky note for copy-paste templates you can modify. Need Custom Actions? When a button needs to actually DO something (save data, call an API, send an email), that's where handlers come in. The workflow includes 7 pre-built handlers for common tasks like ratings, language switching, and analytics. Want to add your own? The "💡 ADDING HANDLERS" sticky note walks you through it. 💡 Why This Workflow Is Different Most Telegram bot tutorials have you mixing menu code with business logic, making changes a nightmare. This workflow separates everything cleanly. Your menus live in one place, your logic in another. It's like having a control panel for your bot. The workflow also solves a common n8n limitation - the native Telegram node doesn't support dynamic inline keyboards. Instead of giving up, this workflow uses HTTP requests directly to the Telegram API, giving you full control over every feature. 🔧 Pro Tips from the Trenches After building dozens of Telegram bots, here's what I've learned: Always include a "Back" button - users panic without an escape route Use emojis in your buttons - they make everything friendlier Test each menu path after changes - one typo can break navigation Keep action handlers focused - one handler, one job Hit a snag? Check the "🐛 TROUBLESHOOTING & TIPS" sticky note in the workflow. I've documented all the common "gotchas" and their fixes. 📦 What's Included This workflow comes with everything you need: Centralized menu configuration system Smart routing that automatically detects which button was pressed 7 ready-to-use action handlers (modify or replace as needed) Parallel processing for lightning-fast responses Built-in error handling with fallback menus Comprehensive documentation right in the workflow via sticky notes 🚀 Taking It Further Once you're comfortable with the basics, this architecture scales beautifully. Connect a database to remember user preferences. Integrate with your CRM to pull customer data. Add payment processing for a shopping bot. The modular design means you can enhance one part without touching the others. The workflow sticky notes contain advanced examples for multi-language support, user authentication, and API integrations. Everything is explained in plain English with code examples you can actually use. 🤝 One Last Thing This workflow started as a simple dynamic menu with rating workflow and evolved into something much more powerful through community feedback. If you build something cool with it, I'd love to hear about it. And if you get stuck, remember - all the answers are in those sticky notes. I spent way too much time making them ridiculously detailed so you wouldn't have to struggle like I did. Happy bot building! 🎯 Version: 1.0 - Centralized Menu System with Branching Author: Ruslan Elishev. An n8n automation workflow template by Ruslan Elishev.

By AI/ML API | D1m7asis

This n8n workflow turns Telegram into a personal language tutor. Users can choose between different learning modes — vocabulary, grammar, quiz, or mixed lessons — simply by adding a hashtag to their message. The bot processes requests with AI/ML API and sends back structured, interactive lessons in Telegram. 🚀 Features 📩 Telegram-based input with hashtag commands 🧠 Adaptive AI responses (vocabulary, grammar, quiz) 🔤 Pronunciation support in Latin transcription 📒 Grammar explanations with examples ❓ Custom quizzes with auto-feedback 💬 Supportive learning experience with motivational messages ⏳ Typing indicator for smoother UX 🛠 Setup Guide 📲 Create Telegram Bot Go to @BotFather Use /newbot → choose a name and username Save the bot token 🔐 Set Up Credentials in n8n Telegram API: Use your bot token AI/ML API: Add your API key under AI/ML account ⚙️ Configure the Workflow Import the JSON into n8n Update credentials (Telegram + AI/ML API) Activate the workflow 💬 Start Learning In Telegram, send a message with one of the supported hashtags: #vocabulary — learn new words #grammar — study rules with examples #quiz — get exercises Or just send plain text for a free-form AI response 🔍 Node Overview Telegram Trigger** → Listens for incoming messages Show Typing Indicator** → Displays “typing…” while processing Switch Node** → Routes message by hashtag (#vocabulary, #grammar, #quiz) Prompt Builder Nodes** → Create JSON payload for AI/ML API AI/ML API Node** → Generates the structured lesson Telegram Send** → Sends the formatted response back to the user 💡 Example Flow User Input: #vocabulary кукуруза Bot Output: Кукуруза (Kukurúza) — Corn Pronunciation: koo-koo-ROO-zah Sentence: Я люблю есть кукурузу на гриле. I love eating grilled corn. 👉 Try to write your own sentence with “кукуруза”!. An n8n automation workflow template by AI/ML API | D1m7asis.

By Evoort Solutions

🎁 Automate YouTube Giveaway Winner Selection with YouTube Comments Scraper API Description: Easily automate your YouTube video giveaways using n8n and the YouTube Comments Scraper API. This workflow fetches comments, selects a random winner, logs results to Google Sheets, and notifies the admin—all hands-free! 🧩 Node-by-Node Breakdown | Node | Name | Purpose | | ---- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | 1️⃣ | Form Trigger | Captures a YouTube video URL from a user via form submission. | | 2️⃣ | Fetch YouTube Comments | Makes a POST request to YouTube Comments Scraper API to retrieve comments. | | 3️⃣ | Check API Response Status | Ensures that the response status is 200 before proceeding. | | 4️⃣ | Select Random Commenter | Parses the comments and selects a random commenter as the giveaway winner. | | 5️⃣ | Log Winner to Google Sheet | Appends winner name, video URL, and date to a Google Sheet for record-keeping. | | 6️⃣ | Notify Winner Email | Sends a congratulatory email to the admin with the selected winner's name. | | 7️⃣ | Notify: Invalid API Response | If the API fails, sends an alert to the admin about the issue. | 🔑 How to Get Your RapidAPI Key To use the YouTube Comments Scraper API, follow these steps: Go to YouTube Comments Scraper API. Sign in or create a free RapidAPI account. Click the "Subscribe to Test" button. Copy your x-rapidapi-key from the "Code Snippets" or "Header Parameters" section. Paste it into your HTTP Request node in n8n. 🎯 Use Case & Benefits ✅ Use Case: Automatically pick a random commenter from a YouTube video as a giveaway winner. 🚀 Benefits: Fully automated** – no manual comment scanning or random selection. Accurate & fair** – random selection from valid commenters only. Time-saving** – especially for creators running multiple giveaways. Integrated logging** – keep a historical record of all winners in Google Sheets. Email alerts** – get notified whether the flow succeeds or fails. 👥 Who Is This For? YouTube Content Creators** running giveaways. Marketing Teams** promoting products via YouTube contests. Agencies** managing influencer campaigns. Developers & Automation Enthusiasts** looking to simplify giveaway processes. 💡 Why Use YouTube Comments Scraper API? The YouTube Comments Scraper API offers a simple and effective way to extract public YouTube comments programmatically. It’s fast, reliable, and integrates smoothly with platforms like n8n. You’ll use this API: To retrieve all comments from a YouTube video. To power fair and transparent giveaways. To trigger downstream automations like winner logging and notification. 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!. An n8n automation workflow template by Evoort Solutions.

By Rahul Joshi

Description Turn incoming Gmail messages into structured Zendesk tickets, enriched by Azure OpenAI, and log key details to Google Sheets for tracking. Ideal for IT Support teams needing fast, consistent intake and documentation. ⚡ What This Template Does Fetches new emails via Gmail Trigger. ✉️ Normalizes Gmail data and formats it for downstream steps. Enriches and structures content with Azure OpenAI Chat Model and Output Parsers. Creates Zendesk tickets from the processed data. 🎫 Appends or updates logs in Google Sheets for auditing and reporting. 📊 Key Benefits Saves time by automating ticket creation and logging. ⏱️ Improves ticket quality with AI-driven normalization and structure. Ensures consistent records in Google Sheets for easy reporting. Reduces manual errors in IT Support intake. ✅ Features Gmail-triggered intake flow for new messages. AI enrichment using Azure OpenAI Chat Model with parsing and memory tooling. Zendesk ticket creation (create: ticket) with structured fields. Google Sheets logging (appendOrUpdate: sheet). Modular design with Execute Workflow nodes for reuse and scaling. Requirements n8n instance (Cloud or self-hosted). Gmail credentials configured in n8n for the Gmail Trigger. Zendesk credentials with permission to create tickets. Google Sheets credentials with access to the target spreadsheet (append/update enabled). Azure OpenAI credentials configured for the Azure OpenAI Chat Model and associated parsing. Target Audience IT Support and Helpdesk teams handling email-based requests. 🛠️ Operations teams standardizing inbound email workflows. Agencies and MSPs offering managed support intake. Internal automation teams centralizing ticket capture and logging. Step-by-Step Setup Instructions Connect Gmail credentials in n8n and select the inbox/label for the Gmail Trigger. Add Zendesk credentials and confirm ticket creation permissions. Configure Google Sheets credentials and select the target sheet for logs. Add Azure OpenAI credentials to the Azure OpenAI Chat Model node and verify parsing steps. Import the workflow, assign credentials to each node, update any placeholders, and run a test. Rename the final email/logging nodes descriptively (e.g., “Log to Support Sheet”) and schedule if needed. An n8n automation workflow template by Rahul Joshi.

By Evoort Solutions

Job Search Automation with Job Search Global API & Google Sheet Logging Description: Automate your job search process by querying the Job Search Global API via RapidAPI every 6 hours for a specified keyword like “Web Developer.” This workflow extracts job listings and saves them directly to Google Sheets, with alerts sent for any API failures. Workflow Overview Schedule Trigger Runs the workflow automatically every 6 hours to ensure up-to-date job listings. Set Search Term Defines the dynamic job keyword, e.g., "Web Developer," used in API requests. Fetch Job Listings Sends a POST request to the Job Search Global API (via RapidAPI) to retrieve job listings with pagination. Check API Response Validates the API response status, branching workflow on success or failure. Extract Job Data Parses the job listings array from the API response for processing. Save to Google Sheet Appends or updates job listings in Google Sheets, avoiding duplicates by matching job titles. Send Failure Notification Email Sends an alert email if the API response fails or returns an error. How to Obtain Your RapidAPI Key (Quick Steps) Go to RapidAPI Job Search Global API. Sign up or log in to your RapidAPI account. Subscribe to the API plan that suits your needs. Copy your unique X-RapidAPI-Key from the dashboard. Insert this key into your workflow’s HTTP Request node headers. How to Configure Google Sheets Create a new Google Sheet for job listings. Share the sheet with your Google Service Account email to enable API access. Use the sheet URL in the Google Sheets node within your workflow. Map columns correctly based on the job data fields. Google Sheet Columns Used | Column Name | Description | | ----------- | ----------------------------------- | | title | Job title | | url | Job posting URL | | company | Company name | | postDate | Date job was posted | | jobSource | Source of the job listing | | slug | Unique job identifier or slug | | sentiment | Sentiment analysis score (if any) | | dateAdded | Date the job was added to the sheet | | tags | Associated tags or keywords | | viewCount | Number of views for the job post | Use Cases & Benefits Automated Job Tracking:** Get fresh job listings without manual searching by automatically querying the Job Search Global API multiple times per day. Centralized Job Data:** Save and update listings in Google Sheets for easy filtering, sharing, and tracking. Failure Alerts:** Get notified immediately if API calls fail, helping maintain workflow reliability. Customizable Search:** Change keywords anytime to tailor job searches for different roles or industries. Who Is This Workflow For? Recruiters** looking to monitor job market trends in real-time. Job Seekers** who want to automate job discovery for specific roles like “Web Developer.” HR Teams** managing talent pipelines and job postings. Data Analysts** needing structured job market data for research or reporting. 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!. An n8n automation workflow template by Evoort Solutions.

By Rohit Dabra

Google Sheets → Stripe Payment Automation Workflow 📌 Overview This workflow automates the end-to-end process of generating and sending client payment links using Google Sheets and Stripe. Whenever a new or updated entry is added to the Google Sheet, the workflow will: Fetch client and invoice details. Create a Stripe Product and Price. Generate a Stripe Payment Link. Store the link back in the Google Sheet. Upload a copy of the invoice to Google Drive. Send a professional, formatted email with the payment link to the client using Gmail. 🔗 Demo Video: Watch on YouTube ⚡️ Workflow Steps Trigger – The workflow is triggered on any update in the Google Sheet. Filter – Ensures only relevant rows (e.g., PENDING invoices) proceed. Stripe Automation Create Stripe Product Create Stripe Price Generate Stripe Payment Link Google Drive – Store invoice files (if required). Google Sheets – Update the sheet with the generated Stripe Payment Link and timestamp. Gmail – Send a client-facing email with the invoice details and payment link. 🛠 Setup Guide Prerequisites n8n account** Google Sheets & Google Drive credentials** Gmail API credentials** Stripe API Key** Steps Clone/Import Workflow Import the workflow JSON file into your n8n instance. Configure Google Sheets Create a Google Sheet with columns: Order ID, Client Name, Client Email, Items Description, Due Date, Amount, Currency, Invoice Status, Invoice Link, Stripe Payment Link, Last Updated Connect your Google Sheets node to this sheet. Set Up Stripe Obtain your Stripe Secret Key from Stripe Dashboard. Add it in the Stripe nodes for Product, Price, and Payment Link creation. Google Drive Configure to store invoice backups (optional). Gmail Authorize Gmail and set up the Send Email node. Customize the email template with client details and the Stripe link. Test the Workflow Add a sample row in Google Sheets. Run the workflow manually or update the sheet to trigger automatically. Verify that the Stripe link is created, updated in the sheet, and emailed to the client. ✅ Now your workflow is ready to automatically manage client invoices and payments with Stripe + Google Sheets + Gmail + Google Drive. An n8n automation workflow template by Rohit Dabra.

By Rahul Joshi

Description This workflow automates Zendesk ticket escalation by creating ClickUp tasks for urgent cases and notifying the support team in Telegram. It ensures that high-priority tickets are instantly visible to the right team members, avoiding delays in resolution. What This Template Does (Step-by-Step) 🟢 Trigger (Manual Test or Later Zendesk Trigger) Currently uses a manual trigger (Execute Workflow) for testing. In production, this would start whenever a pending Zendesk ticket appears. 🎫 Fetch Zendesk Tickets Pulls all pending tickets assigned to a group. Sorts them by status and date. 🧹 Select Latest Ticket Sorts by created_at and keeps only the newest ticket. Outputs: id, subject, description, requester_id, created_at. 📧 Fetch Requester Email Retrieves requester details (name, email, timezone) from Zendesk Users API. 🔀 Merge Ticket & Requester Data Combines both streams: ticket info + requester info. Ensures the ClickUp task payload has everything it needs. 📝 Prepare ClickUp Task Payload Builds a structured task: Task Name: [Escalation] {Subject} (Ticket #ID) Description: Ticket + requester details + escalation message Priority: 3 (default, can be adjusted) Tags: zendesk, escalation 📂 Create ClickUp Task Pushes the structured task into ClickUp under the escalation list. Assigns it to a predefined team member. 📨 Format Telegram Alert Message Generates a concise but urgent message: Ticket subject + ID Requester name + email Direct ClickUp link Adds urgency formatting (🚨 Immediate Attention Required). 📢 Send Telegram Escalation Alert Posts the alert into the chosen Telegram chat/team. Ensures managers/stakeholders know instantly. Prerequisites Zendesk account + API credentials ClickUp account + API credentials Telegram bot token & chat ID n8n instance (cloud or self-hosted) Customization Ideas ⚡ Replace manual trigger with Zendesk “Ticket Created” trigger. 🎯 Add SLA-based conditions (e.g., escalate only if response > 4 hrs). 📊 Auto-assign ClickUp tasks by ticket category. 🔔 Add Slack/Email notification along with Telegram. 📂 Store escalation logs into Notion or Google Sheets. Key Benefits ✅ Zero delay in handling critical tickets ✅ Automatically creates ClickUp task + Telegram alert ✅ Reduces manual handoff between support → escalation team ✅ Keeps everyone aligned in real-time Perfect For 🎯 Support teams needing fast escalations 📈 SaaS companies managing large ticket volumes 🚀 Agencies ensuring VIP clients never wait. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description: Stay on top of product issues with this n8n automation template that centralizes bug reports from Zendesk into a Google Sheets dashboard. The workflow filters only tickets tagged as “bug,” enriches them with reporter details, and updates a single source of truth for developers, QA teams, and support staff. Perfect for product managers, SaaS companies, and agile teams that need full visibility into bug trends and customer impact without wasting time on manual data entry. What This Template Does (Step-by-Step) ⚡ Manual Trigger or Scheduling Run on-demand after releases or bug triage meetings, or set up a schedule to auto-run daily/weekly. 📥 Fetch All Zendesk Tickets Retrieves tickets from your Zendesk account with full metadata. 🔍 Filter Bug Reports Only Processes only tickets tagged as “bug” to ensure relevance. 👤 Add Reporter Details Enriches bug reports with requester’s name, email, and profile data for impact tracking. 📊 Update Google Sheets Bug Tracker Stores bug details including Ticket No., Description, Status, Reporter Info, and Tags. ✔️ Smart update avoids duplicates by using description as a unique key. 🔁 Continuous Bug Aggregation Ensures all relevant bug reports are tracked and kept up-to-date in one central place. Key Features 🔍 Tag-based bug filtering 📊 Centralized bug dashboard in Google Sheets ⚡ Zendesk + Google Sheets integration with OAuth2 ♻️ Real-time sync with deduplication logic 🔐 Secure API credential handling Use Cases 🐞 Track and prioritize product bugs from customer reports 📊 Give QA and dev teams a shared bug dashboard 📩 Identify high-impact bugs based on affected customers 📈 Monitor bug frequency and trends for release planning Required Integrations Zendesk API (for ticket fetch + user info) Google Sheets (for storing/updating bug tracker) Why Use This Template? ✅ Centralizes bug visibility for all teams ✅ Saves hours of manual spreadsheet updates ✅ Improves prioritization with customer context ✅ Scales easily with more tags or categories ✅ Keeps bug tracking transparent across stakeholders. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Automatically consolidate Zendesk and Freshdesk ticket data into a unified performance dashboard with KPI calculations, Google Sheets logging, real-time Slack alerts, and weekly Gmail email reports. Provides complete visibility into support operations, SLA compliance, and customer satisfaction across multiple platforms. 📊💬📧 What This Template Does Runs weekly on schedule to fetch tickets from both Zendesk and Freshdesk. ⏰ Merges ticket data into a standardized JSON structure with normalized priorities, statuses, and channels. 🔄 Logs all tickets and metadata into Google Sheets for audit-ready performance tracking. 📑 Calculates advanced KPIs including resolution rates, SLA breaches, CSAT score estimation, urgent ticket rates, and performance grading. 📊 Evaluates alert conditions (e.g., high SLA breach, low CSAT, backlog risk). 🚨 Sends formatted Slack alerts with performance grades, key metrics, and recommendations. 💬 Generates corporate-style HTML weekly reports and delivers them via Gmail. 📧 Key Benefits Unifies Zendesk and Freshdesk data into one consistent reporting flow. 🌐 Provides actionable KPIs for SLA monitoring, customer satisfaction, and backlog health. ⏱️ Ensures leadership visibility with Google Sheets logs and professional email reports. 🧾 Alerts the support team instantly on Slack when performance drops. 🚨 Reduces manual data analysis with automated grading and recommendations. 🤖 Features Multi-Platform Ticket Integration – Fetches tickets from Zendesk and Freshdesk. 🎫 Data Normalization – Cleans descriptions, maps priorities/statuses, and detects escalations. 🧼 Google Sheets Logging – Tracks tickets with IDs, URLs, tags, timestamps, and metadata. 📈 KPI Calculation Engine – Computes SLA breach rate, resolution rate, CSAT, escalation %, and more. 🧮 Performance Grading – Grades support performance (A–D) with detailed descriptions. 🏅 Slack Alerts – Notifies with active alerts, recommendations, and emoji-based health signals. 📢 Weekly Gmail Reports – Delivers branded HTML reports for management and audits. ✨ Requirements n8n instance (cloud or self-hosted). Zendesk API credentials with ticket read access. Freshdesk API credentials with ticket read access. Google Sheets OAuth2 credentials with spreadsheet write permissions. Slack Bot API credentials with posting permissions. Gmail OAuth2 credentials with send email permissions. Pre-configured Google Sheet for KPI logging. Target Audience Support managers overseeing multi-platform ticketing systems. 👩‍💻 Customer success teams monitoring SLA compliance and CSAT health. 🚀 SMBs running Zendesk + Freshdesk who need unified dashboards. 🏢 Remote/global support teams needing automated KPI visibility. 🌐 Executives requiring weekly performance reports and recommendations. 📈 Step-by-Step Setup Instructions Connect Zendesk, Freshdesk, Google Sheets, Slack, and Gmail credentials in n8n. 🔑 Update the Google Sheet ID in the “Log KPIs in Google Sheets” node. 📊 Configure Slack channel ID for alerts (default: zendesk-churn-alerts). 💬 Replace {Enter Your Email} in the Gmail node with your recipient email. 📧 Adjust thresholds in the KPI calculation node (default: 4h response, 24h resolution). ⏱️ Test with sample tickets to validate Sheets logging, Slack alerts, and Gmail reports. ✅ Deploy on schedule (default: weekly at 8 PM) for continuous tracking. 🗓️. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Automatically convert structured Slack messages into Jira issues with parsed titles, descriptions, and priorities. This workflow also downloads file attachments from Slack (e.g., screenshots, logs, or documents) and uploads them directly into the created Jira issue. It then confirms success back to the Slack channel, ensuring transparency and seamless collaboration. 📋💬📎 What This Template Does Monitors a designated Slack channel for new issue reports. 🔔 Parses Slack message text with regex to extract title, description, priority, and type. 🧠 Creates a new Jira issue with the structured data. 🎫 Detects and processes attachments, splitting multiple files into batches. 📂 Downloads files from Slack using secure URLs and Slack bot authentication. 🔑 Uploads attachments directly into the created Jira issue. 📎 Sends a Slack confirmation with Jira issue key, link, and summary details. ✅ Key Benefits Eliminates manual Jira ticket creation from Slack messages. ⏱️ Preserves critical context by attaching screenshots, logs, and documentation. 📎 Ensures structured, standardized issue reporting across teams. 🔄 Provides instant Slack confirmation with direct Jira links. 📲 Handles multiple attachments gracefully with batch processing. ⚡ Features Slack Trigger – Monitors specific channels for new issue messages. 💬 Message Parsing Engine – Extracts title, description, priority, and type using regex + fallback logic. 📝 Jira Integration – Creates structured Jira issues with proper fields (summary, description, priority, type). 🎫 Attachment Handling – Splits, downloads, and uploads Slack files into Jira automatically. 📂 Slack Confirmation – Sends formatted success messages with clickable Jira links. 🔗 Robust Data Handling – Supports rich text, multiple files, and smart mappings of Slack priorities to Jira. 🧠 Requirements n8n instance (cloud or self-hosted). Slack Bot API credentials with channels:history, files:read, and chat:write permissions. Jira Software Cloud API credentials with project and issue creation permissions. Pre-configured Slack channel for reporting issues. Jira project set up with supported issue types (bug, task, feature, etc.). Target Audience Software development teams managing issue intake from Slack. 👩‍💻 QA and testing teams reporting bugs directly from Slack. 🧪 IT support teams needing structured Jira issues with attachments. 🛠️ Agile teams looking for seamless Slack → Jira integration. 🚀 Remote teams requiring real-time visibility into Jira issue creation. 🌐 Step-by-Step Setup Instructions Connect Slack and Jira credentials in n8n. 🔑 Configure the Slack channel ID to listen for issue reports. 💬 Map Jira project and issue type IDs in the “Create Jira Issue” node. 🎫 Customize parsing logic for message formats (default: Title: X, Description: Y, Priority: Z). 📝 Ensure Slack files can be downloaded with your bot token (files:read scope). 📂 Test with a sample message containing a title, description, and attachment. ✅ Deploy and monitor Slack → Jira issue creation in real-time. ⚡. An n8n automation workflow template by Rahul Joshi.

By Muhammad Farooq Iqbal

Transform any product image into engaging UGC (User-Generated Content) videos and images using AI automation. This comprehensive workflow analyzes uploaded images via Telegram, generates realistic product images, and creates authentic UGC-style videos with multiple scenes. Key Features: 📱 Telegram Integration**: Upload images directly via Telegram bot 🔍 AI Image Analysis**: Automatically analyzes and describes uploaded images using GPT-4 Vision 🎨 Smart Image Generation**: Creates realistic product images using Fal.ai's nano-banana model with reference images 🎬 UGC Video Creation**: Generates 3-scene UGC-style videos using KIE.ai's Veo3 model 📹 Video Compilation**: Automatically combines multiple video scenes into a final output 📤 Instant Delivery**: Sends both generated images and final videos back to Telegram Perfect For: E-commerce businesses creating authentic product content Social media marketers needing UGC-style content Influencers and content creators Marketing agencies automating content production Anyone looking to scale UGC content creation What It Does: Receives product images via Telegram Analyzes image content with AI vision Generates realistic product images with UGC styling Creates 3-scene video prompts (Hook → Product → CTA) Generates individual video scenes Combines scenes into final UGC video Delivers both image and video results Technical Stack: OpenAI GPT-4 Vision for image analysis Fal.ai for image generation and video merging KIE.ai Veo3 for video generation Telegram for input/output interface Ready to automate your UGC content creation? This workflow handles everything from image analysis to final video delivery! Updated. An n8n automation workflow template by Muhammad Farooq Iqbal.

By Eric

Why use this? This workflow turns any event-related text into a new event on your calendar. Poster for a concert you want to go to? Snap a photo [with your iPhone] and boom city, it's in your calendar. † Parent-Teacher conference you can't forget? Forward that email to the webhook. † Appointment card from the doctor? Snap it in, baby! † How it works (Very, very simple) Data received by webhook. Ai Agent prompted to parse the text into structured event data. Create event in NextCloud cal (or Zoho, or GoogleCal). (Optional, intended use case) Set up the iOS Shortcut (linked in workflow) to turn your iPhone into the trigger for this workflow. Say "Siri, Add Event To Calendar," and she opens the camera, OCRs the text in the photo and sends that to the webhook. Boom city. Expected input structure [ { "body": { "cal": "work", <- this is optional for deciding among calendars "eventInfo": "Join us for Betty-Jean's 98th birthday! (Yes, we celebrate every year now...) It's October 11th at 2:30pm, at Betty-Jean's house. Come after lunch 'cause her kitchen hasn't been used in 20 years. She mellows out pretty early these days so plan for the party to end by 4:00pm." } } ] Extras Includes multiple calendar nodes.** Whether you're using NextCloud, Zoho or Google Cal, you can swap in the node you need. iOS Shortcut linked in workflow.** I also set up a Shortcut for the iPhone. The first time you use the Shortcut, you'll need to give it some permissions, and paste in your production webhook URL. Expansion option: Accept images**. iPhone has a native OCR feature but this isn't always an option. To make this workflow more versatile, consider building out a second branch to send an image to an Agent to parse the event data from the image directly. Expansion option: Multiple triggers**. You could add more triggers to receive event-related text from other sources, like an IMAP node reading your email (pro tip: set up a designated folder and give the IMAP access only to that folder). † Workflow begins with a webhook which can receive correctly-formatted data from anywhere on the web --- mailhook, webform, iOS Shortcut, etc. Direct data to this webhook from your source of text to use this workflow. An n8n automation workflow template by Eric.

By Jose Luis Segura

Revolut Extracts Analyzer This n8n template processes Revolut statements, normalizes transactions, and uses AI to categorize expenses automatically. Use cases include detecting subscriptions, separating internal transfers, and building dashboards to track spending. How it works Get Categories from Supabase** Download & Transform** Loop Over Items** LLM Categorizer** Insert into Supabase** How to use Start with the manual trigger node or replace it with a schedule/webhook. Connect Google Drive to provide Revolut CSV files. Ensure Supabase has tables for transactions and categories. Extend with notifications, reports, or BI tools. Requirements Google Drive for CSV files Supabase tables for categories & transactions LLM provider (OpenAI/Gemini). An n8n automation workflow template by Jose Luis Segura.

By LeeWei

⚙️ Self Learning Agent: AI-Powered Email Auto-Responder that Improves with Feedback 🧑‍💻 Author: LeeWei Overview of the n8n Workflow This n8n workflow builds a self-improving AI agent for handling email responses. It integrates Gmail for incoming messages, uses an AI agent with a Supabase vector store for knowledge retrieval, drafts replies based on dynamic prompts, and evaluates confidence scores. High-confidence drafts are sent automatically, while low-confidence ones are routed to Google Sheets for human review. Feedback from Sheets triggers updates to the prompt or knowledge base, enabling the agent to learn and refine its responses over time. The workflow supports OpenAI and OpenRouter models, with structured output parsing and conditional routing for efficiency. How it Works • Triggers on new Gmail emails, extracts content, and uses an AI agent with company knowledge from Supabase to draft a response. • Assesses confidence; auto-sends high-confidence replies or saves drafts to Google Sheets for human feedback. • Monitors Sheets for updates, extracts feedback via AI, and applies changes—either refining the dynamic prompt or adding new info to the vector store. • Loops back improvements to enhance future responses without manual reconfiguration. Set Up Steps Setup takes about 20-30 minutes, focused on credentials and basic resource creation (e.g., Google Sheet and Supabase table). Detailed node-level guidance is in the workflow's sticky notes—clone the JSON for plug-and-play nodes, then edit only essentials like credentials and IDs. No need to rebuild nodes; they're pre-connected and ready. 🚀 Steps to Connect: Gmail Setup Set up OAuth2 credentials at console.cloud.google.com with scopes for Gmail (read/send). Paste into the Gmail Trigger and Gmail nodes' credentials fields. Test by sending a sample email to your connected inbox. OpenAI API Key Generate at platform.openai.com. Paste into the OpenAI Chat Model and OpenAI Chat Model1 nodes' credentials. 💡 Use a model like gpt-4o-mini for cost efficiency; adjust temperature in options for response creativity. OpenRouter API Key Sign up at openrouter.ai and create an API key. Paste into the OpenAI Chat Model2 node's credentials (used for feedback extraction). Select a model like gpt-4o-mini in the node for consistency. Supabase Connection Create a free account at supabase.com, set up a project, and add a table named documents with vector support (enable pgvector extension). Paste API URL and key into the Supabase Vector Store and Supabase Vector Store1 nodes' credentials. Initialize with sample docs via the workflow or dashboard for knowledge base testing. Google Sheets Setup Create OAuth2 credentials at console.cloud.google.com with scopes for Sheets (read/write). Paste into all Google Sheets nodes' credentials. Duplicate the sample sheet (ID: 1YDzwYd5LdTnSQlFM5YrDhhbCnNH7oHVvNg6x3mYu8I4) or create one with tabs: "Dynamic Var" (for prompts) and "Feedback" (columns: Id, Original Email, Draft, Human Feedback, Status). Replace the documentId in nodes with your sheet's ID. Plug and Play Instructions Clone the provided JSON directly into n8n—all nodes (triggers, agents, parsers, switches) are pre-wired and functional. No re-setup required beyond the steps above. Key editable fields (detailed in sticky notes): AI Agent Node: System Message** Customize the prompt template for response style (e.g., add rules for tone or specific facts). Default handles factual, concise replies. Structured Output Parser Node: JSON Schema** Adjust if adding output fields (e.g., include "suggested_followup" alongside "final_response" and "resolution_score"). If Node: Conditions** Tweak the confidence threshold (default: <4 routes to review) based on your risk tolerance. Information Extractor Node: Prompt** Refine the feedback analysis (e.g., prioritize certain feedback types like "add facts" vs. "update prompt"). Test with a sample email: Send a query to your Gmail, review in Sheets if low-confidence, provide feedback, and watch the agent improve on the next run. Potential Customizations Switch AI Models**: Swap OpenAI/OpenRouter nodes for alternatives like Anthropic via compatible n8n nodes. Add Notifications**: Insert a Slack or email node post-Sheets save for alerts on low-confidence drafts. Expand Knowledge Base**: Add a loader node to ingest more docs into Supabase automatically. Confidence Routing**: Duplicate the If node for multi-tier reviews (e.g., score 1-2 escalates to admin). Considerations and Improvements API Limits**: Monitor OpenAI/OpenRouter usage for costs; start with mini models. Supabase free tier handles small knowledge bases—upgrade for scale. Data Privacy**: Emails and feedback pass through AI providers—ensure compliance for sensitive info. Feedback Loop**: Test iterations to confirm improvements; initial runs may need manual prompt tweaks. Enhancements**: Integrate audio transcription for voice feedback or export logs for auditing. This workflow turns email handling into an adaptive, low-maintenance system—ideal for support teams or busy inboxes. For tweaks, reference the sticky notes or experiment in a test clone!. An n8n automation workflow template by LeeWei.

By FlyCode

⚙️ Automated Stripe Failed Payment Recovery (with Postmark + AI Email Generator) Recover failed Stripe subscription payments with AI-personalized emails sent via Postmark. 📝 Template Description Recover failed subscription payments automatically with Stripe, Postmark, and AI. This workflow listens for Stripe invoice.payment_failed webhooks, checks that the event is related to an auto-charged subscription, and then automatically sends a personalized email (generated with AI) to the customer. The email is polite, branded, but also urgent — encouraging the customer to pay quickly and avoid service cancellation. 🛠️ How it works 📣 Webhook Listens for Stripe webhook events. Make sure to connect it in your Stripe dashboard (see setup below). 🧹 Filter (Guard) Ensures the event is indeed an invoice event and filters out unrelated webhooks. 💡 Code Node Extracts useful fields (firstName, lastName, customer email, amount, currency, invoice number, hosted invoice URL, subscription description, account name). ✅ If Node Verifies that: Event type = invoice.payment_failed Billing reason = subscription_cycle Collection method = charge_automatically 👉 This ensures only recurring subscription invoices with auto-payment are processed. 🤖 AI Agent + OpenAI Generates a ready-to-send email JSON (to, subject, HTML body) using the extracted Stripe data. ✍️ You can customize the prompt here to match your brand’s tone of voice and style. 🧩 Code Parser Parses the AI model’s JSON output into fields (to_email, email_subject, email_body). 📧 HTTP Request (Postmark) Sends the email using Postmark’s API. You’ll need your own Postmark Server Token, From address, and Message Stream. 🚀 Setup Instructions 1. Stripe Webhook Go to Stripe Dashboard → Developers → Webhooks. Click + Add endpoint. Use your n8n Webhook URL (from the Webhook node) as the endpoint. Select event type: invoice.payment_failed. Save and deploy. 👉 Example docs: Stripe: Listen to events with webhooks. 2. Disable Stripe’s Default Failed Payment Emails In Stripe, go to Billing → Settings → Customer emails → Manage failed payments. Turn off “Failed payment” emails under the Revenue Recovery section. This prevents customers from receiving duplicate or conflicting emails. 3. Postmark Setup Create a Postmark account. Add a Server and copy the Server API Token. In n8n, add Postmark credentials with this token. Configure: From = your verified sending email (must be verified in Postmark). MessageStream = typically "outbound" (or any custom stream you set up). Docs: Postmark API overview. 4. OpenAI Setup Add your OpenAI credentials in n8n. Attach them to the OpenAI Chat Model node. You can modify the prompt in the AI Agent node to fit your company’s style. ✨ Customization Tips Update the AI prompt with your brand’s tone of voice (friendly, formal, playful, etc.). Adjust the HTML email design inside the prompt (button colors, footer, etc.). Add extra guard conditions (e.g., only trigger if invoice_amount > 0). Change the sending service: replace Postmark with Gmail, SMTP, or another provider. 💬 Or talk to our Billing Recovery Experts at flycode.com for hands-on help. ✅ Outcome Whenever a customer’s subscription payment fails, this workflow: Detects it instantly via Stripe Generates a polite but urgent recovery email Sends it automatically via Postmark Result: Fewer cancellations, higher recovered revenue, and a smoother customer experience. 💸💌. An n8n automation workflow template by FlyCode.

By Li CHEN

AWS News Analysis and LinkedIn Automation Pipeline Transform AWS industry news into engaging LinkedIn content with AI-powered analysis and automated approval workflows. Who's it for This template is perfect for: Cloud architects and DevOps engineers** who want to stay current with AWS developments Content creators** looking to automate their AWS news coverage Marketing teams** needing consistent, professional AWS content Technical leaders** who want to share industry insights on LinkedIn AWS consultants** building thought leadership through automated content How it works This workflow creates a comprehensive AWS news analysis and content generation pipeline with two main flows: Flow 1: News Collection and Analysis Scheduled RSS Monitoring: Automatically fetches latest AWS news from the official AWS RSS feed daily at 8 PM AI-Powered Analysis: Uses AWS Bedrock (Claude 3 Sonnet) to analyze each news item, extracting: Professional summary Key themes and keywords Importance rating (Low/Medium/High) Business impact assessment Structured Data Storage: Saves analyzed news to Feishu Bitable with approval status tracking Flow 2: LinkedIn Content Generation Manual Approval Trigger: Feishu automation sends approved news items to the webhook AI Content Creation: AWS Bedrock generates professional LinkedIn posts with: Attention-grabbing headlines Technical insights from a Solutions Architect perspective Business impact analysis Call-to-action engagement Automated Publishing: Posts directly to LinkedIn with relevant hashtags How to set up Prerequisites AWS Bedrock access** with Claude 3 Sonnet model enabled Feishu account** with Bitable access LinkedIn company account** with posting permissions n8n instance** (self-hosted or cloud) Detailed Configuration Steps 1. AWS Bedrock Setup Step 1: Enable Claude 3 Sonnet Model Log into your AWS Console Navigate to AWS Bedrock Go to Model access in the left sidebar Find Anthropic Claude 3 Sonnet and click Request model access Fill out the access request form (usually approved within minutes) Once approved, verify the model appears in your Model access list Step 2: Create IAM User and Credentials Go to IAM Console Click Users → Create user Name: n8n-bedrock-user Attach policy: AmazonBedrockFullAccess (or create custom policy with minimal permissions) Go to Security credentials tab → Create access key Choose Application running outside AWS Download the credentials CSV file Step 3: Configure in n8n In n8n, go to Credentials → Add credential Select AWS credential type Enter your Access Key ID and Secret Access Key Set Region to your preferred AWS region (e.g., us-east-1) Test the connection Useful Links: AWS Bedrock Documentation Claude 3 Sonnet Model Access AWS Bedrock Pricing 2. Feishu Bitable Configuration Step 1: Create Feishu Account and App Sign up at Feishu International Create a new Bitable (multi-dimensional table) Go to Developer Console → Create App Enable Bitable permissions in your app Generate App Token and App Secret Step 2: Create Bitable Structure Create a new Bitable with these columns: title (Text) pubDate (Date) summary (Long Text) keywords (Multi-select) rating (Single Select: Low, Medium, High) link (URL) approval_status (Single Select: Pending, Approved, Rejected) Get your App Token and Table ID: App Token: Found in app settings Table ID: Found in the Bitable URL (tbl...) Step 3: Set Up Automation In your Bitable, go to Automation → Create automation Trigger: When field value changes → Select approval_status field Condition: approval_status equals "Approved" Action: Send HTTP request Method: POST URL: Your n8n webhook URL (from Flow 2) Headers: Content-Type: application/json Body: {{record}} Step 4: Configure Feishu Credentials in n8n Install Feishu Lite community node (self-hosted only) Add Feishu credential with your App Token and App Secret Test the connection Useful Links: Feishu Developer Documentation Bitable API Reference Feishu Automation Guide 3. LinkedIn Company Account Setup Step 1: Create LinkedIn App Go to LinkedIn Developer Portal Click Create App Fill in app details: App name: AWS News Automation LinkedIn Page: Select your company page App logo: Upload your logo Legal agreement: Accept terms Step 2: Configure OAuth2 Settings In your app, go to Auth tab Add redirect URL: https://your-n8n-instance.com/rest/oauth2-credential/callback Request these scopes: w_member_social (Post on behalf of members) r_liteprofile (Read basic profile) r_emailaddress (Read email address) Step 3: Get Company Page Access Go to your LinkedIn Company Page Navigate to Admin tools → Manage admins Ensure you have Content admin or Super admin role Note your Company Page ID (found in page URL) Step 4: Configure LinkedIn Credentials in n8n Add LinkedIn OAuth2 credential Enter your Client ID and Client Secret Complete OAuth2 flow by clicking Connect my account Select your company page for posting Useful Links: LinkedIn Developer Portal LinkedIn API Documentation LinkedIn OAuth2 Guide 4. Workflow Activation Final Setup Steps: Import the workflow JSON into n8n Configure all credential connections: AWS Bedrock credentials Feishu credentials LinkedIn OAuth2 credentials Update webhook URL in Feishu automation to match your n8n instance Activate the scheduled trigger (daily at 8 PM) Test with manual webhook trigger using sample data Verify Feishu Bitable receives data Test approval workflow and LinkedIn posting Requirements Service Requirements AWS Bedrock** with Claude 3 Sonnet model access AWS account with Bedrock service enabled IAM user with Bedrock permissions Model access approval for Claude 3 Sonnet Feishu Bitable** for news storage and approval workflow Feishu account (International or Lark) Developer app with Bitable permissions Automation capabilities for webhook triggers LinkedIn Company Account** for automated posting LinkedIn company page with admin access LinkedIn Developer app with posting permissions OAuth2 authentication setup n8n community nodes**: Feishu Lite node (self-hosted only) Technical Requirements n8n instance** (self-hosted recommended for community nodes) Webhook endpoint** accessible from Feishu automation Internet connectivity** for API calls and RSS feeds Storage space** for workflow execution logs Cost Considerations AWS Bedrock**: ~$0.01-0.05 per news analysis Feishu**: Free tier available, paid plans for advanced features LinkedIn**: Free API access with rate limits n8n**: Self-hosted (free) or cloud subscription How to customize the workflow Content Customization Modify AI prompts** in the AI Agent nodes to change tone, focus, or target audience Adjust hashtags** in the LinkedIn posting node for different industries Change scheduling** frequency by modifying the Schedule Trigger settings Integration Options Replace LinkedIn** with Twitter/X, Facebook, or other social platforms Add Slack notifications** for approved content before posting Integrate with CRM** systems to track content performance Add content calendar** integration for better planning Advanced Features Multi-language support** by modifying AI prompts for different regions Content categorization** by adding tags for different AWS services Performance tracking** by integrating analytics platforms Team collaboration** by adding approval workflows with multiple reviewers Technical Modifications Change RSS sources** to monitor other AWS blogs or competitor news Adjust AI models** to use different Bedrock models or external APIs Add data validation** nodes for better error handling Implement retry logic** for failed API calls Important Notes Service Limitations This template uses community nodes (Feishu Lite) and requires self-hosted n8n Geo-restrictions** may apply to AWS Bedrock models in certain regions Rate limits** may affect high-frequency posting - adjust scheduling accordingly Content moderation** is recommended before automated posting Cost considerations**: Each AI analysis costs approximately $0.01-0.05 USD per news item Troubleshooting Common Issues AWS Bedrock Issues: Model not found**: Ensure Claude 3 Sonnet access is approved in your region Access denied**: Verify IAM permissions include Bedrock service access Rate limiting**: Implement retry logic or reduce analysis frequency Feishu Integration Issues: Authentication failed**: Check App Token and App Secret are correct Table not found**: Verify Table ID matches your Bitable URL Automation not triggering**: Ensure webhook URL is accessible and returns 200 status LinkedIn Posting Issues: OAuth2 errors**: Re-authenticate LinkedIn credentials Posting failed**: Verify company page admin permissions Rate limits**: LinkedIn has daily posting limits for company pages Security Best Practices Never hardcode credentials** in workflow nodes Use environment variables** for sensitive configuration Regularly rotate API keys** and access tokens Monitor API usage** to prevent unexpected charges Implement error handling** for failed API calls. An n8n automation workflow template by Li CHEN.

By Mariela Slavenova

This template enriches a lead list by analyzing each contact’s LinkedIn activity and auto-generating a single personalized opening line for cold outreach. Drop a spreadsheet into a Google Drive folder → the workflow parses rows, fetches LinkedIn content (recent post or profile), uses an LLM to craft a one-liner, writes the result back to Google Sheets, and sends a Telegram summary. ⸻ Good to know • Works with two paths: • Recent post found → personalize from the latest LinkedIn post. • No recent post → personalize from profile fields (headline, about, current role). • Requires valid Apify credentials for LinkedIn scrapers and LLM keys (Anthropic and/or OpenAI). • Costs depend on the LLM(s) you choose and scraping usage. • Replace all placeholders like [put your token here] and [put your Telegram Bot Chat ID here] before running. • Respect the target platform’s terms of service when scraping LinkedIn data. What this workflow does Trigger (Google Drive) – Watches a specific folder for newly uploaded lead spreadsheets. Download & Parse – Downloads the file and converts it to structured items (first name, last name, company, LinkedIn URL, email, website). Batch Loop – Processes each row individually. Fetch Activity – Calls Apify LinkedIn Profile Posts (latest post) and records current date for recency checks. Recency Check (LLM) – An OpenAI node returns true/false for “post is from the current year.” Branching • If TRUE → AI Agent (Anthropic) crafts a single, natural reference line based on the recent post. • If FALSE → Apify LinkedIn Profile → AI Agent (Anthropic) crafts a one-liner from profile data (headline/about/current role). Write Back (Google Sheets) – Updates the original sheet by matching on email and writing the personalization field. Notify (Telegram) – Sends a brief completion summary with sheet name and link. Requirements • Google Drive & Google Sheets connections • Apify account + token for LinkedIn scrapers • LLM keys: Anthropic (Claude) and/or OpenAI (you can use one or both) • Telegram bot for notifications (bot token + chat ID) How to use Connect credentials for Google, Apify, OpenAI/Anthropic, and Telegram. Set your folder in the Google Drive Trigger to the one where you’ll drop lead sheets. Map sheet columns to the expected headers (e.g., First Name, Last Name, Company Name for Emails, Person Linkedin Url, Email, Website). Replace placeholders ([put your token here], [put your Telegram Bot Chat ID here]) in the respective nodes. Upload a test spreadsheet to the watched folder and run once to validate the flow. Review results in your sheet (new personalization column) and check Telegram for the completion message. Setup Connect credentials - Google Drive/Sheets, Apify, OpenAI and/or Anthropic, Telegram. Configure the Drive trigger - Select the folder where you’ll upload your lead sheets. Map columns - Ensure your sheet has: First Name, Last Name, Company Name for Emails, Person Linkedin Url, Email, Website. Replace placeholders - In HTTP nodes: Bearer [put your token here]. In Telegram node: [put your Telegram Bot Chat ID here] (Optional) Adjust the recency rule - Current logic checks for current-year posts; change the prompt if you prefer 30-day windows. How to use Upload a test spreadsheet to the watched Drive folder. Execute the workflow once to validate. Open your Google Sheet to see the new personalization column populated. Check Telegram for the completion summary. Customizing this template • Data sources: Add company news, website content, or X/Twitter as fallback signals. • LLM choices: Use only Anthropic or only OpenAI; tweak temperature for tone. • Destinations: Write to a CRM (HubSpot/Salesforce/Airtable) instead of Sheets. • Notifications: Swap Telegram for Slack/Email/Discord. Who it’s for • Sales & SDR teams needing authentic, scalable personalization for cold outreach. • Lead gen agencies enriching spreadsheets with ready-to-use openers. • Marketing & growth teams improving reply rates by referencing real prospect activity. Limitations & compliance • LinkedIn scraping may be rate-limited or blocked; follow platform ToS and local laws. • Costs vary with scraping volume and LLM usage. Need help customizing? Contact me for consulting and support: LinkedIn. An n8n automation workflow template by Mariela Slavenova.

By usamaahmed

🚀 HR Resume Screening Workflow — Smart Hiring on Autopilot 🤖 🎯 Overview: "This workflow builds an AI-powered resume screening system inside n8n. It begins with Gmail and Form triggers that capture incoming resumes, then uploads each file to Google Drive for storage. The resume is downloaded and converted into plain text, where two branches run in parallel: one extracts structured contact details, and the other uses an AI agent to summarize education, job history, and skills while assigning a suitability score. A cleanup step normalizes the data before merging both outputs, and the final candidate record is saved into Google Sheets and Airtable, giving recruiters a centralized dashboard to identify top talent quickly and consistently.” 🔑 Prerequisites: To run this workflow successfully, you’ll need: Gmail OAuth** → to read incoming resumes. Google Drive OAuth** → to upload and download resume files. Google Sheets OAuth** → to save structured candidate records. Airtable Personal Access Token** → for dashboards and record-keeping. OpenAI / OpenRouter API Key** → to run the AI summarizer and evaluator. ⚙️ Setup Instructions: Import the Workflow Clone or import the workflow into your n8n instance. Add Credentials Go to n8n → Credentials and connect Gmail, Google Drive, Google Sheets, Airtable, and OpenRouter/OpenAI. Configure Key Nodes Gmail Trigger → Update filters.q with the job title you are hiring for (e.g., "Senior Software Engineer"). Google Drive Upload → Set the folderId where resumes will be stored. Google Sheets Node → Link to your HR spreadsheet (e.g., “Candidates 2025”). Airtable Node → Select the correct base & table schema for candidate records. Test the Workflow Send a test resume (via email or form). Check Google Sheets & Airtable for structured candidate data. Go Live Enable the workflow. It will now run continuously and process new resumes as they arrive. 📊 End-to-End Workflow Walkthrough: 🟢 Section 1 – Entry & Intake Nodes: 📧 Gmail Trigger → Polls inbox every minute, captures job application emails, and downloads resume attachments (CV0, CV1, …). 🌐 Form Trigger → Alternate entry for resumes submitted via a careers page or job portal. ✅ Quick Understanding: Think of this section as the front desk of recruitment - resumes received either by email or online form, and the system immediately grabs them for processing. 📂 Section 2 – File Management Nodes: ☁️ Upload File (Google Drive) → Saves the incoming resume into a structured Google Drive folder, naming it after the applicant. ⬇️ Download File (Google Drive) → Retrieves the stored resume file for further processing. 🔎 Extract from File → Converts the resume (PDF/DOC) into plain text so the AI and extractors can work with it. ✅ Quick Understanding: This is your digital filing room. Every resume is safely stored, then converted into a readable format for the hiring system. 🤖 Section 3 – AI Processing (Parallel Analysis) Nodes: 🧾 Information Extractor → Pulls structured contact information (candidate name, candidate email and candidate phone number) using regex validation and schema rules. 🤖 AI Agent (LangChain + OpenRouter) → Reads the full CV and outputs: 🎓 Educational Qualifications 💼 Job History 🛠 Skills Set 📊 Candidate Evaluation Score (1–10) 📝 Justification for the score ✅ Quick Understanding: Imagine having two assistants working in parallel, one quickly extracts basic contact info, while the other deeply reviews the CV and gives an evaluation. 🛠️ Section 4 – Data Cleanup & Merging Nodes: ✏️ Edit Fields → Standardizes the AI Agent’s output into a consistent field (output). 🛠 Code (JS Parsing & Cleanup) → Converts the AI’s free-text summary into clean JSON fields (education, jobHistory, skills, score, justification). 🔗 Merge → Combines the structured contact info with the AI’s evaluation into a single candidate record. ✅ Quick Understanding: This is like the data cleaning and reporting team, making sure all details are neat, structured, and merged into one complete candidate profile. 📊 Section 5 – Persistence & Dashboards Nodes: 📑 Google Sheets (Append Row) → Saves candidate details into a Google Sheet for quick team access. 🗄 Airtable (Create Record) → Stores the same structured data into Airtable, enabling dashboards, analytics, and ATS-like tracking. ✅ Quick Understanding: Think of this as your HR dashboard and database. Every candidate record is logged in both Google Sheets and Airtable, ready for filtering, reporting, or further action. 📊 Workflow Overview Table: | Section | Key Roles / Nodes | Model / Service | Purpose | Benefit | | --- | --- | --- | --- | --- | | 📥 Entry & Intake | Gmail Trigger, Form Trigger | Gmail API / Webhook | Capture resumes from email or forms | Resumes collected instantly from multiple sources | | 📂 File Management | Google Drive Upload, Google Drive Download, Extract from File | Google Drive + n8n Extract | Store resumes & convert to plain text | Centralized storage + text extraction for processing | | 🤖 AI Processing | Information Extractor, AI Agent (LangChain + OpenRouter) | Regex + OpenRouter AI {gpt-oss-20b (free)} | Extract contact info + AI CV analysis | Candidate details + score + justification generated automatically | | 🛠 Data Cleanup & Merge | Edit Fields, Code (JS Parsing & Cleanup), Merge | n8n native + Regex Parsing | Standardize and merge outputs | Clean, structured JSON record with all candidate info | | 📊 Persistence Layer | Google Sheets Append Row, Airtable Create Record | Google Sheets + Airtable APIs | Store structured candidate data | HR dashboards & ATS-ready records for easy review and analytics | | 🔄 Execution Flow | All connected | Gmail + Drive + Sheets + Airtable + AI | End-to-end automation | Automated resume → structured record → recruiter dashboards | 📂 Workflow Output Overview: Each candidate’s data is standardized into the following fields: Candidate Name Candidate Email Contact Number Educational Qualifications Job History Skills Set AI Score (1–10) Justification 📌 Example (Google Sheet row): 📊 Benefits of This Workflow at a Glance: ⏱️ Lightning-Fast Screening** → Processes hundreds of resumes in minutes instead of hours. 🤖 AI-Powered Evaluation** → Automatically summarizes candidate education, work history, skills, and gives a suitability score (1–10) with justification. 📂 Centralized Storage** → Every resume is securely saved in Google Drive for easy access and record-keeping. 📊 Data-Ready Outputs** → Structured candidate profiles go straight into Google Sheets and Airtable, ready for dashboards and analytics. ✅ Consistency & Fairness** → Standardized AI scoring ensures every candidate is evaluated on the same criteria, reducing human bias. 🛠️ Flexible Intake** → Works with both Gmail (email applications) and Form submissions (job portals or career pages). 🚀 Recruiter Productivity Boost** → Frees HR teams from manual extraction and data entry, allowing them to focus on interviewing and hiring the best talent. 👉 Practical HR Use Case: “Screen resumes for a Senior Software Engineer role and shortlist top candidates.” Gmail Trigger → Captures incoming job applications with CVs attached. Google Drive → Stores resumes for record-keeping. Extract from File → Converts CVs into plain text. Information Extractor → Pulls candidate name, email, and phone number. AI Agent → Summarizes education, job history, skills, and assigns a suitability score (1–10). Code & Merge → Cleans and combines outputs into a structured candidate profile. Google Sheets → Logs candidate data for quick HR review. Airtable → Builds dashboards to filter and identify top-scoring candidates. ✅ Result: HR instantly sees structured candidate records, filters by score, and focuses interviews on the best talent. An n8n automation workflow template by usamaahmed.

By Krishna Sharma

📄 AI-Powered Document Summarizer & Notifier This workflow monitors a Google Drive folder for new files (Google Docs or PDFs), extracts text, summarizes content with OpenAI, and sends results to Slack or Email. 🔧 How It Works Monitors a Google Drive folder for new files. Detects file type → Google Doc vs PDF. Extracts text (via Google Docs API or PDF extractor). Summarizes & analyzes content using OpenAI. Sends results to Slack and/or Email. 👤 Who Is This For? Business teams → Quick digests of reports, proposals, contracts. Educators / researchers → Summaries of long study materials. Founders / managers → Daily summaries without opening every file. Operations teams → Compliance and documentation tracking. 💡 Use Case / Problem Solved Reading long documents is time-consuming. Sharing key points across teams requires manual effort. Important context (sentiment, action items) is often missed. 👉 This workflow solves it by auto-summarizing documents and notifying teams instantly. ⚙️ What This Workflow Does Monitors Google Drive for new Google Docs or PDFs. Extracts text automatically. Uses OpenAI to generate: Title Summary Key Points Suggested Action Items Language detection Sentiment (positive, neutral, negative) Pushes output to Slack channel and/or Email inbox. 🛠️ Setup Instructions Prerequisites Google Drive (OAuth2) Google Docs (OAuth2) OpenAI API Key Slack (OAuth2) or Gmail (OAuth2) Steps to Configure Connect Google Drive Choose the folder you want to monitor. Set up file type routing Use an IF node to split Docs vs PDFs. For Google Docs Use Google Docs Get → extract text. For PDFs Use Google Drive Download → Extract PDF. Send text to OpenAI Connect to your OpenAI model. Customize the system prompt to generate title, summary, sentiment, etc. Notify Send output to Slack channel or Gmail. Save & activate your workflow. 📌 Notes Adjust OpenAI prompt to suit your context. For large PDFs, consider splitting into smaller chunks. An n8n automation workflow template by Krishna Sharma.

By Nishant Rayan

Create Video with HeyGen and Upload to YouTube Overview This workflow automates the process of creating an AI-generated avatar video using HeyGen and directly uploading it to YouTube. By sending text input via a webhook, the workflow generates a video with a chosen avatar and voice, waits for processing, downloads the completed file, and publishes it to your configured YouTube channel. This template is ideal for automating content creation pipelines, such as daily news updates, explainer videos, or narrated scripts, without manual intervention. Use Case Marketing teams**: Automate explainer or promotional video creation from text input. Content creators**: Generate AI-based avatar videos for YouTube directly from scripts. Organizations**: Streamline video generation for announcements, product updates, or tutorials. Instead of recording and editing videos manually, this template allows you to feed text content into a webhook and have a ready-to-publish video on your YouTube channel within minutes. How It Works Webhook Trigger: The workflow starts when text content and a title are sent to the webhook endpoint. Code Node: Cleans and formats the input text by removing unnecessary newlines and returns it with the title. Set Node: Prepares HeyGen parameters, including API key, avatar ID, voice ID, title, and content. HeyGen API Call: Sends the request to generate a video with the provided avatar and voice. Wait Node: Pauses briefly to allow HeyGen to process the video. Video Status Check: Polls HeyGen to check whether the video has finished processing. Conditional Check: If the video is still processing, it loops back to wait. Once complete, it moves forward. Download Node: Retrieves the generated video file. YouTube Upload Node: Uploads the video to your YouTube channel with the provided title and default settings. Requirements HeyGen API Key**: Required to authenticate with HeyGen’s video generation API. HeyGen Avatar & Voice IDs**: Unique identifiers for the avatar and voice you want to use. YouTube OAuth2 Credentials**: Connected account for video uploads. Setup Instructions Import the Workflow: Download and import this template JSON into your n8n instance. Configure the Webhook: Copy the webhook URL from n8n and use it to send requests with title and content. Example payload: { "title": "Tech News Update", "content": "Today’s top story is about AI advancements in video generation..." } Add HeyGen Credentials: Insert your HeyGen API key in the Set Node under x-api-key. Provide your chosen avatar_id and voice_id from HeyGen. To find your HeyGen avatar_id and voice_id, first retrieve your API key from the HeyGen dashboard. With this key, you can use HeyGen’s API to look up available options: run a GET request to https://api.heygen.com/v2/avatars to see a list of avatars along with their avatar_id, and then run a GET request to https://api.heygen.com/v2/voices to see a list of voices with their voice_id. Once you’ve identified the avatar and voice you want to use, copy their IDs and paste them into the Set HeyGen Parameters node in your n8n workflow. Set Up YouTube Credentials: Connect your YouTube account in n8n using OAuth2. Ensure proper permissions are granted for video uploads. To set up YouTube credentials in n8n, go to the Google Cloud Console, enable YouTube Data API v3, and create an OAuth Client ID (choose Web Application and add the redirect URI: https://<your-n8n-domain>/rest/oauth2-credential/callback). Copy the Client ID and Client Secret, then in n8n create new credentials for YouTube OAuth2 API. Enter the values, authenticate with your Google account to grant upload permissions, and test the connection. Once complete, the YouTube node will be ready to upload videos automatically. Activate the Workflow: Once configured, enable the workflow. Sending a POST request to the webhook with title and content will trigger the full process. Notes You can adjust video dimensions (default: 1280x720) in the HeyGen API request. Processing time may vary depending on script length. The workflow uses a wait-and-poll loop until the video is ready. Default YouTube upload category is Education (28) and region is US. These can be customized in the YouTube node. An n8n automation workflow template by Nishant Rayan.

By Jitesh Dugar

Automated Client Onboarding Workflow This n8n workflow automates the end-to-end client onboarding process: capturing client details, validating emails, assigning tiers, generating welcome packs, creating tasks, notifying teams, archiving records, and sending weekly reports. Who’s It For B2B SaaS companies** onboarding new customers Agencies** handling structured client setups Sales & customer success teams** needing automation Consulting firms** aiming for error-free onboarding ⚙️ How It Works Capture client details through a Webhook (connected to forms). Validate client’s email using Verifi Email. Log onboarding data into Google Sheets. Assign tier logic (Basic/Pro/Enterprise) via Function node. Create a Trello task card with onboarding steps. Generate a personalized Welcome Pack PDF with client details. Send Slack notification to internal team with client details. Download and attach PDF, then send personalized welcome email to the client. Archive structured onboarding data in Airtable. Weekly scheduled report: Collects Airtable onboarding data Processes weekly stats (plans, tiers, counts) Sends onboarding summary via email to the manager 🛠️ How to Set Up Webhook Setup Install & configure credentials: Verifi Email key Google Sheets OAuth2 Airtable OAuth2 Gmail OAuth2 Slack OAuth2 Trello API Optional: Customize the Welcome PDF template (HTML/CSS). Edit tier assignment logic inside the Assign Tier Logic node. Modify Slack & email templates to match your branding. Adjust schedule for weekly reports (default: Monday 9 AM IST). Test with sample payload: { "name": "Jane Doe", "email": "jane@acme.com", "company": "Acme Corp", "plan": "Pro" } 📋 Requirements Self-hosted or Cloud n8n Credentials: Verifi Email, Google Sheets, Airtable, Gmail, Slack, Trello Optional: API for company enrichment ⚠️ Note: The HTML/CSS to PDF node (used for report generation) has a limit of 10 free requests. For production usage, you’ll need an API plan. ⭐ Core Features Email Validation: Blocks fake/spam signups - **Tier Assignment: Auto-classifies clients into Basic/Pro/Enterprise Task Management**: Trello cards for onboarding checklist Welcome PDF Pack**: Branded, client-personalized PDF attachment Slack Notifications**: Real-time internal updates Airtable Archiving**: Permanent record-keeping Weekly Reports**: Automated onboarding summaries for managers 📈 Use Cases & Applications B2B SaaS**: Scale client onboarding without hiring more staff Agencies**: Deliver smooth onboarding experiences Sales Teams**: Reduce delays in CRM entry Customer Success**: Focus on relationship-building instead of admin ✅ Key Benefits Saves 5–6 hours of manual onboarding per client Ensures error-free onboarding with email validation Provides a professional, branded experience Improves collaboration with Slack + Trello integration Scales seamlessly as client volume grows 🔧 Customization Options Modify tier logic (e.g., budget, plan, company size) Customize Slack channel or Trello list for task routing Update PDF branding (logo, theme, styling) Add extra onboarding steps (e.g., Calendly call scheduling) Extend weekly reports (e.g., include ROI or CSM notes) ⚠️ Important Disclaimers For educational & automation purposes Ensure compliance with GDPR/CCPA before storing client data Always test workflow with dummy data before production Workflow Components Webhook Trigger** → Captures client form submissions Verifi Email** → Validates client email Google Sheets** → Logs onboarding entries Code Node** → Assigns tier & priority Trello** → Creates task card for CSM HTML/CSS to PDF** → Generates Welcome Pack PDF Slack** → Notifies team about new client Gmail** → Sends welcome email with PDF Airtable** → Archives full onboarding record Schedule Trigger* + *Report** → Weekly summary to management. An n8n automation workflow template by Jitesh Dugar.

By Don Jayamaha Jr

Access live KuCoin Spot Market data instantly in Telegram! This workflow integrates the KuCoin REST API with Telegram and an optional GPT-4.1-mini formatter, delivering real-time insights like latest prices, 24h stats, order book depth, trades, and candlesticks — all structured into clean Telegram messages. 🔎 How It Works A Telegram Trigger listens for user commands. User Authentication validates the Telegram ID against an allowlist. A SessionId is generated from the chat ID to support memory across turns. The KuCoin AI Agent orchestrates API requests: 24h Stats → /api/v1/market/stats?symbol=BTC-USDT Order Book Depth → /api/v1/market/orderbook/level2_100?symbol=BTC-USDT Latest Price → /api/v1/market/orderbook/level1?symbol=BTC-USDT Best Bid/Ask → /api/v1/market/orderbook/level1?symbol=BTC-USDT Klines (Candles) → /api/v1/market/candles?symbol=BTC-USDT&type=15min&limit=20 Recent Trades → /api/v1/market/histories?symbol=BTC-USDT Average Price (via Ticker) → /api/v1/market/orderbook/level1?symbol=BTC-USDT Utility Tools process results: Calculator → spreads, % changes, averages. Think → reshapes JSON, selects fields, formats outputs. Message Splitter breaks outputs >4000 chars (Telegram limit). Final report is sent back via Telegram SendMessage in human-readable format. ✅ What You Can Do with This Agent Get 24h rolling statistics (open, high, low, close, last, volume). Retrieve full order book depth (20, 100 levels) or best bid/ask. Monitor real-time latest prices with spreads. Analyze candlestick data (OHLCV) across supported intervals. View recent public trades with price, size, side, and time. Use average price proxies from bid/ask + last trade. Receive structured Telegram reports — not raw JSON. 🛠️ Setup Steps Create a Telegram Bot Use @BotFather to create a bot and copy its token. Configure in n8n Import KuCoin AI Agent v1.02.json. Update User Authentication node with your Telegram ID. Add Telegram API credentials (bot token). Add OpenAI API key. (Optional) Add KuCoin API key Deploy & Test Activate the workflow in n8n. Send a query like BTC-USDT to your bot. Instantly receive structured KuCoin Spot Market insights in Telegram. 📤 Output Rules Responses grouped into Price, 24h Stats, Order Book, Klines, Trades. No raw JSON (only human-readable summaries). No financial advice or predictions. Always fetch directly from KuCoin’s official API. 📺 Setup Video Tutorial Watch the full setup guide on YouTube: If you want, I can also update embed links & thumbnails elsewhere to match this. ⚡ Unlock KuCoin Spot Market insights in Telegram — fast, reliable, and API-key free. 🧾 Licensing & Attribution © 2025 Treasurium Capital Limited Company Architecture, prompts, and trade report structure are IP-protected. No unauthorized rebranding permitted. 🔗 For support: Don Jayamaha – LinkedIn. An n8n automation workflow template by Don Jayamaha Jr.

By Davide Boizza

The official ChatGPT connector doesn’t allow you to interact directly with Google Workspace apps from within the app. Let’s see how to overcome this limitation by creating a dedicated MCP server. This workflow acts as a Middleware Control Point (MCP) between Google Workspace services — including Gmail, Drive, Docs, Sheets, Calendar, and Slides — and AI agents like OpenAI’s Agent Builder and the ChatGPT App. It enables these AI assistants to directly interact with Google Workspace tools — from managing emails and calendars to creating and editing documents, spreadsheets, or presentations — through secure automation endpoints, a feature that is not natively supported in the ChatGPT app. Key Advantages ✅ Unified AI–Google Workspace Integration Allows large language models (LLMs) to manage Gmail, Drive, Docs, Sheets, Calendar, and Slides directly, enabling AI-driven workflows like email automation, document creation, meeting scheduling, and data analysis. ✅ Full Control Across Google Apps Supports key actions across multiple services: Gmail: Read, send, reply, search, and draft emails. Drive: Search, upload, organize, and share files. Docs: Create, edit, and retrieve Google Docs. Sheets: Create or update spreadsheets, analyze data, and read cell values. Calendar: List, create, update, or delete events. Slides: Generate or modify presentations. ✅ Plug-and-Play with OpenAI Agent Builder & ChatGPT Easily connect to MCP-compatible AI platforms like Claude Desktop or OpenAI Agent Builder, with minimal configuration. ✅ Scalable and Extensible The modular structure allows you to expand to additional Google APIs or custom automations (e.g., CRM syncing, sentiment analysis, or reporting). ✅ No-Code/Low-Code Configuration Fully built in n8n, allowing easy customization and maintenance without deep programming skills. How It Works MCP Trigger: The “MCP Google Workspace Trigger” node acts as the server endpoint, waiting for incoming requests from an AI application. Tool Execution: When the AI needs to interact with a Google app (e.g., Gmail or Drive), it sends a command to this trigger. The workflow routes the request to the appropriate tool node. Available Actions (Examples): Gmail: Get, send, reply, search, or draft messages. Drive: Upload or retrieve files. Docs: Create or edit documents. Sheets: Read or update cell data. Calendar: Manage events. Slides: Generate or modify presentations. Data Return: The result (email content, document link, file metadata, event details, etc.) is returned to the MCP server and then to the AI, which can use it to continue the workflow or conversation. Setup Steps Configure Google Workspace Credentials in n8n: Authenticate each Google service (Gmail, Drive, Docs, Sheets, Calendar, Slides) via OAuth2 using the correct account credentials. Activate the Workflow: The workflow must be active in n8n. The MCP Trigger node provides a unique URL that serves as the server endpoint. Connect to an AI Application (Choose one method): ChatGPT App: Open the ChatGPT App (Plus plan required). Enable Dev Mode → Add new connector. Add an “MCP Server” as a tool and provide the URL from the “MCP Google Workspace Trigger” node. OpenAI Agent Builder: Visit OpenAI Agent Builder. Create a new workflow or agent. Add an “MCP Server” as a tool and provide the MCP URL from n8n. Once connected, the AI can intelligently manage Google Workspace tasks based on natural language requests such as: > “Schedule a meeting with Sarah tomorrow at 3 PM,” > “Create a new Google Doc titled ‘Marketing Plan’ and share it with the team,” > or “Find the latest report in Drive and summarize it.” Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By yusan25c

How It Works This template is a workflow that registers Jira tickets to Pinecone. By combining it with the Automated Jira Ticket Responses with GPT-4 and Pinecone Knowledge Base template, you can continuously improve the quality of automated responses in Jira. Prerequisites A Jira account and credentials (API key and email address) A Pinecone account and credentials (API key and environment settings) OpenAI credentials (API key) Setup Instructions Jira Credentials Register your Jira credentials (API key and email address) in n8n. Vector Database Setup (Pinecone) Register your Pinecone credentials (API key and environment variables) in n8n. AI Node Configure the OpenAI node with your credentials (API key). Step by Step Scheduled Trigger The workflow runs at regular intervals according to the schedule set in the Scheduled Trigger node. Jira Trigger (Completed Tickets) Retrieves the summary, description, and comments of completed Jira tickets. Register to Pinecone Converts the retrieved ticket information into vectors and registers them in Pinecone. Notes Configure the Scheduled Trigger interval carefully to avoid exceeding API rate limits. Further Reference For a detailed walkthrough (in Japanese), see this article: 👉 Automating knowledge registration to Pinecone with n8n (Qiita) You can find the template file on GitHub here: 👉 Template File on GitHub. An n8n automation workflow template by yusan25c.