Workflow Templates

How it works: Daily Trigger: Every morning at 8 AM, the workflow is automatically triggered. Fetch Trending Topics: The workflow collects trending topics from external sources, such as news RSS feeds and Reddit popular posts. These trends are merged and summarized to provide up-to-date context for content generation. Read Active Campaigns: The workflow reads all rows from the “Active Campaigns” Google Sheet, but only processes campaigns with a status of "active" to avoid generating content for paused or inactive campaigns. Enrich Campaigns with Trends: Each active campaign is enriched with the latest trending topics, so the generated content can reference current events or popular themes. AI Content Generation: For each enriched campaign, Groq AI generates: An engaging post caption tailored to the platform and target audience Creative direction with visual suggestions Relevant hashtags (5-10) Best posting time recommendation for the platform Quality Scoring: The workflow calculates a quality score for each generated content idea, considering factors like caption length, hashtag count, and creative direction. Append to Google Sheets: The generated content ideas, along with their quality scores and other details, are appended to the “Daily Content Plan” Google Sheet for record-keeping and team collaboration. Schedule in Google Calendar: For each campaign, an event is created in Google Calendar with the content details and recommended posting time, ensuring the team is reminded to review or publish the content. Daily Email Summary (Optional): At the end of the process, a summary email can be sent to the team, including statistics such as the number of campaigns processed, average quality score, and a platform breakdown. Set up steps: Prepare Your Google Sheets: Create a sheet named “Active Campaigns” with columns: Project Name, Theme, Target Audience, Platform, and Status (to mark campaigns as active/inactive). Create another sheet named “Daily Content Plan” with columns for Project Name, Date, Platform, Caption, Creative Direction, Hashtags, and any other details you want to track. Connect Google Services to n8n: In n8n, set up and authenticate your Google Sheets and Google Calendar credentials. You can find authentication information in the n8n documentation for Google credentials. Add a Cron Node: Drag in a Cron node and set it to trigger every day at 8:00 AM. Read Campaigns from Google Sheets: Add a Google Sheets node. Set the operation to “Read Rows” and select your “Active Campaigns” sheet. (Optional) Use a Filter or IF node to process only rows where Status is “active”. (Optional) Fetch Trending Topics: If you want to enrich your content with trending topics, add nodes to fetch data from RSS feeds, Reddit, or other sources. Process Each Campaign: Use a SplitInBatches node to process each campaign row individually. Generate Content Ideas with Groq AI: Add a Groq AI node (or OpenAI node if Groq is not available). Configure the prompt to generate a content idea using the campaign’s theme, target audience, and platform. You can reference fields from the Google Sheets node using expressions like $("Google Sheets").item.json['Theme']. Append Results to “Daily Content Plan”: Add another Google Sheets node. Set the operation to “Append” and select your “Daily Content Plan” sheet. Map the generated content fields to the appropriate columns. Schedule Events in Google Calendar: Add a Google Calendar node. Set the operation to “Create Event”. Use the project name and content idea for the event title and description, and set the event time as needed. (Optional) Send a Daily Summary Email: Add an Email node to send a summary of the day’s content plan to your team. Test the Workflow: Run the workflow manually to ensure all steps work as expected. Check that new content ideas appear in the “Daily Content Plan” sheet and that events are created in Google Calendar. Activate the Workflow: Once you’ve confirmed everything works, activate the workflow so it runs automatically every morning.

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primary_keywords, seo_strength_score, keyword_density_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors** → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection** → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report** → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization** → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs** → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo** for intelligent web scraping OpenAI GPT-4.1-mini** for keyword and SEO analysis Google Sheets** for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

