Workflow Templates

How It Works This workflow automates tax compliance by aggregating multi-channel revenue data, calculating jurisdiction-specific tax obligations, detecting anomalies, and generating submission-ready reports for tax authorities. Designed for finance teams, tax professionals, and e-commerce operations, it solves the challenge of manually reconciling transactions across multiple sales channels, applying complex tax rules, and preparing compliant filings under tight deadlines. The system triggers monthly or on-demand, fetching revenue data from e-commerce platforms, payment processors, and accounting systems. Transaction records flow through validation layers that merge historical context, classify revenue streams, and calculate tax obligations using jurisdiction-specific rules engines. AI models detect anomalies in tax calculations, identify unusual deduction patterns, and flag potential audit risks. The workflow routes revenue data by tax jurisdiction, applies progressive tax brackets, and generates formatted reports matching authority specifications. Critical anomalies trigger immediate alerts to tax teams via Gmail, while finalized reports store in Google Sheets and Airtable for audit trails. This eliminates 80% of manual tax preparation work, ensures multi-jurisdiction compliance, and reduces filing errors. Setup Steps Configure e-commerce API credentials for transaction access Set up payment processor integrations (Stripe, PayPal) for revenue reconciliation Add accounting system credentials (QuickBooks, Xero) for financial data Configure OpenAI API key for anomaly detection and tax analysis Set Gmail OAuth credentials for tax team alert notifications Link Google Sheets for report storage and audit trail documentation Connect Airtable workspace for structured tax record management Prerequisites Active e-commerce platform accounts with API access. Payment processor credentials. Use Cases Automated monthly sales tax calculations for multi-state e-commerce. Customization Modify tax calculation rules for specific jurisdiction requirements. Benefits Reduces tax preparation time by 80% through end-to-end automation.

Analyze website SEO issues and generate optimization actions with AI Author: Hyrum Hurst, AI Automation Engineer at QuarterSmart Contact: hyrum@quartersmart.com This workflow provides a fully automated, AI-powered SEO analysis system designed to turn any website URL into a structured set of clear, actionable optimization recommendations. Instead of relying on manual audits, browser extensions, or generic SEO tools, this automation programmatically inspects a page’s core on-page elements and uses AI to translate raw data into practical next steps. The workflow is built for repeatability, scale, and operational use inside agencies, internal marketing teams, and consulting environments. Results are logged, scored, and routed automatically so teams can focus on execution rather than analysis. What this workflow does When a URL is submitted, the workflow: Fetches the full HTML content of the page Extracts critical SEO-relevant elements such as: Page title Meta description Heading hierarchy (H1–H6) Internal and external links Image tags and alt text Sends the extracted data to an AI model for structured analysis Generates specific, prioritized SEO recommendations, including: Keyword optimization opportunities Title and meta description improvements Heading structure fixes Internal linking suggestions Content clarity and relevance improvements Assigns an overall optimization score to the page Logs all results to Google Sheets for tracking, reporting, and comparison over time Sends summaries or alerts to Slack or email when critical issues are detected This creates a hands-off SEO assistant that can be run on demand, scheduled, or integrated into larger automation systems. How it works (high level) A URL is submitted via a Manual Trigger or Webhook An HTTP Request node fetches the page HTML HTML parsing nodes extract structured on-page elements An AI model analyzes the extracted content and generates recommendations A Set node formats the output into clean, readable fields Google Sheets stores the audit results for reporting and history A Switch node routes results based on severity or score Slack and/or email nodes notify stakeholders when action is required The workflow is modular and can easily be extended with additional checks, scoring logic, or integrations. Use cases This template is applicable across many industries and workflows, including: Digital marketing agencies** Run fast, consistent SEO audits for client websites and landing pages. SEO consultants and freelancers** Automate recurring audits and deliver structured recommendations at scale. Ecommerce businesses** Analyze product pages and category pages for discoverability improvements. SaaS companies** Optimize landing pages, feature pages, and pricing pages for search traffic. Content teams and bloggers** Improve on-page SEO without manual checklists or tooling overhead. Web development agencies** Validate SEO readiness before site launches or migrations. Local businesses** Continuously monitor service pages for SEO health and optimization gaps. Real estate, travel, and hospitality websites** Improve visibility of listings, booking pages, and informational content. Why this workflow is useful Eliminates repetitive manual SEO checks Produces standardized, actionable output Works across unlimited URLs and clients Easy to customize for different SEO frameworks Ideal for automation-first teams and agencies This workflow is designed to act as a practical SEO operations layer, not just an analysis tool. For setup support, customization, or help integrating this workflow into your agency or internal systems, contact Hyrum Hurst, AI Automation Engineer at QuarterSmart, at hyrum@quartersmart.com.

