by WeblineIndia
WooCommerce VIP Customer Automation This workflow automatically identifies VIP customers from your WooCommerce store based on their total spending and number of completed orders. It pulls new orders on a schedule, filters valid transactions, groups customers, calculates their VIP tier, stores them into Airtable and notifies your team in Slack.It removes all manual checking and ensures your team instantly knows when a high-value customer places an order. Quick Start – Implementation Steps Add your WooCommerce store domain and API credentials inside n8n. Configure Airtable and Slack credentials. Adjust VIP rules (lifetime spend or total orders) if needed. Activate the workflow — it will automatically detect VIPs and alert your team. What It Does This workflow fully automates VIP customer detection for WooCommerce stores. Every few minutes, it retrieves new orders via WooCommerce API. It filters only processing or completed orders and extracts essential fields such as customer ID, customer name order total and timestamps. The workflow then groups orders by customer to ensure duplicate orders don’t inflate metrics. For each customer, it fetches their complete order history, calculates lifetime value, counts total paid orders and assigns a VIP tier (Platinum, Gold or Silver). Once a customer qualifies, their details are saved into Airtable for tracking. A Slack message is simultaneously sent to inform your team so they can take immediate action — such as providing priority support, follow-up messages or special offers. This system runs completely on its own and keeps customer insights up-to-date without manual checks. Who’s It For This workflow is ideal for: WooCommerce store owners Customer support teams Marketing teams CRM & retention specialists eCommerce operations teams Businesses wanting automated VIP alerts Requirements to Use This Workflow You will need: A running n8n instance (cloud or self-hosted) A WooCommerce store with API keys A Slack workspace with API permissions An Airtable Base to store VIP customers Basic understanding of WooCommerce and Airtable fields How It Works Scheduled Trigger – Runs every few minutes to check for new orders. Domain Setup – Assigns the WooCommerce store domain used across API calls. Fetch Orders – Retrieves all orders from WooCommerce. Filter Valid Orders – Only keeps completed or processing orders. Format & Clean Data – Extracts only key order details. Deduplicate Customers – Only the first order per customer is processed. Fetch Order History – Gets lifetime order history for each customer. Calculate VIP Tier – Determines Platinum/Gold/Silver based on spend or order count. Filter VIP Only – Removes customers who do not qualify. Save to Airtable – Creates/updates VIP records. Notify Team on Slack – Sends VIP alerts instantly. Setup Steps Import this workflow JSON into n8n. Enter your WooCommerce API credentials in the HTTP Request nodes. Update the wc\_domain value in the “Set WooCommerce Domain” node. Configure Airtable credentials and select your Base + Table. Set your Slack channel ID inside the Slack node. Adjust VIP rules inside the “Calculate VIP Tier” code node if needed. Activate the workflow — it will now run automatically. How to Customize Nodes Adjust VIP Rules Edit the logic inside Calculate VIP Tier: Change Platinum threshold (₹20,000 or your value) Change Gold rule (5 orders or more) Add new VIP tiers Customize Airtable Fields You can modify: Table columns Field naming Additional customer details Customize Slack Alerts In the Slack node, change: Message format Channel ID Emoji, headings or urgency indicators Add-Ons (Optional Enhancements) You can extend this workflow with: Automatic email to VIP customers Loyalty point calculation Google Sheets export Integration with CRM platforms Send SMS notifications Separate VIP tiers into dedicated Slack channels Use Case Examples Notify support about high-value customers Track customers crossing spending milestones Identify loyal customers with 5+ repeat purchases Automatically sync VIP customers to CRM Trigger loyalty coupon generation Troubleshooting Guide | Issue | Possible Cause | Solution | |---------------------------|--------------------------------------------------|--------------------------------------------------------------| | No orders fetched | Wrong domain or API keys | Update WooCommerce credentials | | VIP not detected | Customer has low spend or low orders | Verify VIP rules in “Calculate VIP Tier” | | Airtable record not created | Incorrect table schema | Match Airtable fields with node mapping | | Slack alert missing | Wrong Slack channel ID or credentials | Re-check Slack authentication | | Guest users included | Missing customer_id filter | Ensure customer_id != 0 condition stays in place | Need Help? If you need assistance integrating this workflow, customizing VIP rules or adding new automations, our automation team at WeblineIndia is happy to help. You can also extend this system with loyalty engines, advanced analytics, multi-store support or any custom automation tailored for your eCommerce business.
by Devon Toh
This Template Demonstrates How To Automate Generating and Sending Personalized Quotations as PDF. Use cases are many: send branded quotations to new leads after a discovery call, distribute pricing proposals to inbound form submissions, or push service packages to prospects. All without manually creating documents, exporting PDFs, or writing individual emails. Good to know OpenAI charges per token. The workflow uses gpt-4o-mini for cost efficiency (~$0.15/1M input tokens). Check OpenAI Pricing before running at scale. Google Docs template must be set up with placeholder variables before the first run. The workflow fills data in — it won’t generate a layout for you. Gmail has daily sending limits depending on your Google Workspace plan. Check your quota before sending large volumes. The form is hosted by n8n — share the form URL with your team or embed it in your internal tools. How it works PHASE 1: FORM INTAKE An n8n Form Trigger collects all quotation details: client name, email, company, service type, service description, price, validity date, and optional notes. The form is self-hosted on your n8n instance — no third-party form tools needed. Once submitted, all fields pass directly into the workflow as structured data. PHASE 2: AI PERSONALIZATION The form data is sent to OpenAI (gpt-4o-mini) which generates two pieces of content: – A personalized introduction paragraph addressing the client by name, referencing their company and specific needs. – A structured scope of work summary with deliverable bullet points based on the service description. Output is returned as JSON so it slots cleanly into the document template and email body. PHASE 3: DOCUMENT GENERATION The workflow copies your pre-built Google Docs quotation template to a new document, named automatically as “Quotation - {Company} - {Service}”. Nine placeholder variables are replaced in the copied document: {{client_name}}, {{company_name}}, {{client_email}}, {{service}}, {{price}}, {{valid_until}}, {{notes}}, {{intro}}, and {{scope_summary}}. The completed document is exported from Google Drive as a PDF. Your branding, layout, and formatting stay exactly as designed in the template. PHASE 4: EMAIL DELIVERY The PDF is attached to a personalized email sent via Gmail directly to the client’s email address. The email body includes the AI-generated intro, scope of work summary, total price, and validity date — no manual copy-pasting. The form submitter sees a confirmation response once the email is sent. Closed loop, fully hands-off. How to use Create your Google Docs template with your preferred layout, branding, and these placeholders: {{client_name}}, {{company_name}}, {{client_email}}, {{service}}, {{price}}, {{valid_until}}, {{notes}}, {{intro}}, {{scope_summary}}. Copy the template Document ID from the URL (docs.google.com/document/d/THIS_PART/edit) and paste it into the Copy Template node. Configure Google OAuth via Google Console. Create a project, apply your Client ID and Secret in the Google Drive, Google Docs, and Gmail node credentials. Set the OpenAI credential with your API key in the OpenAI Personalize node. Share the form URL with your team. The URL is generated automatically when the workflow is activated. Requirements • OpenAI API — personalized intro and scope generation • Google Drive OAuth — template copying and PDF export • Google Docs OAuth — variable replacement in the document • Gmail OAuth — personalized email delivery with PDF attachment • n8n instance (self-hosted or cloud) Customising this workflow • Swap the form trigger for a webhook or CRM integration (HubSpot, GoHighLevel, Airtable) if you want quotations generated from pipeline stage changes instead of manual form submissions. • Add a Slack or email approval step before sending — insert a Slack node between Export as PDF and Send Quotation Email if you want a manager to review before it goes out. • Replace Gmail with any email provider (Outlook, SMTP, SendGrid) if your team doesn’t use Google Workspace. • Add a Google Sheets logging step after sending to track all sent quotations with client name, date, service, and price for reporting. • This pattern works beyond quotations — try it for proposals, invoices, contracts, or any document where the structure stays fixed but the data changes. • Add multiple service line items by extending the form with repeating fields and adjusting the template to include a table of services with individual pricing.
by Akshay Chug
Overview Know what your competitors are doing every morning before your first meeting. This workflow visits each competitor website daily, uses OpenAI to analyse it for strategic signals, and emails your team a consolidated executive briefing automatically. How it works A schedule trigger fires every morning at 8AM Your list of competitor URLs is loaded from the Configure node Each competitor page is fetched and stripped to clean readable text GPT-4o-mini analyses each one for key signals, threat level, and recommended actions All analyses are aggregated and sent to GPT-4o to write one consolidated executive briefing The briefing is formatted as a clean HTML email and sent to your team via Gmail Every run is logged to Google Sheets with the date and summary Setup steps Competitors — Open Configure Competitors and Settings, replace the placeholder URLs with your real competitor URLs Your details — In the same node set YOUR_COMPANY and YOUR_FOCUS to describe your market OpenAI — Add your OpenAI API key as a credential at platform.openai.com Gmail — Connect your Gmail account in Send Email Briefing and set your team email in the Configure node Google Sheets — Create a sheet with columns: Date, Company, Competitors Analyzed, Briefing Summary. Connect your Google account and update the sheet ID in the Log node Activate the workflow — it runs automatically at 8AM every day
by Vlad Arbatov
Summary Send a number to your Telegram bot (e.g., 2) and get a neatly formatted digest of all Gmail newsletters received since that date. Each email is summarized by an LLM into concise topics, merged into a single Telegram message, automatically split into chunks to fit Telegram limits, and safely formatted as HTML. What this workflow does Triggers on your Telegram message containing a number of days, e.g., 1, 2, 7 Fetches all Gmail messages since that date using a custom search query, optionally filtered by senders Retrieves and decodes each email’s HTML, subject, sender name, date Prompts an LLM (GPT‑4.1‑mini) to produce a consistent JSON summary of topics per email Merges topics from all emails into a single digest Builds a readable, enumerated message (with bold titles) Splits it into 3 500‑char parts and sanitizes Markdown to Telegram‑safe HTML Sends the digest to your Telegram chat with preview disabled Apps and credentials Gmail OAuth2: Gmail account Telegram: Telegram account (bot) OpenAI: OpenAi account Typical use cases Personal or team daily/weekly newsletter digests in Telegram Curated feeds from selected senders compiled on demand Lightweight knowledge briefings without leaving Telegram How it works (node-by-node) Telegram Trigger Waits for your message (e.g., "2"). Chat ID is restricted to your Telegram ID for safety. Get days (Code) Takes the numeric daysAgo from the Telegram message text Computes YYYY/MM/DD for Gmail’s after: filter Get many messages (Gmail → getAll, returnAll: true) Uses a custom q filter like: =(from:@.com) OR (from:@.com) OR (from:@.com -"__") after:{{ $json.dateString }} Returns a list of message IDs Loop Over Items (Split in Batches) Iterates through each message ID Get a message (Gmail → get) Retrieves the full message/payload for the current email Get message data (Code) Extracts HTML from Gmail’s payload (body/parts) Normalizes sender to just the name Formats the date as DD.MM.YYYY Passes html, subject, from, date forward Clean (Code) Converts DD.MM.YYYY → MM.DD (for prompt brevity) Passes html, subject, from, date to the LLM Message a model (OpenAI, model: gpt‑4.1‑mini, JSON output) Prompt instructs: Produce JSON: { "topics": [ { "title", "descr", "subject", "from", "date" } ] } Split multi-news blocks into separate topics Combine or ignore specific blocks for particular senders (placeholders __) Keep subject untranslated; other values in __ language Injects subject/from/date/html from the current email Loop Over Items (continues) After all iterations complete, the aggregated per-email results are available Merge (Code) Flattens the topics arrays from all processed emails into one combined topics list Create TG message (Code) Renders an enumerated list: 1. Title (bold) Short description Original subject From — Date Split (Code) Splits into 3 500‑character chunks to stay below Telegram’s 4 096 limit with HTML overhead Sanitize (Code) Escapes &, <, > Fixes unbalanced * and _ Converts basic Markdown markers to Telegram HTML Send a message (Telegram) Sends each part with parse_mode=HTML, previews disabled Node map | Node | Type | Purpose | |---|---|---| | Telegram Trigger | Trigger | Receive daysAgo command from Telegram | | Get days | Code | Compute Gmail after:YYYY/MM/DD from daysAgo | | Get many messages | Gmail (getAll) | Search emails since date with custom from: filters | | Loop Over Items | Split in Batches | Iterate messages one-by-one | | Get a message | Gmail (get) | Fetch full message payload | | Get message data | Code | Extract HTML/subject/from/date; normalize sender and date | | Clean | Code | Reformat date and forward fields to LLM | | Message a model | OpenAI | Summarize email into JSON topics | | Merge | Code | Merge topics from all emails | | Create TG message | Code | Build human-friendly digest text | | Split | Code | Chunk into 3 500‑char parts | | Sanitize | Code | Escape HTML and map Markdown to Telegram HTML | | Send a message | Telegram | Deliver digest to Telegram chat | Before you start Create a Telegram bot and get its token (via @BotFather) Get your Telegram user ID to restrict access Connect Gmail OAuth2 in n8n Add your OpenAI API key Import the provided workflow JSON into n8n Setup instructions 1) Telegram Telegram Trigger node: additionalFields.chatIds = your Telegram user ID Send a message node: chatId = your Telegram user ID parse_mode = HTML disable_web_page_preview = true 2) Gmail Connect a Gmail OAuth2 credential (Gmail account) In Get many messages, adjust filters.q to your senders and rules: Example: =(from:news@publisher.com) OR (from:briefs@media.com -"promo") after:{{ $json.dateString }} If needed, add label: or category: filters 3) OpenAI Message a model: Model: gpt‑4.1‑mini (can swap to gpt‑4o‑mini or your preferred) Update the prompt placeholders: __ language → your target language __ sender rules → your special cases (combine blocks, ignore sections) 4) Safety and formatting Keep parse_mode=HTML in Telegram The Sanitize node is designed for ` and ` only; avoid other HTML tags The Split node uses 3 500 chars per part to stay safe under Telegram limits How to use In Telegram, send a number indicating “days ago” Example: 2 → will query Gmail after the date 2 days ago The workflow compiles and returns a digest in your chat Rerun anytime with a new number Customization ideas Labels instead of global search: q = label:Newsletters after:{{ $json.dateString }} Time window control: add before: or exact date ranges Different language: set the __ language in the LLM prompt Model choice: swap to cheaper/faster models if volume is high Chunk size: adjust from 3 500 to your needs Formatting: tweak Create TG message to include links parsed from HTML (if you add an HTML parser step) Limits and notes Telegram messages are limited to ~4 096 characters; we chunk to 3 500 per part Gmail “after:” uses YYYY/MM/DD and Google’s interpretation of dates; your n8n server time influences the computed date LLM usage incurs cost and latency proportional to email size and count HTML extraction is robust for typical Gmail structures but may need tweaks for exotic MIME layouts Privacy and safety Emails are sent to OpenAI for summarization—ensure that’s acceptable for your data policies The Telegram Trigger restricts chat access; keep your chatIds locked down Avoid sending raw HTML to Telegram; rely on the Sanitize node Sample output format (Telegram) Bold topic title One-sentence description Original Subject Line → Sender Name — DD.MM.YYYY Next topic title ... Tips and troubleshooting Got empty digests? Check Gmail filters.q and make sure there really are emails after the computed date Model errors or empty JSON? Lower prompt complexity or switch model HTML formatting issues in Telegram? Ensure parse_mode=HTML and keep only `, ` Long messages not fully delivered? Reduce chunk size from 3 500 Tags gmail, telegram, openai, llm, newsletters, digest, summarization, automation Changelog v1: Initial release with sender filters, topic merging, Telegram HTML sanitization, and on-demand time window via Telegram message
by Avkash Kakdiya
How it works This workflow automatically captures website visitors using Albacross, enriches their data with Datagma, and syncs it into HubSpot. Once leads are created or updated, a personalized email is generated and sent through Gmail. All email activities are logged in HubSpot for proper sales tracking and follow-up. Step-by-step 1. Trigger the workflow Schedule Trigger** – Runs the workflow at set intervals (hourly, daily, or custom). 2. Capture website visitors Albacross Website Visitor** – Pulls company and visitor details from website activity. 3. Enrich lead data Enrich Lead Data** – Enhances visitor records with personal and professional details via Datagma. 4. Sync to CRM Create/Update HubSpot Contact** – Creates or updates contact records in HubSpot with enriched lead data. 5. Generate personalized outreach Generate Personalized Message** – Builds a tailored email including company, industry, and value propositions. 6. Send and track emails Send Personalized Email** – Sends the outreach message through Gmail. Log Email Activity in HubSpot** – Tracks email engagement automatically in HubSpot. Why use this? Capture and identify anonymous website visitors as potential leads. Enrich contact details with accurate, professional information. Keep HubSpot updated automatically without manual data entry. Send highly personalized outreach emails tailored to each lead. Log all communication for better pipeline visibility and sales follow-up.
by isaWOW
Paste your raw meeting notes into a simple web form and submit. The workflow sends your notes to GPT-4o-mini, which converts them into a clean 6-section structured document. The finished document saves automatically to your Google Drive folder — ready to share with your team or client. Built for agency teams, consultants, and project managers who spend too much time cleaning up notes after every call. What This Workflow Does Collects meeting details via form — A built-in web form captures the client name, date, attendees, raw notes, your name, and your Drive folder ID in one submission. Auto-builds the document title — Combines the client name and meeting date into a clean file name automatically — no manual renaming needed. Structures messy notes with AI — GPT-4o-mini reads your rough bullet points or sentences and returns a properly formatted 6-section document every time. Enforces consistent output format — A structured output parser locks GPT-4o-mini into returning exactly the six required fields — no missing sections, no extra content. Handles missing data gracefully — If a section has no relevant content in your notes, the workflow fills it with a clear fallback message instead of leaving it blank or failing. Saves directly to Google Drive — The finished document lands in the exact Drive folder you specify — no copy-pasting, no manual uploads. Setup Requirements Tools and accounts needed: n8n instance (self-hosted or cloud) OpenAI account with API access (for GPT-4o-mini) Google account with Google Drive access (OAuth2 credential) Estimated Setup Time: 8–12 minutes Step-by-Step Setup Import the workflow — Open n8n → Workflows → Import from JSON. Paste the workflow JSON and import. Confirm all 7 nodes are connected in sequence. Connect your OpenAI API key — Go to Credentials → New → OpenAI API in n8n. Paste your API key from platform.openai.com. Open the 4. OpenAI — GPT-4o-mini Model node and select this credential. Connect your Google Drive credential — Go to Credentials → New → Google Drive OAuth2 in n8n. Complete the OAuth flow with the Google account that owns the Drive folder where notes should be saved. Open the 7. Google Drive — Save Notes Document node and select this credential. > ⚠️ The 7. Google Drive — Save Notes Document node ships with no credential connected. The workflow will fail at the final step if you skip this. Connect it before activating. Find your Google Drive Folder ID — Open Google Drive in your browser. Navigate to the folder where you want notes saved. Look at the URL — copy the string of characters after /folders/. That is your Folder ID. You will paste this into the form each time you submit notes. Activate the workflow — Toggle the workflow to Active. Open the 1. Form — Meeting Notes Submission node and copy the Form URL. Paste this URL into your browser to access the submission form. How It Works (Step by Step) Step 1 — Form Trigger (Meeting Notes Submission) You open the form URL in any browser and fill in six fields: client or project name, meeting date, attendees, raw notes, your name, and your Google Drive folder ID. Submitting the form sends all six values to the workflow instantly. Step 2 — Set (Extract Form Fields) All six form values are mapped into clean named variables. The document title is also built automatically here — it combines the client name and meeting date into the format: Meeting Notes — [Client Name] — [Meeting Date]. Step 3 — AI Agent (Structure Meeting Notes) GPT-4o-mini receives your raw notes alongside a detailed prompt. It reads everything and returns a structured JSON object with exactly six fields: a header block, an overview, key discussion points, decisions made, action items with owner and deadline, and next steps. The AI is instructed to use plain text only — no markdown, no symbols. Step 4 — OpenAI Model (GPT-4o-mini) This is the language model powering the AI Agent in Step 3. It runs at a temperature of 0.3 for consistent, predictable formatting and has a 1,200-token output limit — enough for a thorough set of meeting notes. Step 5 — Parser (Structured Notes Output) A structured output parser enforces the exact JSON schema on the AI's response. It ensures all six required fields are present and correctly typed. This prevents the workflow from producing incomplete or malformed output even if the AI response is slightly off. Step 6 — Code (Assemble Full Document) A short script reads the six structured fields and assembles them into one plain-text document with clear section headings. If any field is empty or missing, a fallback message fills it automatically. The document title and folder ID from Step 2 are also passed forward here. Step 7 — Google Drive (Save Notes Document) The completed plain-text document is created as a new file in your specified Google Drive folder. The file name is the auto-generated document title from Step 2. Your structured meeting notes are now saved and ready to share. Key Features ✅ Web form trigger — No n8n login needed to submit notes — anyone with the form URL can use it from any browser. ✅ Auto-generated file name — Every file is named consistently using the client name and meeting date — your Drive stays organized without extra effort. ✅ Schema-enforced AI output — The structured output parser locks GPT-4o-mini to exactly 6 fields — you always get a complete document, never a partial one. ✅ Action items with owner and deadline — GPT-4o-mini formats every task as Task | Owner | Deadline and writes Not assigned or Not specified when the information is not in your notes. ✅ Fallback text for empty sections — Missing data never breaks the document — each empty section gets a clear placeholder message automatically. ✅ Dynamic folder routing — You specify the Drive folder ID in the form, so you can route different clients' notes to different folders from a single workflow. ✅ Plain-text output — No markdown, asterisks, or formatting symbols in the final document — it reads cleanly in any viewer and copies cleanly into any tool. Customisation Options Route notes to a fixed folder — If you always save to the same Drive folder, remove the Google Drive Folder ID field from the form in 1. Form — Meeting Notes Submission and hardcode your folder ID directly in the 2. Set — Extract Form Fields node under folderId. Add a seventh section — To include a section like "Open Questions" or "Risks Identified", add a new field to the JSON schema in 5. Parser — Structured Notes Output and add a matching instruction to the prompt in 3. AI Agent — Structure Meeting Notes, then include it in the assembly script in 6. Code — Assemble Full Document. Send an email confirmation — Add a Gmail node after 7. Google Drive — Save Notes Document and use the docTitle and folderId values already available to send a confirmation email to the person who submitted the form. Add a dropdown for meeting type — In 1. Form — Meeting Notes Submission, add a dropdown field (e.g., Client Call / Internal Sync / Discovery) and pass that value into the AI prompt in 3. AI Agent — Structure Meeting Notes to tailor the tone or section focus by meeting type. Save as a Google Doc instead of a plain-text file — In 7. Google Drive — Save Notes Document, change the file creation settings to use Google Docs MIME type so the output opens natively in Google Docs with editable formatting. Troubleshooting AI Agent produces incomplete or missing sections: Check that the 4. OpenAI — GPT-4o-mini Model credential is valid and has available API credits Open the execution log for 3. AI Agent — Structure Meeting Notes to see if an OpenAI error was returned If the raw notes are very short or vague, GPT-4o-mini may struggle — add more detail to your notes before submitting Google Drive node fails and the file is not saved: Confirm the 7. Google Drive — Save Notes Document node has a Google Drive OAuth2 credential connected — it ships without one Re-authenticate the credential if it has expired Verify the folder ID you pasted in the form is correct — open the Drive folder in your browser and re-copy the ID from the URL after /folders/ Form submission does not trigger the workflow: Confirm the workflow is toggled to Active — the form URL only works when the workflow is active Check that you are opening the correct Form URL from the 1. Form — Meeting Notes Submission node If you recently re-imported the workflow, the form URL may have changed — copy it again from the node Document title is blank or shows raw placeholders: Confirm the Client or Project Name and Meeting Date fields were filled in before submitting the form — both are required fields Open the execution log for 2. Set — Extract Form Fields to verify the values were received correctly from the form Output file contains Not available in every section: This means the AI received the raw notes but could not extract meaningful content — check that the Raw Meeting Notes field was filled in with actual content, not left empty Confirm the 5. Parser — Structured Notes Output node did not return an error — if the AI output did not match the schema, all fields fall back to their default messages Support Need help setting this up or want a custom version built for your team or agency? 📧 Email:info@isawow.com 🌐 Website:https://isawow.com
by Oneclick AI Squad
Automatically scans incoming job emails and LinkedIn messages, intelligently detects genuine opportunities, and sends personalized, professional replies using your resume and preferences. It extracts job details, crafts human-sounding responses with AI, sends them instantly, and maintains a complete tracking sheet in Google Sheets with status and follow-up dates. Perfect for active job seekers who want to reply faster and smarter without spending hours writing tailored applications. Who’s it for • Job seekers applying to 10+ jobs per week • Professionals receiving recruiter inbound messages • Career switchers managing high application volume How it works / What it does Captures new job emails or LinkedIn messages Analyzes if it's a relevant job opportunity Loads your resume and preferences AI generates personalized, human reply Sends the tailored response Logs everything with status in Google Sheet How to set up Import this workflow Set up credentials (Gmail, Google Sheets, OpenAI/Anthropic) Update your resume text and preferences Activate workflow Requirements • Gmail access (or IMAP) • Google Sheets • OpenAI / Anthropic / Grok API • Your latest resume How to customize the workflow • Change AI tone in the AI node • Modify Python filter keywords • Update Google Sheet columns • Adjust wait times
by Akshay Chug
Overview Stop spending Monday mornings manually pulling numbers and building reports. This workflow reads your last 7 days of business data from Google Sheets, asks Claude AI to compare it to the week before, spot trends, flag problems and highlight wins — then emails a plain-English health report to your inbox before your team standup. How it works Fires every Monday at 7AM automatically Pulls this week's and last week's data from your Google Sheet Formats both datasets into a clean comparison table Claude AI analyses the numbers and writes a structured health report covering wins, concerns, and top 3 actions Report is emailed to your team via Gmail Every run is logged to a second sheet tab for historical tracking Setup steps Google Sheets — Connect your Google account in Fetch This Week Data and Fetch Last Week Data nodes and select your data sheet. Each row should be one day, columns should be your key metrics Configure node — Open Configure Report Settings and set your business name, report email, and a plain-English description of what your columns mean Claude AI — Add your Anthropic API key to the Claude Sonnet sub-node from console.anthropic.com Gmail — Connect your Gmail account in Send Weekly Report Log sheet — Create a second tab called Report Log with columns: Date, Week Covered, Business, Status, Summary. Connect it in Log Report Run Activate — runs automatically every Monday at 7AM
by DataForSEO
This weekly workflow helps you keep track of new Featured Snippet visibility for your domain without manual SERP checks. Each week, it fetches the most recent data from DataForSEO, saves a snapshot to Google Sheets, and compares it against the previous run. Any new keywords for which your domain appears in a Featured Snippet are automatically added to a dedicated sheet along with ranking and search volume data, creating a historical log of growth over time. Lastly, the workflow sends you or your team an email overview highlighting how many new keywords were found, so you never miss an important update. Who’s it for SEO professionals, marketers and content teams who want an automated way to monitor new keyword appearances in Google’s Featured Snippets and receive regular updates without checking SERPs by hand. What it does This workflow automatically detects when your domains start ranking for new keywords in Featured Snippets, records those keywords in Google Sheets, and sends a brief weekly summary of changes via email. How it works Runs on a predefined schedule (default: once a week). Reads your keywords and domains from Google Sheets. Extracts the latest data on Google’s Featured Snippet results via DataForSEO API. Compares the data with the previous snapshot. Logs newly ranked keywords to a dedicated Google Sheet. Sends a summary email with key highlights. Requirements DataForSEO account and API credentials A spreadsheet in Google Sheets with your keywords, following the required column structure (as in the example). A spreadsheet in Google Sheets with your target domains, following the required column structure (as in the example). Gmail account Customization You can easily adapt this workflow to your specific needs and preferences by adjusting the schedule, exporting results to other tools (like Looker Studio and BigQuery) instead of Google Sheets, and cusomtizing the email content.
by Cadu | Ei, Doc!
This n8n template demonstrates how to automate blog post creation with AI and WordPress This workflow is designed for creators who want to maintain an active blog without spending hours writing — while still taking advantage of SEO benefits. It connects OpenAI and WordPress to help you schedule AI-generated posts or create content from simple one- or two-word prompts. 🧠 Good to know At the time of writing, each AI-generated post will use your OpenAI API credits according to your model and usage tier. This workflow requires an active WordPress site with API access and your OpenAI API key. Setup is quick — in less than 5 minutes, you can have everything running smoothly! ⚙️ How it works The workflow connects to your WordPress API and your OpenAI account. You can choose between two modes: Scheduled mode: AI automatically creates and publishes posts based on your defined schedule. Prompt mode: Enter a short phrase (one or two words) and let AI generate a complete SEO-optimized post. The generated content is formatted and published directly to your WordPress blog. You can easily customize prompts, post styles, or scheduling frequency to match your brand and goals. 🚀 How to use Start with the Manual Trigger node (as an example) — or replace it with other triggers such as webhooks, cron jobs, or form submissions. Adjust your OpenAI prompts to fine-tune the tone, structure, or SEO focus of your posts. You can also extend this workflow to automatically share posts on social media or send notifications when new articles go live. ✅ Requirements Active OpenAI API key WordPress site** with API access 🧩 Customising this workflow AI-powered content creation can be adapted for many purposes. Try using it for: Automated content calendars Generating product descriptions Creating newsletter drafts Building SEO-focused blogs effortlessly
by AI Solutions
How it works Webhook Trigger — A web form POSTs prospect details, selected services, discount level, and requestor info to the webhook endpoint. Fetch Pricing Sheet — Retrieves all rows from your pricing_request.xlsx Excel table in OneDrive/SharePoint. Process & Price — Filters the pricing rows to the selected services, applies the correct Discount / Retail / Premium price tier, and calculates the total. Build HTML — Renders a fully branded HTML proposal document with cover info, line-item pricing table, terms, and a signature block. Convert to PDF — Sends the HTML to a self-hosted Gotenberg instance, which returns a print-ready PDF. Email Proposal — Delivers the PDF as an attachment via Gmail OAuth2 to the requester and any internal recipients you configure.
by Avkash Kakdiya
How it works This workflow automates lead nurturing by pulling data from Google Sheets, analyzing leads with AI, and sending personalized outreach emails. It runs on a schedule, processes leads in batches, and routes them based on their status and step. AI generates both first-touch and follow-up emails while updating the CRM automatically. The system ensures consistent outreach and tracks lead progression without manual work. Step-by-step Trigger and lead intake** Schedule Trigger – Runs the workflow at set intervals. Get row(s) in sheet – Fetches lead data from Google Sheets. If – Filters leads that need action based on status or date. Data preparation and batching** Code in JavaScript – Normalizes fields like email, name, and company. Loop Over Items – Processes leads in controlled batches. AI lead scoring and routing** AI-Lead-Analysis – Evaluates lead quality and assigns score and priority. Parse AI – Extracts structured AI insights from the response. Switch – Routes leads based on outreach step or status. First outreach automation** First AI mail – Generates a personalized cold email. Save Message – Stores the generated message. Send a message – Sends the email via Gmail. Update row in sheet – Updates CRM with outreach details. Follow-up and pipeline completion** AI-Follow-up – Creates a follow-up email using AI. Parse Follow-up – Extracts follow-up message content. Send a message1 – Sends the follow-up email. Update row in sheet1 – Updates CRM with follow-up info. Wait – Delays before checking for response. If1 – Checks if the lead replied or not. Update row in sheet2 – Marks lead as closed if no response. Why use this? Automates end-to-end outbound lead nurturing Uses AI for smarter lead scoring and personalization Reduces manual CRM updates and follow-up tracking Improves response rates with timely outreach Scales cold email campaigns efficiently