This automation workflow transforms Meta advertising data into executive ready presentation decks, eliminating manual report creation while ensuring stakeholders receive consistent performance insights. It generates professional Google Slides presentations from your ad campaigns and delivers them automatically via email to designated recipients. By combining scheduled data extraction with AI-powered analysis and automated presentation building, you'll receive polished, actionable reports that facilitate strategic advertising decisions and client communication Key Features: Scheduled automated summary deck generation (daily, weekly, or monthly) AI powered data analysis using advanced language models Intelligent presentation generation with actionable recommendations Direct email delivery of formatted summary decks Prerequisites: GoMarble MCP account and API access Anthropic account Google Slides, Google Drive & Gmail accounts n8n instance (cloud or self-hosted) Configuration Time: ~15-20 minutes Step By Step Setup: 1. Connect GoMarble MCP to n8n Follow the integration guide: GoMarble MCP Setup Configure your Meta Ads account credentials in GoMarble platform 2. Configure the Schedule Trigger 3.Customize the Ad Account Settings. Update the account name to match your ad account name. 4. Customise the Report Prompt (Although the workflow includes a pre configured template report prompt) Define specific metrics and KPIs to track Set analysis parameters and report format preferences 5. Set up AI Agent Configuration Configure Anthropic Claude model with your API credentials Connect the GoMarble MCP tools for Meta advertising data 6. Configure Google Services Integration Set up Google Slides OAuth2 API for presentation creation Configure Google Drive OAuth2 API for file management Link Gmail OAuth2 for automated email delivery 7. Customize Email Delivery Set recipient email addresses for stakeholders Customize email subject line and message content Advanced Configuration Modify report prompt to include specific metrics and KPIs Adjust slide content structure (5-slide format: Executive Snapshot, Channel KPIs, Top Campaigns, Under-performers, Action Recommendations) What You'll Get Automated Presentation Creation: Weekly Google Slides decks generated without manual intervention Professional Ads Analysis: Executive-ready performance summaries with key metrics and insights Structured Intelligence: Consistent 5-slide format covering spend, ROAS, campaign performance, and strategic recommendations Direct Stakeholder Delivery: Presentations automatically emailed as attachments to specified recipients Data-Driven Insights: AI-powered analysis of campaign performance with actionable next steps Scalable Reporting: Easy to modify timing, recipients, or content structure as business needs evolve Perfect for marketing teams, agencies, and business owners who need regular Meta advertising performance updates delivered professionally without manual report creation.

This automated n8n workflow transforms uploaded radiology images into professional, patient-friendly PDF reports. It uses AI-powered image analysis to interpret medical scans, simplify technical terms, and produce clear explanations. The reports are formatted, converted to PDF, stored in a database, and sent directly to patients via email, ensuring both accuracy and accessibility. 🏥 Workflow Overview: Simple Process Flow: Upload Image → 2. AI Analysis → 3. Generate Report → 4. Send to Patient 🔧 How It Works: Webhook Trigger - Receives image uploads via POST request Extract Image Data - Processes patient info and image data AI Image Analysis - Uses GPT-4 Vision to analyze the radiology image Process Analysis - Structures the AI response into readable sections Generate PDF Report - Creates a beautiful HTML report Convert to PDF - Converts HTML to downloadable PDF Save to Database - Logs all reports in Google Sheets Email Patient - Sends the report via email Return Response - Confirms successful processing 📊 Key Features: AI-Powered Analysis** using GPT-4 Vision Patient-Friendly Language** (no medical jargon) Professional PDF Reports** with clear sections Email Delivery** with report attachment Database Logging** for record keeping Simple Webhook Interface** for easy integration 🚀 Usage Example: Send POST request to webhook with: { "patient_name": "John Smith", "patient_id": "P12345", "scan_type": "X-Ray", "body_part": "Chest", "image_url": "https://example.com/xray.jpg", "doctor_name": "Dr. Johnson", "patient_email": "john@email.com" } ⚙️ Required Setup: OpenAI API - For GPT-4 Vision image analysis PDF Conversion Service - HTML to PDF converter Gmail Account - For sending reports Google Sheets - For logging reports Replace YOUR_REPORTS_SHEET_ID with your actual sheet ID Want a tailored workflow for your business? Our experts can craft it quickly Contact our team