Generate personalized concert ticket PDFs with QR codes using PDF Generator API, then email them to attendees, log sales to Google Sheets, and notify organizers via Slack — all triggered from a simple web form. Who is this for Event organizers, ticketing teams, and developers who need an automated pipeline to issue branded PDF concert tickets with unique QR codes for venue entry — without building a custom backend. How it works An attendee fills out a web form with their name, email, event details, seat number, and ticket tier (General / VIP / Backstage). The workflow generates a unique ticket ID and prepares all data for the PDF template. PDF Generator API renders a personalized PDF ticket. The QR code is a native template component that encodes the ticket ID automatically. A styled HTML confirmation email with a download link is sent to the attendee via Gmail. The ticket details are logged to a Google Sheets spreadsheet for tracking and attendance management. A Slack notification alerts the event organizer with a summary of the newly issued ticket. Set up PDF Generator API — Sign up at pdfgeneratorapi.com, create a ticket template with a QR Code component bound to {{ ticket_id }}, and note your template ID. Template ID — Open the "Prepare Ticket Data" Code node and replace the TEMPLATE_ID value with your own. Credentials — Connect your accounts in each node: PDF Generator API, Gmail, Google Sheets, and Slack. Google Sheets — Create a spreadsheet with columns: Ticket ID, Attendee, Email, Event, Venue, Date, Seat, Tier, PDF URL, Issued At. Set the spreadsheet ID in the "Log Ticket Sale" node. Slack — Choose a channel (e.g. #tickets) in the "Notify Event Organizer" node. Requirements PDF Generator API account (free trial available) Gmail account (OAuth) Google Sheets account (OAuth) Slack workspace (optional — remove the last node if not needed) How to customize Output format** — The PDF node returns a hosted URL by default (valid 30 days). Switch to File output to attach the PDF directly to the email instead. Ticket tiers** — Add or rename tiers in the form node and update the tier mapping logic in the "Prepare Ticket Data" Code node. Email design** — Edit the "Build Confirmation Email" Code node to match your brand colors and layout. Remove Slack** — Simply delete the "Notify Event Organizer" node if you don't need organizer alerts. Add payment** — Insert a Stripe or payment node before the form confirmation to handle paid tickets.

About This Template This workflow creates high-quality, text-rich advertising banners from simple LINE messages. It combines Google Gemini (for marketing-focused prompt engineering) and Nano Banana Pro (accessed via Kie.ai API) to generate images with superior text rendering capabilities. It also handles the asynchronous API polling required for high-quality image generation. How It Works Input: Users send a banner concept via LINE (e.g., "Coffee brand, morning vibe"). Prompt Engineering: Gemini optimizes the request into a detailed prompt, specifying lighting, composition, and Japanese catch-copy placement. Async Generation: The workflow submits a job to Nano Banana Pro (Kie API) and intelligently waits/polls until the image is ready. Hosting: The final image is downloaded and uploaded to a public AWS S3 bucket. Delivery: The image is pushed back to the user on LINE. Who It’s For Marketing teams creating A/B test assets. Japanese market advertisers needing accurate text rendering. Developers looking for an example of Async API Polling patterns in n8n. Requirements n8n** (Cloud or Self-hosted). Kie.ai API Key** (for Nano Banana Pro model). Google Gemini API Key**. AWS S3 Bucket** (Public access enabled). LINE Official Account** (Messaging API). Setup Steps Credentials: Configure the "Header Auth" credential for the Kie.ai nodes (Header: Authorization, Value: Bearer YOUR_API_KEY). AWS: Ensure your S3 bucket allows public read access so LINE can display the image. Webhook: Add the production webhook URL to your LINE Developers console.

How It Works This workflow automates performance governance and policy compliance monitoring for HR leaders, talent managers, and organizational development teams across enterprises. It solves the challenge of maintaining consistent performance standards while ensuring human judgment on promotion and termination decisions. Scheduled triggers initiate governance cycles that fetch performance data and policy rules, then orchestrate specialized AI agents working in parallel: governance assessment evaluates policy adherence, performance validation verifies metric accuracy, and calibration analysis ensures rating consistency across departments. A policy compliance checker synthesizes findings and routes outcomes intelligently—approved promotions store automatically, while exceptions requiring HR review trigger human approval gates before case creation and email escalation. Setup Steps Configure API credentials with Llama-3.1-70B-Instruct model access Set up schedule trigger aligned with review cycles (quarterly/annual) Configure decision routing logic for approved versus exception cases Connect Gmail for HR escalation alerts to designated reviewers Set up Google Sheets for storing approved promotions and audit trails Prerequisites API key, performance management system data access, Gmail account with app password Use Cases Annual performance review calibration, promotion decision validation Customization Integrate HRIS for live performance data, add custom policy rule engines Benefits Reduces governance review time by 70%, ensures consistent policy application

Who is this for? This template is perfect for: AI art enthusiasts** who want to stay updated on trending AI-generated artwork Content curators** looking to automate art discovery Japanese-speaking users** who want translated captions Social media managers** tracking AI art trends across platforms What this workflow does This workflow automatically collects viral AI art posts from Instagram and delivers them to your Telegram with Japanese translations. It runs daily and filters only high-engagement posts to ensure quality content. Key Features: 📸 Collects from 4 AI art hashtags (#AIart, #midjourney, #stablediffusion, #aiartwork) 🔥 Filters viral posts only (100+ likes threshold) 🇯🇵 Auto-translates captions to Japanese via DeepL ⚠️ Sends error alerts to Telegram if something goes wrong ⏱️ Built-in rate limiting to avoid API blocks How it works Schedule Trigger - Runs daily at 18:00 Instagram Scraping - Apify collects posts from multiple AI art hashtags Viral Filter - Only posts with 100+ likes and valid captions pass through Translation - DeepL translates captions from English to Japanese Image Download - Fetches the post image Telegram Delivery - Sends photo with translated caption, likes count, and source link Rate Limiting - 3-second delay between posts to avoid API limits Setup Requirements Apify account** - Sign up at apify.com for Instagram scraping DeepL API key** - Get free API access at deepl.com/pro-api Telegram Bot** - Create via @BotFather and get your Chat ID How to set up Import this workflow into n8n Set up credentials: Connect your Apify account Add your DeepL API key Configure Telegram Bot token Replace YOUR_TELEGRAM_CHAT_ID with your actual Chat ID in both Telegram nodes (Optional) Adjust the viral threshold in the Filter node (Optional) Modify hashtags in the Apify node Activate the workflow How to customize Change hashtags:** Edit the directUrls array in the Apify node Adjust viral threshold:** Change the 100 value in the Filter node Change schedule:** Modify the trigger time in the Schedule Trigger node Change language:** Update the translateTo parameter in the DeepL node Modify caption format:** Edit the caption template in the Telegram node

This workflow continuously monitors the TikTok Ads Library for new creatives from specific advertisers or keyword searches, scrapes them via Apify, logs them into Google Sheets, and sends concise notifications to Telegram or Slack with the number of newly discovered ads. It is built as a safe, idempotent loop that can run on a schedule without creating duplicates in your sheet. Use Case Manually checking the TikTok Ads Library for competitor creatives is time-consuming, and it's easy to lose track of which ads you've already seen. This workflow is ideal if you want to: Track competitor creatives over time** in a structured Google Sheet. Avoid duplicates** by matching ads via their unique adId field. Get lightweight notifications* in Telegram or Slack that tell you *how many new ads appeared, without spamming you with full ad lists. Run the process on autopilot** (daily, weekly, etc.) with a single schedule. Monitor by advertiser ID or keywords** with flexible search parameters. How it Works The workflow is organized into four logical blocks: 1. Configuration & Date Conversion Configuration:** The Set Parameters Set node stores all key request variables: Ad target country (e.g., all or specific ISO country codes), Ad published date From (automatically set to yesterday by default), Ad published To (automatically set to today by default), Advertiser name or keyword (for keyword-based searches), adv_biz_ids (advertiser business IDs for specific advertiser tracking), Ad limit (optional limit on the number of results to scrape). Date Conversion:** Convert Dates to Unix transforms the human-readable date format (DD/MM/YYYY) into Unix timestamps in milliseconds, which are required by the TikTok Ads Library API. 2. Request Building & Data Fetching Body Construction:** Build Apify Body creates the JSON request body for the Apify actor: Builds the TikTok Ads Library URL with all search parameters (region, date range, advertiser name/keyword, advertiser IDs). Conditionally adds resultsLimit to the request body only if the Ad limit field is not empty, allowing you to scrape all results or limit them as needed. Data Fetching:** Get TT Ads through Apify executes the Apify actor (Tiktok Ads Scraper) and retrieves all matching ads from the TikTok Ads Library. 3. Data Preparation & De-duplication Data Extraction:** Prepare Data for Sheets safely extracts nested data from the API response: Extracts the first video URL from the videos array (if available). Extracts the cover image URL from the first video object. Extracts the TikTok username from the tiktokUser object (if available). Handles cases where arrays are empty or objects are missing without throwing errors. Load Existing IDs:** Read existing IDs pulls the existing adId column from your Google Sheet (configured to read a specific column/range, e.g., column K). Collect ID list converts these into a unique, normalized string array existingIds, which represents all ads you have already logged. Attach State:** Attach existing ids (Merge node) combines, for each execution, the freshly fetched TikTok response with the historical existingIds array from Sheets. Filter New Creatives:** Filter new creatives Code node compares each ad's adId (string) against the existingIds set and builds a new array containing only ads that are not yet present in the sheet. It also protects against duplicates inside the same batch by tracking seen IDs in a local Set. 4. Data Logging & Notification Write New Ads:** Append or update row in sheet performs an appendOrUpdate into Google Sheets, mapping core fields such as adId, adName, advertiserName, advertiserId, paidBy, impressions, regionStats, targeting, tiktokUser, startUrl, videos, and coverImageURL (using the =IMAGE() formula to display images directly in the sheet). The column mapping uses adId as the matching column so that existing rows can be updated if needed. Count:** In parallel with the write step, Filter new creatives also feeds into Count new ads. This Code node returns a single summary item with newCount = items.length, i.e., the total number of new creatives processed in this run. Guard:** Any new ads? checks whether newCount is greater than 0. If not, the workflow ends silently and no message is sent, avoiding noise. Notify:** When there are new creatives, both Send a text message (Telegram) and Send a message (Slack) send notifications to the configured channels. The message includes {{$json.newCount}} and a fixed link to the Google Sheet, giving you a quick heads-up without listing individual ads. Setup Instructions To use this template, configure the following components. 1. Credentials Apify:** Configure the Apify account credentials used by Get TT Ads through Apify. You'll need an Apify account with access to the Tiktok Ads Scraper actor. Google Sheets:** Connect your Google account in: Read existing IDs, Append or update row in sheet. Telegram (optional):** Connect your Telegram account credentials in Send a text message. Slack (optional):** Configure your Slack credentials in Send a message. 2. The Set Parameters Node Open the Set Parameters Set node and customize: Ad target country: Which countries to monitor (all for all countries, or specific ISO 3166 country codes like US, GB, etc.). Ad published date From: Start date for the search range (defaults to yesterday using {{ $now.minus({ days: 1 }).toFormat('dd/MM/yyyy') }}). Ad published To: End date for the search range (defaults to today using {{ $now.toFormat('dd/MM/yyyy') }}). Advertiser name or keyword: Search by advertiser name or keywords (URL-encoded format, e.g., %22Applicave%20LLC%22). adv_biz_ids: Specific advertiser business IDs to track (comma-separated if multiple). Ad limit: Optional limit on the number of results (leave empty to scrape all available results). 3. Google Sheets Configuration Read existing IDs** Set documentId and sheetName to your tracking spreadsheet and sheet (e.g., Sheet1). Configure the range to read only the column holding the ad adId values (e.g., column K: K:K). Append or update row in sheet** Point documentId and sheetName to the same spreadsheet/sheet. Make sure your sheet has the columns expected by the node (e.g., adId, coverImageURL, adName, Impressions, regionStats, targeting, tiktokUser, advertiserID, paidBy, advertiserName, startURL, videos). Confirm that adId is included in matchingColumns so de-duplication works correctly. 4. Notification Configuration Telegram:** In Send a text message, set: chatId: Your target Telegram chat or channel ID. text: Customize the message template as needed, but keep {{$json.newCount}} to show the number of new creatives. Slack:** In Send a message, set: channelId: Your target Slack channel ID. text: Customize the message template as needed, but keep {{$json.newCount}} to show the number of new creatives. 5. Schedule Open Schedule Trigger and configure when you want the workflow to run (e.g., every morning). Save and activate the workflow. Further Ideas & Customization This workflow is a solid foundation for systematic TikTok competitor monitoring. You can extend it to: Track multiple advertisers** by turning adv_biz_ids into a list and iterating over it with a loop or separate executions. Enrich the log with performance data** by creating a second workflow that reads the sheet, pulls engagement metrics (likes, shares, comments) for each logged adId from TikTok's API (if available), and merges the metrics back. Add more notification channels** such as email, or send a weekly summary that aggregates new ads by advertiser, format, or country. Tag or categorize creatives** (e.g., "video vs image", "country", "language", "advertiser type") directly in the sheet to make later analysis easier. Combine with Meta Ads monitoring** by running both workflows in parallel and creating a unified competitor intelligence dashboard. Add image analysis** by integrating Google Vision API to automatically detect objects, text, and themes in the cover images, similar to the Meta Ads creative analysis workflow.

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

This workflow automatically matches brands with high-converting influencers by analyzing audience insights, engagement patterns, niche alignment, and historical conversion metrics — then delivers a ranked shortlist with detailed match rationale. Who's it for • Brand managers launching influencer campaigns • Marketing agencies managing multiple brand clients • Growth teams running performance-driven influencer programs How it works / What it does Accepts brand requirements via webhook (industry, audience, budget, KPIs) Pulls influencer data from CRM / database or a Google Sheet roster AI analyzes niche alignment, audience overlap, and engagement quality Python scoring engine ranks influencers by conversion probability Filters are applied based on brand budget and minimum thresholds AI generates match rationale and performance predictions Delivers ranked report via email and logs results to Google Sheets How to set up Import this workflow Configure credentials (Gmail/SendGrid, Google Sheets, OpenAI/Anthropic) Populate your influencer data source (Google Sheet or CRM webhook) Activate workflow and POST brand requirements to the webhook URL Requirements • Webhook endpoint (or manual trigger for testing) • Google Sheets (influencer roster + results tracker) • OpenAI / Anthropic / Grok API key • SendGrid or Gmail for delivery How to customize • Adjust scoring weights in the Python node • Change AI tone/output format in the AI nodes • Add more filter criteria in the Filter node • Extend the Google Sheet schema with additional columns Want a custom workflow designed for your business? Our specialists can build it for you in no time—Get in touch with our team

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.

AI Gmail Manager: Sort, Draft & Summarize Transform your chaotic inbox into a streamlined productivity hub! This advanced n8n workflow acts as your personal AI executive assistant. It automatically reads, categorizes, and summarizes your daily emails, generates reply drafts for important messages, and syncs action items directly to Google Tasks. 🧠 Key Features Intelligent Classification:* Uses AI to analyze the context of incoming emails (Sender, Subject, and Snippet) and categorizes them into three levels: *Action Required, Important to Read, and Unimportant/Spam. Automated Inbox Decluttering:** Low-priority emails (like newsletters, receipts, or login alerts) are automatically marked as read, labeled "Unimportant," and archived so you only see what matters. Context-Aware AI Drafts:** If an email requires a response, the workflow automatically generates a ready-to-use draft in your Gmail. Automated Task Extraction:** The AI scans important emails for pending tasks. If a genuine action item is detected, it automatically creates a summarized entry in Google Tasks. Daily Summary:** At the end of the day, the AI compiles all Priority 1 and 2 emails into a neatly structured digest and sends it directly to your inbox. Built-in Time Tracking:** Includes the n8n "Time Saved" node to help you visualize your productivity gains. ⚙️ How It Works Scheduled Trigger: By default, the workflow runs daily at 5:00 PM (17:00). Data Fetching: It connects to Gmail and retrieves all emails received within the last 24 hours. AI Analysis: Emails are processed by an AI Information Extractor that assigns a priority score (1–3) and determines if a reply is needed. Action Execution: Depending on the priority, emails are labeled, marked as read, archived, or sent to the AI agent for drafting and task creation. Summary Generation: Finally, the workflow merges high-priority data, uses an LLM to write a concise summary, and emails it to you. 🚀 Setup Instructions Setup takes 10-15 Minutes depending on if you already use Google OAuth. Schedule: Set your desired trigger time and ensure the workflow timezone is set to local in the n8n settings. AI Setup: Connect your Vertex AI credentials (or your preferred AI model). Gmail: Connect your Gmail credentials. Labels: Create the following labels in your Gmail account: Important, n8n Sorted, and Unimportant. Node Sync: After creating the labels in Gmail, update the corresponding labeling nodes in this workflow to match your label names. Optional Features: Deactivate or delete any unused nodes (e.g., Google Tasks or Time Saving) to skip those steps. Language: If your emails are in a language other than English, you can adjust the prompt language within the LLM Chain nodes. Prompt Customization: You can fine-tune all prompts to your liking—especially the sorting logic, which depends on your preferred AI model and personal needs.

How It Works This workflow automates candidate screening and job matching for recruiters, HR operations teams, and talent acquisition leads. It eliminates the manual effort of parsing resumes, evaluating multi-dimensional candidate fit, and routing outcomes based on assessment confidence. Resume and job data are received via a POST webhook and passed directly to the Matching Agent Orchestrator, backed by a matching model and shared memory. The orchestrator coordinates four specialist agents in parallel: a Resume Parser Agent (structured extraction), a Skill Analysis Agent (competency mapping), an Experience Assessment Agent (seniority and relevance scoring), and a Cultural Fit Agent (organisational alignment evaluation). A Validation Logic Tool cross-checks outputs before a Ranking Output Parser produces a structured candidate ranking. Results are then checked against a confidence threshold — low-confidence cases trigger a review alert via email and are stored in Google Sheets for human follow-up, while high-confidence matches are prepared as analysis data, stored in Sheets, and distributed as a ranked report via email. Setup Steps Import workflow; configure the POST webhook trigger URL for resume and job data ingestion. Add AI model credentials to the Matching Agent Orchestrator, Resume Parser Agent, Skill Analysis Agent, Experience Assessment Agent, and Cultural Fit Agent. Link Google Sheets credentials; set sheet IDs for Low Confidence Cases and Analysis Results tabs. Connect email credentials to the Send Review Required Alert and Send High Confidence Report nodes. Set confidence threshold values in the Check Confidence Level node. Prerequisites OpenAI API key (or compatible LLM) Google Sheets with candidate tracking tabs pre-created Email account credentials (SMTP or Gmail OAuth) Use Cases Recruiters automating high-volume resume screening against structured job descriptions Customisation Extend specialist agents with domain-specific scoring rubrics for technical or executive roles Benefits Four parallel specialist agents evaluate candidates across skills, experience, and cultural fit simultaneously