Description Add your approved SEO Q&A pairs to a Google Sheet, activate the workflow, and share the chat URL with your team or clients. The chatbot reads your entire knowledge base on every question and answers strictly from your own content — never from outside sources. Every conversation is automatically logged to a second sheet so you can track common questions and improve your knowledge base over time. Built for SEO agencies, consultants, and marketing teams who want a branded AI assistant without hallucinated or off-brand answers. What This Workflow Does Reads your knowledge base live** — Pulls all Q&A rows from your Google Sheet on every question so answers always reflect your latest approved content Answers strictly from your content** — GPT-4o-mini is instructed to never use outside knowledge, keeping every response on-brand and accurate Delivers an honest fallback** — If a question is not covered in your sheet, the bot tells the user directly and points them to your support team instead of guessing Maintains conversation memory** — Users can ask follow-up questions naturally without repeating context, just like a real chat Logs every exchange automatically** — Appends each session ID, timestamp, question, and answer to a Chat Log sheet for analytics and gap identification Returns the reply in real time** — The answer is sent back to the chat interface instantly at the same time as it is being logged Setup Requirements Tools Needed n8n instance (self-hosted or cloud) OpenAI account with GPT-4o-mini API access Google account with two Google Sheets (one for the knowledge base, one for the chat log) Credentials Required OpenAI API key Google Sheets OAuth2 (used in two steps — read and log) > ⚠️ Google Sheets OAuth2 appears in 2 steps — connect it in both 3. Google Sheets — Read Knowledge Base and 9. Google Sheets — Log Chat Estimated Setup Time: 15–20 minutes Step-by-Step Setup Import the workflow — Open n8n → Workflows → Import from JSON → paste the workflow JSON → click Import Create your Knowledge Base sheet — Open Google Sheets → create a new sheet → add a tab named exactly SEO FAQ → add these four column headers in row 1: Question, Answer, Category, Last Updated → fill in at least 5–10 Q&A rows before testing Create your Chat Log sheet — In the same Google Sheet or a separate one → add a tab named exactly Chat Log → add these four column headers in row 1: Session ID, Timestamp, User Question, Bot Answer Fill in Config Values — Open node 2. Set — Config Values → replace all placeholders: | Field | What to enter | |---|---| | YOUR_KNOWLEDGE_BASE_SHEET_ID | The ID from your Knowledge Base sheet URL (the string between /d/ and /edit) | | SEO FAQ | Leave as-is, or change to match your tab name exactly | | YOUR_CHAT_LOG_SHEET_ID | The ID from your Chat Log sheet URL (same method) | | Chat Log | Leave as-is, or change to match your log tab name exactly | | YOUR COMPANY NAME | Your agency or business name | | botPersona | Edit the persona description to match your brand voice | Connect Google Sheets for reading — Open node 3. Google Sheets — Read Knowledge Base → click the credential dropdown → add Google Sheets OAuth2 → sign in with your Google account → authorize access Connect OpenAI — Open node 6. OpenAI — GPT-4o-mini Model → click the credential dropdown → add your OpenAI API key → test the connection Connect Google Sheets for logging — Open node 9. Google Sheets — Log Chat → click the credential dropdown → select the same Google Sheets OAuth2 credential you connected in step 5 Activate the workflow — Toggle the workflow to Active → click on node 1. Chat Message Received → copy the Chat URL shown → share this URL with your team or embed it in your site How It Works (Step by Step) Step 1 — Chat Trigger: Receive User Question This step creates a public chat interface at a shareable URL. Every time a user types a message and hits send, that message is passed to the next step automatically. No credentials are needed for this step — it works as soon as the workflow is active. Step 2 — Set: Config Values Your knowledge base Sheet ID, log Sheet ID, tab names, company name, and bot persona are stored here as named variables. A unique session ID is also generated automatically for each new conversation so chats can be tracked individually in the log. Step 3 — Google Sheets: Read Knowledge Base The full contents of your SEO FAQ tab are read from Google Sheets every time a question comes in. This means you can add, edit, or remove Q&A rows at any time and the chatbot will reflect your changes immediately — no redeployment needed. Step 4 — Code: Build Knowledge Base Text All the rows from your sheet are formatted into a numbered Q&A text block grouped by category. The user's question is also pulled from the chat trigger here. If the sheet is empty, a clear fallback message is used instead of crashing the workflow. Everything is assembled into one clean package for the AI step. Step 5 — AI Agent: SEO Consultant GPT-4o-mini receives your bot persona, the full knowledge base text, and the user's question. It searches the knowledge base for a matching answer and responds in plain, friendly language. If the question is not covered, it returns exactly: "I do not have information about this topic in my current knowledge base. Please contact [your company name] support directly for help with this." Answers are kept under 150 words and contain no markdown formatting. Step 6 — OpenAI: GPT-4o-mini Model This is the language model powering the AI step. It runs at temperature 0.3 for factual, consistent answers and is capped at 400 tokens to keep responses concise and costs low per conversation. Step 7 — Memory: Conversation Buffer This step stores the conversation history for the current session. It allows users to ask follow-up questions naturally — for example, asking "Can you explain that in more detail?" — without the bot losing context from earlier in the same chat. Step 8 — Set: Prepare Log Fields The bot's answer, the user's original question, the session ID, and the timestamp are all assembled here into a clean set of fields ready for logging and for returning to the chat interface. Step 9 — Google Sheets: Log Chat A new row is appended to your Chat Log tab with four fields: session ID, timestamp, user question, and bot answer. This runs at the same time as the reply is sent back to the user. Over time this log shows you which questions are being asked most and where your knowledge base has gaps. Step 10 — Set: Return Answer to Chat The bot answer is sent back to the chat interface so the user sees the reply immediately. This step runs simultaneously with the logging step so there is no delay in the response. The final result: the user sees a clean, on-brand answer in the chat window within seconds, and the exchange is permanently recorded in your Google Sheet. Key Features ✅ Live knowledge base sync — Edit your Google Sheet and the chatbot reflects your changes on the very next question — no redeployment ✅ Hallucination-free by design — GPT-4o-mini is explicitly instructed to answer only from your sheet, never from its own training data ✅ Honest fallback built in — Unknown questions get a clear, branded fallback message instead of a confabulated answer that damages trust ✅ Multi-turn conversation support — Conversation memory lets users ask follow-up questions in the same session without losing context ✅ Automatic chat logging — Every exchange is saved to Google Sheets with session ID and timestamp — no manual export needed ✅ Category-organized knowledge base — Q&A rows include a Category column so the AI receives structured, scannable content per topic ✅ Zero-cost trigger — The chat interface is built into n8n with no third-party chat platform required ✅ Token-efficient responses — Answers are capped at 400 tokens and 150 words, keeping GPT costs predictable even at high chat volume Customisation Options Expand the knowledge base to other topics — In node 2. Set — Config Values, edit the botPersona field to change the bot's scope from SEO-only to any topic your team needs (e.g. HR policies, product FAQs, onboarding guides) — then populate your sheet accordingly. Increase answer length for complex topics — In node 6. OpenAI — GPT-4o-mini Model, raise maxTokens from 400 to 700 and change the 150-word limit in the prompt inside node 5. AI Agent — SEO Consultant to allow longer, more detailed answers for technical subjects. Use two separate Google Sheets — If you want your knowledge base and chat log in different files, paste different Sheet IDs into knowledgeBaseSheetId and logSheetId in node 2. Set — Config Values — the workflow handles both independently. Add a Slack notification for unanswered questions — After node 9. Google Sheets — Log Chat, add a Slack node that checks if the bot answer contains the fallback phrase and posts an alert to a #kb-gaps channel so your team knows which topics to add next. Track question frequency in sheets — Add a Google Sheets step after logging that searches the Chat Log for the same question and increments a count in a separate Frequency tab — helping you prioritize which knowledge base gaps to fill first. Troubleshooting Chat not responding after activation: Make sure the workflow is toggled to Active — inactive workflows do not respond to chat messages Click on node 1. Chat Message Received and confirm the Chat URL is visible — copy it fresh after activating Send a test message and check the n8n execution log for which step failed OpenAI credential not working: Confirm the API key is connected in node 6. OpenAI — GPT-4o-mini Model specifically Check that your OpenAI account has available credits — a depleted account silently fails Verify the key has access to gpt-4o-mini — some restricted keys block specific models Knowledge base returning empty or wrong answers: Open node 3. Google Sheets — Read Knowledge Base and confirm the Google Sheets OAuth2 credential is connected Check that knowledgeBaseSheetId in node 2. Set — Config Values exactly matches the ID in your Google Sheet URL Confirm the tab is named SEO FAQ exactly — spelling and capitalization must match knowledgeBaseSheetName Chat Log not saving rows: Open node 9. Google Sheets — Log Chat and confirm the Google Sheets OAuth2 credential is connected (this is a separate connection from the read step) Check that logSheetId in node 2. Set — Config Values is correct and the tab is named Chat Log exactly Confirm your Chat Log sheet has the four column headers in row 1: Session ID, Timestamp, User Question, Bot Answer Bot answering from outside the knowledge base: The prompt in node 5. AI Agent — SEO Consultant explicitly restricts answers to the knowledge base — if the bot strays, check that the full prompt text is intact and has not been accidentally edited Lower the temperature in node 6. OpenAI — GPT-4o-mini Model from 0.3 to 0.1 for stricter, more literal responses Support Need help setting this up or want a custom version built for your team or agency? 📧 Email:info@incrementors.com 🌐 Website: https://www.incrementors.com/

📌 Title (SEO-Friendly) Automate Facebook Messenger orders to Google Sheets and Google Calendar Introduction This workflow automates Facebook Messenger order management by connecting your Facebook Page with Google Sheets and Google Calendar. It’s designed to help small businesses save time, reduce errors, and streamline order-taking. Every time a customer messages your page, they receive a structured order form, their responses are parsed, and the details are saved directly to Google Sheets. The same workflow also creates a Google Calendar event, ensuring you never miss a delivery or pickup schedule. Who’s It For Small businesses** selling products through Facebook Messenger. Entrepreneurs** who want to eliminate manual order-taking. Teams** that need a centralized order tracker (Google Sheets) and automatic reminders (Google Calendar). How It Works Listen to incoming messages on Facebook Messenger. Send an automated greeting and order form to the customer. Parse their responses (items, quantity, payment method, etc.). Save order details into Google Sheets for easy tracking. Create a matching Google Calendar event for the order date/time. Send a confirmation message and an optional upsell suggestion. Requirements Facebook Page** with Messenger enabled. Meta for Developers account** to create a Facebook App and generate a Page Access Token. Google Sheets** account with a spreadsheet containing the following columns: Date, Customer Name, Order Details, Payment Method, Order Status, Notes Google Calendar** account for order scheduling. n8n instance** (cloud or self-hosted). 💡 Security Best Practice: Store your Page Access Token and Google credentials in n8n Credentials (not hardcoded in nodes). Setup Instructions 1. Facebook Messenger Connection Go to Meta for Developers. Create a Messenger App and generate a Page Access Token. Copy the Webhook URL from your n8n Webhook Trigger node. Add the webhook URL and verify it in your Facebook Page settings. 2. Google Sheets Setup Create a new spreadsheet named Messenger Orders. Add columns: Date, Customer Name, Order Details, Payment Method, Order Status, Notes. Share the sheet with the Google account connected in n8n. 3. Google Calendar Setup Connect your Google Calendar credentials in n8n. Select the calendar where orders should be added. 4. Import & Configure Workflow Download this workflow template. Replace placeholders ({{YOUR_PAGE_ACCESS_TOKEN}}, {{YOUR_GOOGLE_SHEET_ID}}, etc.). Test by sending a message to your Facebook Page. Customization Personalize messages** in the Messenger node (greeting, upsell suggestions). Add extra fields such as delivery address or contact number to both the form and the Google Sheet. Extend the workflow by adding Telegram, Email, or SMS notifications for customers or staff. Use Filter nodes to route VIP orders or high-value purchases to a separate workflow. ⚡ Final Flow: Facebook Messenger → Order Form → Google Sheets → Google Calendar → Customer Confirmation 💬 Call to Action: Clone this workflow, connect your accounts, and start automating your Messenger orders in minutes!

This n8n template demonstrates how to capture website leads via a webhook, validate the data, optionally enrich it, store it in your CRM (HubSpot) or a simple Google Sheet, and instantly notify your team via email and Slack. This is ideal for agencies, freelancers, SaaS founders, and small sales teams who want every lead recorded and followed up automatically within seconds. Good to know The workflow supports two storage options: HubSpot or Google Sheets (choose one branch). Enrichment (Clearbit/Hunter) is optional and can be disabled with a single toggle/IF branch. Consider adding anti-spam (honeypot/captcha) if your form gets abused. How it works Webhook receives the lead Your website form sends a POST request to the Webhook URL with lead fields (name, email, message, etc.). Validation & normalization The workflow trims and normalizes fields (like lowercasing email) and checks required fields. If invalid, it returns a Optional enrichment (Clearbit/Hunter) If enrichment is enabled, the workflow calls an enrichment API and merges results into the lead object (industry, company size, domain, etc.). If enrichment fails, the workflow continues (doesn’t block lead capture). Save lead to CRM (Choose one) HubSpot branch**: find contact by email → create or update the contact record Google Sheets branch**: lookup row by email → update if found → otherwise append a new row Instant notifications Posts a Slack message to a channel, optionally including a CRM/Sheet link Success response to the website Returns a #### How to use? Import the workflow into n8n. Configure the Webhook node and copy the production URL into your website form submit action. Choose your storage path: Enable HubSpot nodes OR Enable Google Sheets nodes Add credentials: Slack credential (Optional) HubSpot / Google Sheets (Optional) Clearbit/Hunter keys in the HTTP Request node Send a test lead from your website and confirm: Lead saved correctly Email received Slack notification posted Website receives a 200 response Requirements An n8n instance (cloud or self-hosted) One of: HubSpot account (for CRM storage), or Google account + Google Sheets (for spreadsheet storage) Slack workspace + Slack credentials Optional: Clearbit/Hunter account for enrichment

How it works This workflow sources news from news websites. The information is then passed to an LLM, which processes the article's content. An editor approves or rejects the article. If accepted, the article is first published on the WordPress site and then on the LinkedIn page. Setup Instructions 1. Credentials You'll need to add credentials for the following services in your n8n instance: News API**: A credential for your chosen news provider. LLM**: Your API key for the LLM you want to use. Google OAuth**: For both Gmail and Google Sheets. WordPress OAuth2**: To publish articles via the API. See the WordPress Developer Docs. LinkedIn OAuth2**: To share the post on a company page. 2. Node Configuration Don't forget to: Fetch News (HTTP Request)**: Set the query parameters (keywords, language, etc.) for your news source. Basic LLM Chain: Review and **customize the prompt to match your desired tone, language, and style. Approval request (Gmail)**: Set your email address in the Send To field. HTTP Request WP - Push article**: Replace <site_Id> in the URL with your WordPress Site ID. getImageId (Code Node)**: Update the array with your image IDs from the WordPress Media Library. Create a post (LinkedIn)**: Enter your LinkedIn Organization ID. Append row in sheet (Google Sheets)**: Select your Google Sheet file and the target sheet. All Email Nodes**: Make sure the Send To field is your email.

How it works This workflow automates the handling of new lead responses received in Gmail. It captures emails with a specific label, analyzes the message using AI to determine sentiment, intent, urgency, next action, and priority, and then decides whether follow-up is needed. If required, it creates tasks in HubSpot, notifies the sales team via Slack, and logs all details into Google Sheets for tracking. Step-by-step Trigger on New Lead Email Workflow starts whenever a new email with a defined Gmail label arrives. Captures the sender’s email, subject, message snippet, and timestamp. Normalize Email Data Standardizes Gmail fields into structured values: leadEmail (sender’s address) subject (email subject) message (email content snippet) source (Gmail) receivedAt (timestamp) AI-Powered Lead Analysis Uses OpenAI to analyze the lead’s message. Extracts: Sentiment (Positive / Neutral / Negative) Intent (Interested, Not Interested, Needs Info, Ready to Buy, Objection) Urgency (High / Medium / Low) Next Action (Call, Email, Demo, Quote, No Action) Summary (1–2 sentence description) Priority (Hot / Warm / Cold) Parsed results are merged with the original email data. Flags are added: needsFollowUp (true/false) isHighPriority (true/false) Decision: Needs Follow-Up? If AI suggests a follow-up action, the workflow continues. Otherwise, the process stops here. Create HubSpot Task Automatically creates a HubSpot CRM task for the sales team. Task includes email subject, body, and lead details. Notify Sales Team on Slack Sends a formatted message to Slack with key lead insights: Summary Lead email Priority Urgency Date of analysis Log Lead Data to Google Sheets Appends structured data to Google Sheets for record-keeping. Stores all fields: Email, Date, Subject, Message, Sentiment, Intent, Urgency, Next Action, Summary, and Priority. Why use this? Automates lead triage directly from Gmail. Saves time by using AI-powered analysis instead of manual review. Ensures no potential lead is missed by logging into Google Sheets. Provides instant sales team alerts on high-priority leads. Integrates seamlessly with HubSpot CRM for structured follow-up. Keeps your sales pipeline efficient, organized, and proactive.

Who’s it for Women creators, homemakers-turned-entrepreneurs, and feminine lifestyle brands who want a graceful, low-lift way to keep an eye on competitor content and spark weekly ideas. What it does On a weekly schedule, this workflow crawls your competitor URLs with Firecrawl (HTTP Request), summarizes each page with OpenAI, brainstorms carousel/pin ideas with Gemini, appends results to Google Sheets (Date, URL, Title, Summary, Ideas), and sends you a single email digest (optional Telegram alert). It includes basic error notifications and a setup-friendly config node. Requirements HTTP credentials** for Firecrawl, OpenAI, and Gemini (no keys in nodes) Google Sheets** OAuth credential A Sheets document with a target sheet/range (e.g., Digest!A:F) (Optional) Telegram bot + chat ID How to set up Open Set: Configuration (edit me) and fill: competitorUrls (one per line), sheetsSpreadsheetId, sheetsRange, ownerEmail, emailTo, geminiModel, openaiModel Attach credentials to the HTTP and Sheets nodes. Test by switching Cron to Every minute, then revert to weekly. How it works Cron → Firecrawl (per URL) → Normalize → OpenAI (summary) + Gemini (ideas) → Merge → Compile Row → Google Sheets append → Build one digest → Email (+ optional Telegram). How to customize Add/remove competitors or change the weekly send time. Tweak the OpenAI/Gemini prompts for your brand voice. Expand columns in Sheets (e.g., category, tone, CTA). Swap email/Telegram for Slack/Notion, or add persistent logs.

Forecast sales trends and generate reports with Stripe, Sheets, and Gemini AI Who is this for Revenue operations teams, SaaS growth managers, and sales directors who need automated weekly insights from their Stripe payment data. Perfect for small to medium businesses tracking subscription revenue, one-time charges, and refund patterns without manual spreadsheet work. How it works Every Monday morning, the workflow pulls the previous week's charges, subscriptions, and refunds from Stripe's API. It merges this fresh data with historical sales records stored in Google Sheets, then calculates key metrics like week-over-week growth, moving averages, and MRR estimates. Google Gemini AI analyzes the compiled data to identify trends, predict next week's performance, and flag unusual revenue patterns. When significant changes are detected (20%+ variance), the system triggers targeted alerts through a separate Slack channel. All insights get logged to a Google Sheets history for tracking, while a comprehensive dashboard page updates automatically in Notion. The weekly summary posts to your main sales Slack channel, and executives receive detailed email reports with strategic recommendations. How to set up Configure Stripe API credentials with read access to charges, subscriptions, and refunds. Set up Google Sheets OAuth for both reading historical data and writing analysis logs. Create a Notion integration with page update permissions for your sales dashboard. Add Slack OAuth credentials for posting to your chosen sales and alerts channels. Configure Gmail SMTP for executive email delivery. Update the Configuration Settings node with your specific IDs, channels, and email addresses. Requirements Stripe account with API access Google Sheets with historical sales data Notion workspace for dashboard Slack workspace with posting permissions Gmail account for executive reports Google Gemini API access How to customize Adjust the anomaly detection threshold in the Calculate Trends code node (currently 50% variance triggers alerts). Modify the Slack message templates, email formatting, or add additional metrics to the Notion dashboard. Change the schedule trigger from weekly to daily or monthly based on your reporting needs.

Scheduled Backup Automation – Mailgun & Box This workflow automatically schedules, packages, and uploads backups of your databases, files, or configuration exports to Box cloud storage, then sends a completion email via Mailgun. It is ideal for small-to-medium businesses or solo developers who want hands-off, verifiable backups without writing custom scripts. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n.cloud) Box account with a folder dedicated to backups Mailgun account & verified domain Access to the target database/server you intend to back up Basic knowledge of environment variables to store secrets Required Credentials Box OAuth2** – For uploading the backup file(s) Mailgun API Key** – For sending backup status notifications (Optional) Database Credentials** – Only if the backup includes a DB dump triggered from inside n8n Specific Setup Requirements | Variable | Example | Purpose | |-------------------------|------------------------------------------|---------------------------------------| | BOX_FOLDER_ID | 1234567890 | ID of the Box folder that stores backups | | MAILGUN_DOMAIN | mg.example.com | Mailgun domain used for sending email | | MAILGUN_FROM | Backups <backup@mg.example.com> | “From” address in status emails | | NOTIFY_EMAIL | admin@example.com | Recipient of backup status emails | How it works This workflow automatically schedules, packages, and uploads backups of your databases, files, or configuration exports to Box cloud storage, then sends a completion email via Mailgun. It is ideal for small-to-medium businesses or solo developers who want hands-off, verifiable backups without writing custom scripts. Key Steps: Webhook (Scheduler Trigger)**: Triggers the workflow on a CRON schedule or external call. Code (DB/File Dump)**: Executes bash or Node.js commands to create a tar/zip or SQL dump. Move Binary Data**: Converts the created file into n8n binary format. Set**: Attaches metadata (timestamp, file name). Split In Batches* *(optional): Splits multiple backup files for sequential uploads. Box Node**: Uploads each backup file into the specified Box folder. HTTP Request (Verify Upload)**: Calls Box API to confirm upload success. If**: Branches on success vs failure. Mailgun Node**: Sends confirmation or error report email. Sticky Notes**: Provide inline documentation inside the workflow canvas. Set up steps Setup Time: 15-20 minutes Clone or import the workflow JSON into your n8n instance. Create credentials: Box OAuth2: paste Client ID, Client Secret, perform OAuth handshake. Mailgun API: add Private API key and domain. Update environment variables (BOX_FOLDER_ID, MAILGUN_DOMAIN, etc.) or edit the relevant Set node. Modify the Code node to run your specific backup command, e.g.: pg_dump -U $DB_USER -h $DB_HOST $DB_NAME > /tmp/db_backup.sql tar -czf /tmp/full_backup_{{new Date().toISOString()}}.tar.gz /etc/nginx /var/www /tmp/db_backup.sql Set the CRON schedule inside the Webhook node (or replace with a Cron node) to your desired frequency (daily, weekly, etc.). Execute once manually to verify the Box upload and email notification. Enable the workflow. Node Descriptions Core Workflow Nodes: Webhook / Cron** – Acts as the time-based trigger for backups. Code** – Creates the actual backup archive (tar, zip, SQL dump). Move Binary Data** – Moves the generated file into binary property. Set** – Adds filename and timestamp metadata for Box. Split In Batches** – Handles multiple files when necessary. Box** – Uploads the backup file to Box. HTTP Request** – Optional re-check to ensure the file exists in Box. If** – Routes the flow based on success or error. Mailgun** – Sends success/failure notifications. Sticky Note** – Explains credential handling and customization points. Data Flow: Webhook/Cron → Code → Move Binary Data → Set → Split In Batches → Box → HTTP Request → If → Mailgun Customization Examples Add Retention Policy (Auto-delete old backups) // In a Code node before upload const retentionDays = 30; const cutoff = Date.now() - retentionDays * 246060*1000; items = items.filter(item => { return item.json.modifiedAt > cutoff; // keep only recent files }); return items; Parallel Upload to S3 // Duplicate the Box node, replace with AWS S3 node // Use Merge node to combine results before the HTTP Request verification Data Output Format The workflow outputs structured JSON data: { "fileName": "full_backup_2023-10-31T00-00-00Z.tar.gz", "boxFileId": "9876543210", "uploadStatus": "success", "timestamp": "2023-10-31T00:05:12Z", "emailNotification": "sent" } Troubleshooting Common Issues “Invalid Box Folder ID” – Verify BOX_FOLDER_ID and ensure the OAuth user has write permissions. Mailgun 401 Unauthorized – Check that you used the Private API key and the domain is verified. Backup file too large – Enable chunked upload in Box node or increase client_max_body_size on reverse proxy. Performance Tips Compress backups with gzip or zstd to reduce upload time. Run the database dump on the same host as n8n to avoid network overhead. Pro Tips: Store secrets as environment variables and reference them in Code nodes (process.env.MY_SECRET). Chain backups with version numbers (YYYYMMDD_HHmm) for easy sorting. Use n8n’s built-in execution logging to audit backup history. This is a community workflow template provided “as-is” without warranty. Adapt and test in a safe environment before using in production.