Google Drive and Slack integration

Automated Email Verification & Digital Health Card Generator Overview Transform your clinic's patient check-in process with this fully automated pre-registration system. When patients submit their appointment information through your website, this workflow instantly verifies their email, generates a professional digital health card with a scannable QR code, stores it securely in Google Drive, and sends personalized notifications to both the patient and your reception team—all in under 20 seconds. What This Workflow Does This comprehensive automation handles the entire patient pre-check-in journey: Receives Patient Data - Webhook captures form submissions from your website or app with patient details (name, email, phone, appointment date/time, symptoms, age, gender) Validates & Cleans Data - Automatically validates required fields, cleans input data, and generates a unique patient ID with timestamp for tracking Verifies Email Address - Uses VerifiEmail API to ensure email deliverability by checking RFC compliance, MX records, and filtering out disposable/spoof emails Generates QR Code - Creates a unique verification URL and scannable QR code for instant patient identification at reception Builds Professional Health Card - Generates a beautiful, responsive HTML health card featuring: Patient information grid (name, ID, email, phone, age/gender, appointment) Chief complaints/symptoms section Embedded QR code for quick check-in Important appointment instructions Modern gradient design with mobile-responsive layout Converts to PNG Image - Uses HTMLCSSToImg API to convert the HTML card into a high-quality PNG image (900x1200px) Stores in Google Drive - Uploads the health card to an organized "Patients record" folder with patient ID-based naming for easy retrieval Emails Patient - Sends a beautifully formatted email to the patient containing: Their health card as a PNG attachment Appointment details and confirmation Google Drive link for backup access Check-in instructions and preparation tips Notifies Reception Team - Sends real-time Slack message to clinic reception with patient details, verification status, and Drive link Logs to Database - Records complete patient information, timestamps, verification status, and file links in Google Sheets for tracking and analytics Returns Success Response - Sends JSON response back to the website form with patient ID, confirmation, and Drive link Key Features ✅ Email Verification - VerifiEmail API integration prevents failed deliveries and fake emails ✅ Unique Patient IDs - Timestamp-based IDs ensure no duplicates (format: PAT-{timestamp}-{random}) ✅ QR Code Generation - Free QR Server API creates scannable codes for instant check-in ✅ Professional Design - Modern, gradient-styled health cards with responsive layout ✅ Multi-format Output - PNG image format for easy viewing on any device ✅ Cloud Storage - Secure Google Drive storage with organized folder structure ✅ Multi-channel Notifications - Email to patient + Slack to staff for complete coverage ✅ Comprehensive Logging - Google Sheets database for analytics and record-keeping ✅ Error Handling - Graceful failure for invalid emails with user notification ✅ Webhook Response - Real-time feedback to website form for seamless UX ✅ Indian Locale Support - Date/time formatting in Indian format with 12-hour time ✅ Mobile Responsive - Health cards look great on both desktop and mobile devices Perfect For 🏥 Medical Clinics & Healthcare Providers - Streamline patient pre-registration and reduce waiting times 🦷 Dental Practices - Digital check-in for appointments with patient history 💉 Diagnostic Centers - Pre-appointment verification for lab tests and scans 👨‍⚕️ Specialist Doctors - Organized patient records with symptoms documentation 🏃 Physiotherapy Clinics - Track patient visits and treatment history 💆 Wellness Centers & Spas - Appointment management with customer details 🐕 Veterinary Clinics - Pet owner pre-registration system 📋 Any Appointment-Based Business - Adaptable to salons, consultancies, or service providers Business Benefits 💰 Reduced No-Shows - Email verification ensures valid contact information ⏱️ Time Savings - Eliminates manual data entry at reception 📊 Better Analytics - Automated logging provides insights into patient flow ✨ Professional Image - Modern, branded health cards improve patient experience 🔒 Secure Records - Cloud storage with organized folder structure 📱 Contactless Check-in - QR codes enable touch-free reception process 🎯 Improved Communication - Multi-channel notifications keep everyone informed 🚀 Scalable System - Handles high volumes without additional staff Required Services & Credentials VerifiEmail API - Email verification service Sign up at: https://verifi.email HTMLCSSToImg API - HTML to image conversion Sign up at: https://htmlcsstoimg.com Google Drive - Cloud file storage Requires: Google Account with Drive access Gmail - Email delivery Requires: Google Account Slack - Team notifications Requires: Slack workspace Google Sheets - Database logging Requires: Google Account Customization Options Change Health Card Design: Edit the "Build Health Card HTML" node Modify CSS styles, colors, layout, fonts Add clinic logo by including `` tag in header Adjust Email Template: Edit the "Email Health Card to Patient" node Customize subject line, message content, styling Add clinic branding and contact information Modify Slack Message: Edit the "Notify Reception Team" node Change message format, add emojis, include additional fields Integrate with different channels Add PDF Generation: Insert an additional HTTP Request node after "Build Health Card HTML" Use a PDF conversion API (like PDFMunk or Puppeteer) Upload both PNG and PDF to Google Drive Add SMS Notifications: Insert Twilio or similar SMS node after email verification Send appointment confirmation via SMS Include patient ID and appointment time Multi-language Support: Modify the HTML template to support multiple languages Add language detection based on patient input Translate email and Slack messages Troubleshooting Guide Email Verification Fails: Check VerifiEmail API key is correct Verify API quota hasn't been exceeded Test with known valid email address Image Generation Fails: Check HTMLCSSToImg API credentials Verify HTML content is valid (no syntax errors) Check API rate limits Google Drive Upload Fails: Re-authenticate Google Drive OAuth2 credentials Check folder permissions Verify folder ID is correct Email Not Sending: Re-authenticate Gmail OAuth2 credentials Check email attachment size limits Verify "Less secure app access" if using password auth Slack Message Not Posting: Check Slack app permissions Verify channel exists and bot is invited Re-authenticate Slack credentials Google Sheets Not Logging: Re-authenticate Google Sheets credentials Verify sheet name and column headers match exactly Check sheet permissions Performance & Scalability Expected Performance: Single execution: 15-20 seconds Concurrent executions: Supports multiple parallel workflows API rate limits: Respects all third-party API limits Volume Handling: Small clinics: <50 patients/day - Perfect Medium practices: 50-200 patients/day - Excellent Large hospitals: 200+ patients/day - Consider API tier upgrades Security & Compliance ✅ Data Privacy - Patient data transmitted securely via HTTPS ✅ Access Control - OAuth2 authentication for all Google services ✅ Secure Storage - Files stored in private Google Drive folders ✅ Audit Trail - Complete logging in Google Sheets with timestamps ✅ Email Verification - Prevents data leakage to invalid addresses ✅ No Data Storage in n8n - Patient data passes through, not stored Tags healthcare, medical, clinic, patient-management, appointment, email-verification, qr-code, google-drive, gmail, slack, automation, workflow, pre-checkin, health-card, verifi-email, htmlcsstoimg, medical-records, patient-portal, healthcare-automation, clinic-management Category Healthcare & Medical Subcategory Patient Management & Appointment Systems License MIT License - Free to use, modify, and distribute with attribution

Free PDF Generator in n8n – No External Libraries or Paid Services > A 100% free n8n workflow for generating professionally formatted PDFs without relying on external libraries or paid converters. It uses OpenAI to create Markdown content, Google Docs to format and convert to PDF, and integrates with Google Drive and Slack for archiving and sharing, ideal for reports, BRDs, proposals, or any document you need directly inside n8n. Watch the demo video below: Who’s it for Teams that need auto-generated documents (reports, guides, checklists) in PDF format. Operations or enablement teams who want files archived in Google Drive and shared in Slack automatically. Anyone experimenting with LLM-powered document generation integrated into business workflows. How it works / What it does Manual trigger starts the workflow. LLM generates a sample Markdown document (via OpenAI Chat Model). Google Drive folder is configured for storage. Google Doc is created from the generated Markdown content. Document is exported to PDF using Google Drive. (Sample PDF generated from comprehensive markdown) PDF is archived in a designated Drive folder. Archived PDF is downloaded for sharing. Slack message is sent with the PDF attached. How to set up Add nodes in sequence: Manual Trigger OpenAI Chat Model (prompt to generate sample Markdown) Set/Manual input for Google Drive folder ID(s) HTTP Request or Google Drive Upload (convert to Google Docs) Google Drive Download (PDF export) Google Drive Upload (archive PDF) Google Drive Download (fetch archived file) Slack Upload (send message with attachment) Configure credentials for OpenAI, Google Drive, and Slack. Map output fields: data.markdown → Google Docs creation docId → PDF export fileId → Slack upload Test run to ensure PDF is generated, archived, and posted to Slack. Requirements Credentials**: OpenAI API key (or compatible LLM provider) Google Drive (OAuth2) with read/write permissions Slack bot token with files:write permission Access**: Write access to target Google Drive folders Slack bot invited to the target channel How to customize the workflow Change the prompt** in the OpenAI Chat Model to generate different types of content (reports, meeting notes, checklists). Automate triggering**: Replace Manual Trigger with Cron for scheduled document generation. Use Webhook Trigger to run on-demand from external apps. Modify storage logic**: Save both .md and .pdf versions in Google Drive. Use separate folders for drafts vs. final versions. Enhance distribution**: Send PDFs to multiple Slack channels or via email. Integrate with project management tools for automated task creation.

Imagine having an AI chatbot on Slack that seamlessly integrates with your company’s workflow, automating repetitive requests. No more digging through emails or documents to find answers about IT requests, company policies, or vacation days—just ask the bot, and it will instantly provide the right information. With its 24/7 availability, the chatbot ensures that team members get immediate support without waiting for a colleague to be online, making assistance faster and more efficient. Moreover, this AI-powered bot serves as a central hub for internal communication, allowing everyone to quickly access procedures, documents, and company knowledge without searching manually. A simple Slack message is all it takes to get the information you need, enhancing productivity and collaboration across teams. How It Works Slack Trigger: The workflow starts when a user mentions the AI bot in a Slack channel. The trigger captures the message and forwards it to the AI Agent. AI Agent Processing: The AI Agent, powered by Anthropic's Claude 3.7 Sonnet model, processes the query. It uses Retrieval-Augmented Generation (RAG) to fetch relevant information from the company’s internal knowledge base stored in Qdrant (a vector database). A Simple Memory buffer retains recent conversation context (last 10 messages) for continuity. Knowledge Retrieval: The RAG tool searches Qdrant’s vector store using OpenAI embeddings to find the most relevant document chunks (top 10 matches). Response Generation: The AI synthesizes the retrieved data into a concise, structured response (1-2 sentences for the answer, 2-3 supporting details, and a source citation). The response is formatted in Slack-friendly markdown (bullet points, blockquotes) and sent back to the user. Set Up Steps Prepare Qdrant Vector Database: Create a Qdrant collection via HTTP request (Create collection node). Optionally, refresh/clear the collection (Refresh collection node) before adding new documents. Load Company Documents: Fetch files from a Google Drive folder (Get folder → Download Files). Process documents: Split text into chunks (Token Splitter) and generate embeddings (Embeddings OpenAI2). Store embeddings in Qdrant (Qdrant Vector Store1). Configure Slack Bot: Create a Slack bot via Slack API with required permissions Add the bot to the desired Slack channel and note the channelId for the workflow. Deploy AI Components: Connect the AI Agent to Anthropic’s model, RAG tool, and memory buffer. Ensure OpenAI embeddings are configured for both RAG and document processing. Test & Activate: Use the manual trigger (When clicking ‘Test workflow’) to validate document ingestion. Activate the workflow to enable real-time Slack interactions. Need help customizing? Contact me for consulting and support or add me on Linkedin.

Build a fully automated music generation workflow in n8n using Suno to create and store AI-generated songs. What's the Goal? Automate end-to-end AI music creation — from a simple text prompt to a fully generated, stored, and shareable song — using Suno's API inside n8n with zero manual effort. Why Does It Matter? AI music generation is powerful but manual. This workflow lets you batch-generate songs, integrate music into apps or content pipelines, and store outputs automatically — saving hours of repetitive work. How It Works Webhook or Schedule triggers the flow with a text prompt Prompt is enriched/formatted for best Suno results Suno API call initiates song generation Workflow polls until song is ready (async wait loop) Song metadata & audio URL retrieved File downloaded and saved to cloud storage (Google Drive / S3) Metadata logged to Google Sheets / Airtable Notification sent via Slack / Email Configuration Requirements Suno API key (via RapidAPI or official Suno API access) Cloud storage credentials (Google Drive / AWS S3) Google Sheets or Airtable credentials (for logging) Slack Bot Token or SMTP (for notifications) Optional: OpenAI API key (for prompt enrichment) Setup Guide Import workflow into n8n Connect credentials (Suno/RapidAPI, Google Drive, Sheets, Slack) Configure Set node: default genre, mood, duration, style tags Test with a manual trigger and a sample prompt Activate webhook → send prompts to trigger URL Monitor generation status and tune polling interval Check storage & logs for generated songs Contact Us https://www.oneclickitsolution.com/contact-us/

Who is it for? This template is designed for school nutritionists, cafeteria managers, and school administrators who are responsible for managing student dietary needs and ensuring food safety. What it does The workflow operates in two main scenarios: immediate allergy alerting and proactive menu analysis. Automated Allergy Alert System: It reads upcoming menus, student allergy lists, and teacher rosters from your Google Sheets. If it finds a potential conflict—like a student with a dairy allergy scheduled for a cheese-based meal—it automatically sends a detailed, AI-generated alert to the correct teacher in Slack and logs the event in Google Drive. Proactive AI Menu Assistant: Beyond daily alerts, the workflow uses AI to analyze the entire monthly menu. It identifies "high-risk" days with numerous potential allergy issues and generates a strategic "Menu Improvement Report" with suggestions for safer, alternative dishes. This report is sent directly to you via Slack, helping you make informed decisions before finalizing the menu. Built-in Error Handling: If any part of the workflow fails, it immediately sends a detailed error notification to an administrator, ensuring the system remains reliable. How to set up Connect Credentials: First, ensure you have created and connected credentials for Google (for Sheets and Drive) and Slack in your n8n instance. Configure Google Sheets Nodes: In the three Read... nodes (Read Monthly Menu, Read Student Allergy List, Read Teacher List), update the Document ID and Sheet Name to point to your specific files. The column structure of your sheets should match the data being used in the workflow. Configure Slack Nodes: In all four Slack nodes, select the correct recipient User or Channel for each type of notification (e.g., send allergy alerts to teachers, but error alerts to your IT admin). Configure Google Drive Node: In the Log Alert to Google Drive node, select the target Drive and Folder where you want your audit logs to be saved. (Optional) Configure AI Model: You can configure the OpenRouter Chat Model nodes if you want to use a specific LLM or add your own API key. Requirements An active n8n instance. A Google account with access to Google Sheets and Google Drive. A Slack workspace and account. An OpenRouter account to power the AI features.

📘 Description: This workflow automates the incident response lifecycle — from creation to communication and archival. It instantly creates Jira tickets for new incidents, alerts the on-call Slack team, generates timeline reports, logs the status in Google Sheets, and archives documentation to Google Drive — all automatically. It helps engineering and DevOps teams respond faster, maintain audit trails, and ensure no incident details are lost, even after Slack or Jira history expires. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Manual Trigger – Start the incident creation and alerting process manually on demand. 🏷️ Define Incident Metadata – Sets up standardized incident data (Service, Severity, Description) used across Jira, Slack, and Sheets for consistent processing. 🎫 Create Jira Incident Ticket – Automatically creates a Jira task with service, severity, and description fields. Returns a unique Jira key and link for tracking. ✅ Validate Jira Ticket Creation Success – Confirms the Jira ticket was successfully created before continuing. True Path: Proceeds to Slack alerts and documentation flow. False Path: Logs the failure details to Google Sheets for debugging. 🚨 Log Jira Creation Failures to Error Sheet – Records any Jira API errors, permission issues, or timeouts to an error log sheet for reliability monitoring. 🔗 Combine Incident & Jira Data – Merges incident context with Jira ticket data to ensure all details are unified for downstream notifications. 💬 Format Incident Alert for Slack – Generates a rich Slack message containing Jira key, service, severity, and description with clickable Jira links. 📢 Alert On-Call Team in Slack – Posts the formatted message directly to the #oncall Slack channel to instantly notify engineers. 📋 Generate Incident Timeline Report – Parses Slack message content to create a detailed incident timeline including timestamps, service, severity, and placeholders for postmortem tracking. 📄 Convert Timeline to Text File – Converts the generated timeline into a structured .txt file for archival and compliance. ☁️ Archive Incident Timeline to Drive – Uploads the finalized incident report to Google Drive (“Incident Reports” folder) with timestamped filenames for traceability. 📊 Log Incident to Status Tracking Sheet – Appends Jira key, service, severity, and timestamp to the “status update” Google Sheet to build a live incident dashboard and enable SLA tracking. 🧩 Prerequisites Jira account with API access Google Sheets for “status update” and “error log” tracking Slack workspace connected via API credentials Google Drive access for archival 💡 Key Benefits ✅ Instant Slack alerts for new incidents ✅ Centralized Jira ticketing and tracking ✅ Automated timeline documentation for audits ✅ Seamless Google Drive archival and status logging ✅ Reduced MTTR through faster communication 👥 Perfect For DevOps and SRE teams managing production incidents Engineering managers overseeing uptime and reliability Organizations needing automated post-incident documentation Teams focused on SLA adherence and compliance reporting

TalentFlow AI – Bulk Resume Screening with JD Matching Automatically extract, evaluate, and shortlist multiple resumes against a selected job description using GPT-4. This smart, scalable n8n workflow helps HR/TA teams streamline hiring decisions while keeping results structured, auditable, and easy to share. 👤 Who’s it for This workflow is designed for: HR or Talent Acquisition (TA) teams handling multiple candidates per role Recruiters who want AI-assisted resume screening to save time and reduce bias Organizations that want to automatically log evaluations and keep stakeholders updated in real-time via Slack or Sheets ⚙️ How it works / What it does HR/TA uploads multiple candidate resumes and selects a job role Each resume is: Uploaded to Google Drive Parsed with GPT-4 to extract structured profile data The job description for the selected role is: Retrieved from Google Sheets Downloaded from Drive and parsed The profile + JD are sent to an AI agent to generate: Fit score Strengths & gaps Final recommendation Results are: Appended to the evaluation tracking sheet Optionally shared with the hiring team on Slack Used to trigger emails to qualified or unqualified candidates 🛠️ How to set up Clone or import the workflow into your n8n instance Connect your integrations: Google Sheets (positions & evaluation form) Google Drive (CV & JD folders) OpenAI API (GPT-4) Slack (for notifications) (Optional) SendGrid or SMTP for email notifications Update Google Sheets structure: Positions sheet: maps Job Role → JD file link Evaluation form: stores evaluation results Prepare Drive folders: /cv folder for uploaded resumes /jd folder for job description PDFs 📋 Requirements ✅ n8n (hosted or self-hosted) ✅ OpenAI GPT-4 account (used in Profile & JD evaluator agents) ✅ Google Drive + Google Sheets access ✅ Slack workspace + bot token (Optional) SendGrid or email credentials for candidate follow-up 🎨 How to customize the workflow Change the fit score threshold in the Candidate qualified? node Edit Slack message content/formatting to match your company tone Add additional candidate metadata to Sheets or Slack messages Use a webhook trigger to integrate with your ATS or job board Swap GPT-4 with Claude or Gemini if you prefer other AI services Expand to include multi-position batch screening logic Happy Hiring! 🚀 Automated with love using n8n

Who is this for? This template is ideal for HR teams, startup founders, operations leads, remote-first companies, and freelancers managing onboarding manually or across multiple tools. Whether you’re hiring your first intern or streamlining onboarding for dozens of new team members, this workflow automates the entire trigger → task creation → onboarding delivery process using no-code tools connected via n8n. What problem does this solve? Employee onboarding is often fragmented and error-prone — involving Jira tasks, Slack DMs, file sharing, and email templates spread across different apps. This workflow connects it all, letting you create tasks, notify people, share folders, and message hires instantly — right when they’re marked as “Hired” in a Google Sheet or added to Slack. No more bouncing between 5 tabs. This is onboarding as a system. What this workflow does ✅ Watches a Google Sheet (or Slack trigger) for new hires 📋 Creates a Jira onboarding Epic with role-based subtasks 📂 Generates a Google Drive folder and shares it with the new hire 📬 Sends a personalized, HTML-formatted welcome email via Gmail 💬 Posts a Slack message in the #onboarding channel + DM to the hire 📊 Logs onboarding activity back to the Sheet (status, links, etc.) 🔁 Modular subtasks based on role/team (e.g. Dev vs Marketing vs Student) 🧠 Expressions, fallback logic, and Slack→Jira user ID mapping built-in Setup Create API credentials for: Slack Google Sheets Google Drive Jira Cloud Gmail (API or SMTP) Import the .json workflow into your n8n instance (Cloud or self-hosted) Replace placeholder values (e.g. Project ID, Issue Type ID, folder path) Customize onboarding messages, email HTML, and task logic Test with included mock data (sample hire, Slack user, Jira user) Activate your flow and start onboarding with one click 🗒 Color-coded workflow notes This workflow uses Innovatio’s sticky note system to guide you visually: 🟩 Green Notes → Main automation steps 🟦 Blue Notes → What to customize (IDs, prompts, expressions) 🟨 Yellow Notes → Optional logic and future upgrades 🟫 Gray Notes → Welcome + final “next steps” CTA Every group includes pre-filled nodes, dynamic expressions, and mock outputs so you can test quickly and scale confidently. How to customize this workflow? 📂 Swap Google Sheets for Airtable (better for teams or approvals) 📅 Add 30/60/90-day check-ins via Google Calendar 🤖 Plug in OpenAI to generate onboarding subtasks by role 📬 Auto-assign mentors or SlackBot reminders after 7 days 📊 Push Sheet logs into Notion or your HR dashboard Need custom logic? Email me at [email protected] Final notes This template was created by Velebit from Innovatio with modularity, scalability, and team experience in mind. All links included are official. No affiliate tracking, no sponsored content. 📜 A separate commercial license applies to the purchase via Gumroad, which includes extended rights, usage for client work, and scaling strategies.

AI Recruitment Automation Pipeline – Resume Parsing, GPT-4 Evaluation, Assessment Triggers & Interview Scheduling This end-to-end AI-powered recruitment automation workflow helps HR and talent acquisition teams automate the complete hiring pipeline—from resume intake and parsing to GPT-4-based evaluation, TA approvals, assessment delivery, and interview scheduling. Built using n8n, this template integrates with OpenAI GPT-4, Google Sheets, Google Drive, Slack, and SMTP to reduce time-to-hire, improve candidate quality, and eliminate repetitive manual tasks. The workflow enables scalable, consistent, and intelligent decision-making by automating resume evaluation, semantic fit analysis, and candidate communication. This template is ideal for recruiters, TA teams, and founders looking to optimize hiring for tech, sales, support, and other roles with high applicant volume. Who is this for? HR and TA teams handling high-volume recruitment Startups and SMBs looking to reduce hiring time and cost Hiring managers seeking to automate CV parsing and candidate evaluation What problem does this solve? Eliminates manual resume screening Sends real-time updates to TA team on assessment completion Automates assessments, scoring, and interview scheduling Keeps candidate communication consistent and timely What this workflow does Smart Resume Intake Form Collects candidate data: name, email, phone, LinkedIn, job role, and CV (PDF). Custom-designed UI with branding-ready CSS. PDF Resume Parsing & Storage CV is uploaded to a dedicated Google Drive folder. Resume text is extracted for semantic analysis. AI-Based Candidate Evaluation (GPT-4 via LangChain) Extracts: City, Education, Job History, Skills. Summarizes candidate profile (100 words). Retrieves and summarizes job description from Google Sheets. Performs detailed evaluation: ✅ Semantic fit scoring (0–100%) ✅ Key matches and skill gaps ✅ Soft skills extraction ✅ Red flag detection (job-hopping, missing info) ✅ Final score (1–10) with rationale Google Sheets Integration Logs and updates candidate data at each stage: CV Submitted → Scored → Shortlisted → Assessment Sent → Interview Scheduled → Rejected TA Approval via Email (Send & Wait) TA receives evaluation summary and gives one-click approve/reject. ✅ Approved → Status: Resume Selected ❌ Rejected → Status: Resume Rejected Assessment Trigger (Post Approval) Sends assessment link to shortlisted candidates. Notifies TA via Slack and Email when assessment is submitted. Interview Scheduling Sends Calendly link for self-scheduled interview booking. Candidate receives detailed next-step instructions. Status-Based Candidate Emails Automatically sends: ✔️ Shortlisting confirmation + interview setup ❌ Rejection email with branded message Business Benefits Save 80%+ time** spent on manual resume reviews and coordination Reduce cost-per-hire** by eliminating manual tasks Improve hiring accuracy** with structured, AI-based decision-making Scalable recruitment** for 100s of candidates per week Enhance candidate experience** with instant status updates Centralize data** in Google Sheets for full team visibility 🔧 Setup Instructions Google Service Account Setup (One-Time) Before using Google Sheets or Google Drive in n8n: Go to Google Cloud Console. Create a Service Account under your project. Enable these APIs: Google Sheets API Google Drive API Download the JSON credentials for the service account. IMPORTANT: Share your target Google Sheets and Docs with the service account email (e.g., [email protected]). Add Applicant's Details to Google Sheet Document**: Select the Profiles Google Sheet document. Sheet**: Select the Applicant's Details sheet. Fields to Map**: EMAIL: {{ $('On form submission').item.json.Email }} DATE: {{ $now.format('dd-MM-yyyy') }} NAME: {{ $('On form submission').item.json.Name }} LINKEDIN URL: {{ $('On form submission').item.json["LinkedIn Profile URL"] }} JOB PROFILE: {{ $('On form submission').item.json["Job Openings"] }} STATUS: CV SUBMITTED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Extract Applicant's Resume Text Text**: {{ $('Extract from File').item.json.text }} Get Job Description from Google Sheet Document**: Profiles Sheet**: Job Openings Filter**: Column**: Job Profile Value**: {{ $('On form submission').item.json["Job Openings"] }} Save Evaluation Results in Google Sheets Document**: Profiles Sheet**: Applicant's Details Column Match On**: EMAIL Fields to Map**: EMAIL: {{ $('On form submission').item.json.Email }} CITY: {{ $('Applicant\'s Details').item.json.output.City }} EDUCATIONAL: {{ $('Applicant\'s Details').item.json.output["Educational Qualification"] }} JOB HISTORY: {{ $('Applicant\'s Details').item.json.output["Job History"] }} SKILLS: {{ $('Applicant\'s Details').item.json.output.Skills }} SUMMARIZE: {{ $('Summarize Applicant\'s Profile').item.json.response.text }} SEMANTIC FIT SCORE: {{ $json.output.semantic_fit.score }} KEY MATCHES: {{ $json.output.semantic_fit.key_matches.toJsonString() }} KEY GAPS: {{ $json.output.semantic_fit.key_gaps.toJsonString() }} SEMANTIC FIT CONSIDERATION: {{ $json.output.semantic_fit.consideration }} SOFT SKILLS: {{ $json.output.soft_skills.toJsonString() }} EXPERIENCE GAP DETECTED: {{ $json.output.experience_analysis.experience_gap_detected }} OVER QUALIFICATION DETECTED: {{ $json.output.experience_analysis.overqualification_detected }} EXPERIENCE ANALYSIS CONSIDERATION: {{ $json.output.experience_analysis.consideration }} RED FLAGS ISSUES DETECTED: {{ $json.output.red_flags.issues_detected.toJsonString() }} RED FLAGS CONSIDERATION: {{ $json.output.red_flags.consideration }} VOTE: {{ $json.output.overall_evaluation.final_vote }} FINAL CONSIDERATION: {{ $json.output.overall_evaluation.consideration }} STATUS: CV SCORED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Update Applicant Statuses Resume Selected Document**: Profiles Sheet**: Applicant's Details Column Match On**: EMAIL Update**: STATUS: RESUME SELECTED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Resume Rejected Update**: STATUS: RESUME REJECTED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Assessment Sent Email**: {{ $('Loop to Send Assessment Link to Each Candidate').item.json.EMAIL }} Update**: STATUS: ASSESSMENT SENT LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Assessment Submitted Email**: {{ $json["Enter Your Email Address"] }} Update**: STATUS: ASSESSMENT SUBMITTED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Interview Booked Email**: {{ $json.payload.email }} Update**: STATUS: INTERVIEW BOOKED LAST UPDATED DATE: {{ $now.format('dd-MM-yyyy hh:mm:ss') }} Fetch Applicants with Specific Status Status: RESUME SELECTED Document**: Profiles Sheet**: Applicant's Details Filter**: Column**: STATUS Value**: RESUME SELECTED Get Assessment Form URL from Job Profile Document**: Profiles Sheet**: Job Openings Filter**: Column**: Job Profile Value**: {{ $json["JOB PROFILE"] }} Trigger on Applicant Status Update Document**: Profiles Sheet**: Applicant's Details Trigger Settings**: Columns to Watch**: STATUS ⚠️ Important Notes Always use “Select Document from List” instead of manually pasting the sheet/document ID. Share your Sheets/Docs with the Google Service Account email for proper access. Keep your date formats consistent using {{ $now.format('dd-MM-yyyy hh:mm:ss') }}. Add credentials for: Google Drive Google Sheets SMTP (for emails) OpenAI API Key (GPT-4) Replace placeholders: Google Sheet & Folder IDs Calendly Link Assessment Link (Optional) Customize GPT-4 prompts for domain-specific scoring (Optional) Use your Slack webhook for TA notifications 🛠️ Tools & Integrations Form Trigger** – Candidate form with file upload Google Drive + Extract PDF** – CV parsing Google Sheets** – Database for all applicant statuses LangChain GPT-4 Nodes** – AI profile + job analysis Email Send & Send & Wait** – Candidate/TA communication IF Node** – Logic for approve/reject Slack Integration** – TA notification Calendly Link** – Interview scheduling AI resume screening, GPT-4 recruitment workflow, automated hiring pipeline, semantic fit evaluation, LangChain for HR, resume parsing automation, AI in talent acquisition, assessment workflow automation, interview scheduling automation, candidate shortlisting automation, OpenAI HR integration, Google Sheets recruitment tracker, n8n HR automation template, self-scheduling interviews with Calendly, Slack notifications in recruitment

🧾 An intelligent automation system that turns Google Meet recordings into structured meeting notes — integrating Fireflies.ai, OpenAI GPT-4.1-mini, Notion, Slack, Google Drive, and Gmail via n8n. 🎥 Demo: Watch the Loom walkthrough ⚙️ What It Does The Google Meet Notes Generator & Distributor automates the entire post-meeting workflow. Workflow Summary: Fetches Google Meet transcript via Fireflies.ai webhook. Aggregates and summarizes transcript using OpenAI GPT-4.1-mini into: Title Summary Decisions Action Items Risks Questions Stores the transcript as a text file on Google Drive and generates a shareable link. Creates a Notion page with all the meeting details. Posts the summary in #meeting Slack channel. DMs each attendee on Slack with personalized meeting notes. Sends email recap to all attendees via Gmail. Result: No more manual note-taking or scattered updates — everything centralized, formatted, and instantly shareable. 💡 Use Cases | Scenario | Description | | --------------------------- | --------------------------------------------------------------------------------------- | | Team Meeting Summaries | Automatically summarize and distribute meeting notes for internal teams. | | Project Management | Keep structured decisions, action items, and risks documented for each project meeting. | | Remote Teams | Notify distributed teams in Slack and via email without extra effort. | | Client Updates | Share polished meeting summaries with clients instantly. | | Knowledge Base / Notion | Archive structured notes in Notion for reference and compliance. | 🔧 Setup Accounts and Tools Needed | Tool | Purpose | | -------------------------- | ---------------------------------------------- | | 🤖 Fireflies.ai API | Fetch Google Meet transcripts via webhook | | 🧠 OpenAI API | Summarize and structure transcript into notes | | 📓 Notion API | Create structured meeting pages | | 💬 Slack OAuth/Bot | Post summaries in channel and DM attendees | | 🗂 Google Drive OAuth2 | Store transcripts and generate shareable links | | ✉️ Gmail OAuth2 | Email meeting recaps to attendees | Fireflies.ai Setup Get API key from Fireflies.ai. Configure n8n → Credentials → Fireflies API. Ensure webhook triggers are set to send meetingId to n8n. OpenAI Setup Generate API key at OpenAI. Add to n8n → Credentials → OpenAI API. Use model GPT-4.1-mini in Agent and Generate Slack Message nodes. Notion Setup Create a Notion integration and share your workspace. Add API token in n8n → Credentials → Notion API. Map workspace/page IDs to Notion Page node. Slack Setup Create Slack Bot in workspace with chat:write and users:read permissions. Add OAuth token in n8n → Credentials → Slack API. Connect to Send a message #meeting and DMs to Attendees nodes. Google Drive Setup Create a folder for transcripts. Enable Google Drive API in Google Cloud Console. Add OAuth2 credentials to n8n → Google Drive. Gmail Setup Enable Gmail API in Google Cloud. Add OAuth2 credentials in n8n → Gmail. Connect to Email to Attendees node. n8n Workflow Setup Import provided n8n workflow JSON. Configure all credentials: Fireflies, OpenAI, Notion, Slack, Google Drive, Gmail. Activate workflow. Test by sending a meeting ID via webhook. Workflow automatically: Fetch → Summarize → Store → Notion → Slack → DM → Email 🧠 Result A fully automated AI pipeline that transforms Google Meet recordings into polished, shareable meeting notes — eliminating manual note-taking and keeping your team informed in real time. 📞 Support & Contact If you face any issues during setup or execution, contact: 📧 Email: [email protected] 🔗 LinkedIn: Atharva Jaiswal

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Automatically transform your video uploads into AI-powered summaries with key topic extraction and instant team notifications. What this workflow does Monitors Google Drive for new video uploads Downloads and processes videos using VLM Run AI Generates intelligent summaries with key topics extracted Posts results to Slack for immediate team access Setup Prerequisites: Google Drive account, VLM Run API credentials, Slack workspace, self-hosted n8n. You need to install VLM Run community node Quick Setup: Configure Google Drive OAuth2 and create video upload folder Add VLM Run API credentials Set up Slack integration for notifications Update folder/channel IDs in workflow nodes Test and activate Perfect for Meeting recordings and training videos Webinar summaries and educational content Content analysis and team collaboration Any video content requiring quick insights Key Benefits Asynchronous processing** handles large files without timeouts Multi-format support** for MP4, AVI, MOV, WebM, MKV Instant team updates** via Slack notifications Saves hours** of manual video review time How to customize Extend by adding: Video categorization and tagging Integration with project management tools Email notifications alongside Slack Searchable video databases with summaries This workflow transforms lengthy videos into actionable insights, making your content instantly accessible and shareable with your team.

Generate and post Apple App Store review replies with Anthropic Claude, Google Drive and App Store Connect API This workflow empowers app developers and community management teams by automating the generation and posting of responses to user reviews on the Apple App Store. Designed to streamline the engagement process, it drastically reduces the manual workload on community managers by integrating AI-driven responses with necessary human oversight. By leveraging n8n's workflow automation capabilities, this solution eliminates the need for costly third-party platforms like AppFollow or Appbot, making it a cost-effective and efficient alternative. Pre-requisites Google Drive & Google Sheets access: To store and manage review spreadsheets. App Store Connect API credentials: To fetch and respond to app reviews. LLM credentials (e.g., Anthropic): Required for generating responses. Slack account Workflow steps Initialise and trigger workflow: The process begins daily at 10 AM through a scheduled trigger. Fetch application data: Utilizes a data table (Apple App Store apps) to retrieve a list of applications with their app id and name, essential for identifying review sources. Collect App Store Reviews: Retrieves previous day's reviews from the App Store Connect API based on app data. Stores the reviews in Google Sheets for further processing. Generate AI Responses: AI model generates initial responses based on review content. Responses are structured and stored along with reviews within a Google Spreadsheet located in a Google Drive folder called ToReview. A Slack message is sent with the URL of the file Human Review & Modification: Community managers review and refine AI-generated responses. Reviewed spreadsheets are moved to the ToSubmit Google Drive folder by the editor. Post Verified Responses: Workflow triggers again at 5 PM to access reviewed spreadsheets in ToSubmit folder. It posts the human-verified responses back to the respective reviews on Apple App Store using App Store Connect API. Logs are maintained, recording each response's success or failure. Archive processed spreadsheets: After posting the responses, workflow moves the processed files from ToSubmit to a different folder called Archived

CV Extractor: Google Drive to Sheet + Slack Update for Recruiters Watch the demo video below: > This workflow automatically processes resumes (PDFs) uploaded or updated in a Google Drive folder. It extracts and structures the candidate’s information using AI, then updates or inserts the data into a Google Sheet, acting as a central talent database. Finally, it notifies the hiring team via Slack with a summary. Perfect for HR and TA teams, this automation eliminates the repetitive task of manually copying candidate details from CVs into spreadsheets, saving hours of admin work every week and keeping your hiring pipeline clean, fast, and up to date. 👤 Who’s it for This workflow is designed for: Recruiters* and HR coordinators* who manage candidate profiles via Google Drive. Talent Acquisition teams** who want to automate CV parsing, enrichment, and database updating. Companies or hiring agencies** using spreadsheets for candidate tracking and CRM-like HR ops. ⚙️ How it works / What it does This smart and fully automated workflow: Monitors a Google Drive folder for any uploaded or updated resumes (PDFs). Downloads and extracts resume content using PDF parsing. Sends the raw text to GPT-4, which returns a structured profile (name, title, experience, skills, etc.). Verifies the profile and transforms it into a clean, row-based format. Upserts the candidate profile into a Google Sheet (insert or update by email). Notifies the hiring team in Slack or email that a profile was added or updated. This is a no-touch pipeline to keep your candidate data clean, current, and centralized. 🛠️ How to set up Step 1: Prepare your Google Drive folder Create a folder like /SmartHR/cv/ Upload sample resumes in .pdf format Step 2: Create your Google Sheet Columns to include: Email, FullName, JobTitle, Phone, Location, Experience, Education, Skills, etc. Optional: Add conditional formatting to highlight updates Step 3: Connect the n8n workflow Use the Google Drive Trigger: fileCreated → new profile uploaded fileUpdated → existing profile modified Use Google Drive (Download file) to fetch the resume Use Extract From PDF to get raw content Step 4: Configure GPT-4 node Use the structured system prompt to extract profile information Use json parser node to ensure safe formatting for next steps Step 5: Transform & Save Use a Function node to map fields to Google Sheet columns Use Append or update row (based on email as unique key) Optionally send Slack or email message to notify hiring team ✅ Requirements 🔑 OpenAI GPT-4 API key 🟩 n8n Cloud or Self-hosted with: Google Drive integration Google Sheets integration Email/Slack credentials (optional) 📄 Resume files in readable PDF format 📊 Google Sheet prepared with relevant headers ✏️ How to customize the workflow | Part | Customization Options | |----------------------------|----------------------------------------------------------------------------------------| | GPT Prompt | Tune for different job levels or fields (e.g., engineers vs marketers) | | Field Mapping | Update transform node to include other profile fields (LinkedIn, portfolio, etc.) | | Notification | Switch to Microsoft Teams, Telegram, or email alerts instead of Slack | | Data Store | Replace Google Sheet with Airtable, Notion, or database system | | Trigger Source | Trigger from email attachments or webhook instead of Google Drive if needed | | Output Format | Generate PDF profile cards or summary documents using HTML → PDF node |

Say Goodbye to Manual Prospect Research! Imagine walking into every discovery call fully prepared with company background, recent news, and perfectly tailored questions, without spending a single minute prepping. This AI-powered workflow connects to your Google Calendar, looks for upcoming discovery calls, sends an AI out to do deep web research on your prospects, and drops a neat briefing right into Slack and Google Drive. By fully automating the research phase, you get over 45 minutes of your life back per call. Why You'll Love This Workflow Get your time back:** Cuts prep time from 45 minutes to zero. Save money:** No need to pay for pricey sales intelligence tools or hire virtual assistants just to google companies. Zero duplicates:** It’s smart enough to remember which calls it’s already prepped for, so you won't get annoyed by duplicate alerts. Built to scale:** Whether you have 1 call tomorrow or 20, the prep quality stays exactly the same. Who Is This For? Sales Reps (AEs & SDRs):** Nail those high-stakes discovery calls with automated background checks and news updates. Founders & Consultants:** Spot pain points and company growth signals before you even say "hello" to position your services better. Agency Ops Teams:** Standardize how your team preps and automatically organize all client data neatly into Google Drive folders. How The Magic Happens The Kickoff: Every day at 4:00 PM, the automation wakes up to prep for tomorrow's meetings. Finding the Meetings: It grabs all your upcoming events from Google Calendar. Filtering: It specifically looks for keywords (like "discovery" or "call") and ignores any meetings it has already researched for you. The AI Researcher: An AI agent uses Firecrawl to scour the web, read the company’s website, and dig up recent news, leadership changes, and funding info. Filing It Away: The workflow creates a dedicated client folder in Google Drive (or finds the existing one) and saves a structured research doc. The Ping: You get a handy summary in your #ops Slack channel with the brief and a direct link to the Drive folder. What You Need to Get Started n8n instance (The engine that runs the automation) Google Calendar (To find your meetings) OpenAI API (The brain doing the research) Firecrawl API (For reading websites) Google Drive (For saving the docs) Slack (For sending you alerts) Easy Setup Steps Import the JSON file to your n8n instance. Connect your accounts: Log into your Google, OpenAI, Firecrawl, and Slack accounts so the workflow has permission to do its job. Tell it where to put things: In the Search Client Folder node, pick your main "CLIENTS" Drive folder. In the Notify Ops Channel node, pick the Slack channel you want the alerts to go to. Tweak the keywords: If you call your meetings something specific (like "Intro" or "Demo"), update the keywords in the Extract Call Details node. Give it a test run: Trigger the workflow manually to make sure it catches a test event and generates a brief! Make It Your Own The Basics: Change the trigger words to match how you name your meetings. Adjust the timer! If you'd rather have the briefs run at 6:00 AM instead of 4:00 PM, just change the schedule node. Take It to the Next Level: LinkedIn Sync:** Add a tool like Proxycurl to pull the prospect's actual LinkedIn profile. CRM Integration:** Have it drop the notes directly into Salesforce or HubSpot instead of just Google Drive. Email Delivery:** Set it up to email the brief to you 15 minutes before the meeting starts. Quick Troubleshooting Not finding any events?** Make sure your calendar invites actually have the trigger words in the title. Research coming up blank?** If the prospect used a personal @gmail.com email to book, the AI won't be able to scan a company website. Getting duplicates?** If you restart or move your n8n instance, it might "forget" what it already researched. Created by: Khairul Muhtadin | Khaisa Studio Category: Sales & CRM | Tags: AI Agent, Google Workspace, Slack, Research, Automation Need custom workflows? Contact us Connect with the creator: Portfolio • Store • LinkedIn • Medium • Threads

How it works Triggered every 4 hours (or manually) to check all active products in Google Sheets Each product is evaluated for stock level and urgency against its reorder threshold Products with sufficient stock are skipped; duplicate daily orders are prevented OpenAI generates a professional Purchase Order message for products needing reorder PO is posted to a Slack channel; inventory sheet is updated and reorder log appended A summary report is posted to Slack after each full run An error handler sends a Slack alert if anything fails Set up steps Estimated time: ~15 minutes Add your OpenAI API key; connect Slack and Google Sheets via OAuth2 Create a Google Sheet with a Products tab and a Reorder Log tab (column names in setup sticky note) Select your spreadsheet in all Google Sheets nodes Select your Slack channels in the three Slack nodes Activate the workflow

How it works New hire submits an onboarding form with their details Groq AI generates personalised welcome content, Slack messages, and IT access request Welcome email sent to the new hire via Gmail Automated emails sent to HR, the manager, and IT team Company Policy and Employee Handbook PDFs downloaded from Drive and attached Slack messages posted to #general and #hr-team channels Onboarding record appended to Google Sheets tracker Set up steps Estimated time: ~15 minutes Connect Groq API, Gmail, Slack, Google Drive, and Google Sheets credentials Upload your Policy and Handbook PDFs to Drive and link them in the Download nodes Select your Slack channels in the two Slack nodes Select your onboarding Google Sheet in the Append row node Activate the workflow and share the form link with new hires

RFP Automation Workflow with Google Drive, Groq AI (LLaMA 3), Salesforce & Slack > Automate Your Entire RFP Lifecycle This workflow automatically detects new RFP documents uploaded to Google Drive, extracts key requirements using Groq AI (LLaMA 3), generates a complete proposal draft, stores it in Google Docs, creates a Salesforce opportunity, assigns a review task and notifies your team via Slack. Quick Implementation Steps Connect your Google Drive, Groq API, Salesforce, Google Docs and Slack accounts in n8n Set your RFP Intake Folder ID in the trigger node Set a separate Knowledge Base folder for past proposals Customize your company profile in the AI proposal generator node Activate the workflow Upload an RFP → Everything runs automatically What It Does This workflow fully automates the end-to-end process of handling RFP (Request for Proposal) documents. When a new file is uploaded to a specific Google Drive folder, the workflow immediately triggers and downloads the document. It then extracts text from the file and prepares structured metadata such as file name, URL and timestamp. Using Groq-powered AI (LLaMA 3), the workflow analyzes the document and converts unstructured RFP content into structured JSON data. This includes critical fields like client name, project scope, deadlines, budget, technical requirements and evaluation criteria. The workflow ensures that even imperfect AI outputs are safely parsed and normalized. Next, the workflow enhances proposal quality by referencing past proposals stored in a separate knowledge base folder. It then generates a complete, professional proposal draft tailored to the extracted requirements. Finally, it stores outputs in Google Docs and Salesforce, assigns a review task and notifies the team via Slack—ensuring no RFP is missed and every response is standardized. Who It's For IT services companies handling frequent RFP submissions Consulting firms responding to client proposals Digital agencies managing multiple bids Sales and business development teams Enterprises looking to standardize proposal creation Requirements To use this workflow, you need: n8n account (self-hosted or cloud) Google Drive account** RFP Intake Folder Knowledge Base Folder (past proposals) Groq API Key** Salesforce account** Opportunity + Task access Google Docs account** Slack workspace** How It Works & Set Up Step 1: Google Drive Trigger Setup Configure Watch RFP Upload Folder node Replace with your RFP Intake Folder ID Trigger: fileCreated Step 2: File Processing The workflow: Downloads the uploaded file Extracts text (PDF supported) Prepares metadata (file name, ID, URL, timestamp) Step 3: AI Requirement Extraction Configure Groq API credentials Model used: llama-3.3-70b-versatile Extracts structured data such as: Client name Project scope Budget & deadlines Technical requirements Step 4: Clean & Parse Output Code node ensures: JSON is valid Markdown artifacts are removed Fallback structure is used if parsing fails Step 5: Knowledge Base Integration Configure Fetch Past Proposals (KB) node Replace with your separate Knowledge Base folder ID Fetches previous proposal documents for reference Step 6: AI Proposal Generation Uses extracted requirements + KB context Generates a full proposal with sections: Executive Summary Solution Timeline Pricing Team Customize company details inside prompt Step 7: Output Storage Saves proposal to Google Docs Creates Salesforce Opportunity with: Name Deadline Value Description Step 8: Task Creation & Notification Creates a Salesforce Task for review Sends notification to Slack channel How To Customize Nodes AI Nodes Change model (e.g., Mixtral, LLaMA variants) Adjust temperature: 0.1 → structured extraction 0.7 → creative writing Proposal Generator Update: Company name Services Strengths Modify proposal sections if needed Salesforce Node Map custom fields (e.g., Industry__c) Adjust stage names or pipeline stages Slack Node Change channel (#general) Customize notification message Add-Ons You can extend this workflow with: Email notifications (Gmail/Outlook) Approval workflows before submission PDF export of proposal CRM enrichment (HubSpot, Zoho) AI scoring for win probability Auto-deadline reminders Use Case Examples Automatically respond to government RFPs IT companies generating proposals for software projects Agencies handling multiple client bids daily Consulting firms standardizing proposal quality Sales teams tracking opportunities with zero manual entry There can be many more use cases depending on your business workflow and automation needs. Troubleshooting Guide | Issue | Possible Cause | Solution | |------|--------------|---------| | Workflow not triggering | Incorrect folder ID | Verify Google Drive folder ID | | No text extracted | Unsupported file format | Use PDF format | | AI output parsing fails | Unexpected AI response | Check logs in "Clean & Parse AI Output" node | | Salesforce error | Missing custom fields | Remove or create fields in Salesforce | | Proposal not saved | Google Docs credentials issue | Reconnect Google Docs API | | Slack message not sent | Wrong channel or credentials | Verify Slack integration | Need Help? If you need help setting up, customizing or scaling this workflow, our n8n workflow development team at WeblineIndia is happy to help. We can help you: Customize AI prompts for your business Integrate additional CRMs or tools Build advanced automation pipelines Optimize proposal quality using AI Reach out to WeblineIndia for expert support and tailored automation solutions.

💡 What this workflow does Type #Audit https://clientsite.com in Slack. Walk away. Get a professional PDF report and a structured Excel fix sheet delivered to Google Drive and posted back in your Slack thread — fully automated, zero manual work. Built for SEO agencies and freelancers who deliver technical audits at scale. 👇 Check out the deliverables: 📄 View Sample PDF Report 📊 View Sample Excel Fix Sheet 📦 What You Get 20–50 page PDF report:** Includes a health score, Core Web Vitals, broken links, On-Page SEO, issue cards with fix explanations, a priority action plan, and an SEO glossary. Excel fix sheet:** 18 tabs (one per issue type), containing every URL and exact fix instructions — ready to hand off to a developer. Cloud Storage:** Both files are saved to your Google Drive /SEO Audits folder automatically. Slack Delivery:** Links to the generated files are posted directly back into your original Slack thread. ⚙️ How It Works A Slack message containing #Audit and a URL triggers the workflow. A POST request starts the crawl via your self-hosted Screaming Frog CLI API (built with Python + FastAPI, exposed publicly through a Cloudflare Tunnel — no static IP needed). The workflow polls the API every 2 minutes until the status is done, timeout, or failed. The crawl ZIP is downloaded and decompressed, triggering two simultaneous branches: Branch A (Executive Report): SEO Audit Parser → PageSpeed Insights → PSI Parser → Report Builder → HTML to PDF → Google Drive. Branch B (Developer Sheet): Full Data Parser → Tab Builder → Excel File Builder → Google Drive. Both Google Drive links are merged, logged to a Google Sheet, and posted back into the Slack thread. 🛠️ Key Technical Features Streaming CSV Parser:** Easily handles large crawl files up to 500MB without causing timeouts or memory crashes. Smart File Optimization:** Auto-skips massive all_inlinks.csv and all_anchor_text.csv files (reduces the unzipped payload from 450MB to 15MB). Advanced 403 Error Logic:** Splits 403 errors into three actionable categories: Your own site blocking the crawler (WAF/Cloudflare) Known bot-blocked platforms (Twitter, Wikipedia) Unknown external links requiring a manual check Archive Page Filtering:** Removes tags, pagination, feeds, and search pages from all issue counts so your data isn't skewed. Dynamic Health Score (0–100):** Algorithmically weighted by critical vs. warning issues. Universal CMS Support:** Works flawlessly with WordPress, Blogger, Shopify, and any other crawlable CMS. 📋 What You Need | Requirement | Notes | | :--- | :--- | | Screaming Frog SEO Spider | Licensed version (£199/year) required | | SF CLI API (Python/FastAPI) | Not included in this template — Contact creator below | | Cloudflare Tunnel | Free — exposes your local API publicly | | Google PageSpeed API Key | Free from Google Cloud Console | | PDF Conversion Service | Workflow is pre-configured for pdfendpoint.com | | Google Drive & Sheets | OAuth2 credentials for file storage and audit logging | | Slack | OAuth2 credentials for the trigger and delivery | | n8n (Self-Hosted) | Recommended for long execution times | ⚠️ Required n8n Environment Variables To ensure the workflow can process large sites without timing out, add these to your n8n .env file: N8N_DEFAULT_BINARY_DATA_MODE=filesystem EXECUTIONS_TIMEOUT=7200 N8N_RUNNERS_TASK_TIMEOUT=7200 NODE_OPTIONS=--max-old-space-size=8192 🚀 Quick Setup API Setup: Deploy the SF CLI API on your Windows machine/server and expose it via Cloudflare Tunnel. Link the Crawler: Update the Start Crawl node URL and Bearer token with your tunnel URL and API secret. PageSpeed Insights: Replace the PSI API key in the Page Speed Insights HTTP node with your own. Cloud Storage: Set your Google Drive Folder ID in both upload nodes, and your Google Sheets Spreadsheet ID in the Append row node. Branding: In the Report Builder code node, update the AGENCY config object (around line 125) with your name, email, and tagline. In the Input Cleaner node, set the watermark value to your agency's name. 📞 Support & Custom API Access Note: The custom Python/FastAPI backend required to orchestrate Screaming Frog is not included in this JSON template. If you want to set up the complete system, please reach out: 📧 Email:[email protected] 🔗 LinkedIn: Salman Mehboob

This template gives your HR or operations team an AI-powered Slack bot that answers employee questions about internal policies — directly in DM, available to everyone in the workspace, with no per-user setup required. Employees simply send a direct message to the bot. It searches your Google Drive HR documents using RAG (Retrieval-Augmented Generation) via Pinecone, and replies in the same thread using GPT-4.1 — based strictly on your documents, not general knowledge. Who this is for HR, operations, and IT teams who want to reduce repetitive policy questions (leave, expenses, remote work, etc.) without building a custom chatbot from scratch. What's included This template contains two workflows on a single canvas: HR Document Indexer — Runs daily at 3:00 AM. Indexes all documents in a specified Google Drive folder into Pinecone automatically. HR QA Bot — Listens for Slack DMs workspace-wide. Filters out bot messages to prevent infinite loops, retrieves relevant document chunks, generates an answer, and replies in-thread. A built-in RAG quality evaluator automatically scores every response (faithfulness & answer relevancy) and logs results to Google Sheets for continuous quality monitoring. Key features Works for the entire Slack workspace with a single setup — no per-user configuration Strictly document-grounded answers — the bot will not hallucinate outside your documents Infinite loop prevention via bot_id filtering Automatic daily re-indexing with duplicate prevention (namespace clear before upsert) Built-in answer quality logging to Google Sheets Prerequisites Google Drive folder with HR documents (txt, pdf, docx) Pinecone account (index: dimension 1536, metric cosine) OpenAI API key Slack App with DM permissions (setup guide included in the workflow) Google Sheets (copy link provided in the workflow)

Who's it for Small teams, solo operators, and security-conscious individuals who receive email attachments from external senders. Useful for freelancers, agencies, HR teams, and anyone handling CVs, invoices, or documents from unknown sources. How it works Every minute, the workflow polls Gmail for new unread emails with attachments. For each attachment, it calculates the SHA256 hash and queries VirusTotal for known-malware matches. In parallel, an AI model analyzes the email subject and body for phishing patterns. A rule-based scorer combines both signals into three threat levels: Danger (VirusTotal malicious count >= 3 OR AI detects phishing) triggers a Gmail quarantine label plus a Slack alert. Suspicious (partial hits) logs to a human review queue in Google Sheets. Safe saves the attachment to Google Drive. AI is used only for text classification — the final quarantine decision is always rule-based. Set up steps Get a free VirusTotal API key at virustotal.com Create a Google Sheet named suspicious_queue with columns: timestamp, email_from, email_subject, attachment, malicious_count, ai_verdict Create a Gmail label called QUARANTINE and a Google Drive folder for safe attachments Open Set Configuration and fill in the Sheet ID, Drive folder ID, Slack channel, and label name Connect Gmail, Sheets, Drive, Slack, OpenAI, and VirusTotal (Header Auth with x-apikey) credentials Activate the workflow How to customize Adjust thresholds in the Code node, swap Slack for Discord or Teams, or add SPF and DKIM header checks before scanning.

This AI-powered workflow transcribes Zoom/Google Meet recordings, extracts decisions and tasks using AI, then creates tickets in Jira/ClickUp/Linear and assigns them to team members automatically. How it works Trigger - Receives meeting recording URL via webhook or schedule Download Recording - Fetches audio/video file from Zoom/Google Meet Audio Extraction - Converts video to audio if needed using FFmpeg Transcription - Uses Whisper API to transcribe meeting audio Wait & Process - Allows transcription to complete Parse Transcript - Cleans and formats the transcription text AI Analysis - Claude extracts action items, decisions, owners Team Member Matching - Maps names to user IDs in project tools Create Tasks - Generates tickets in Jira/ClickUp/Linear Assign & Notify - Assigns tasks to team members and sends notifications Meeting Summary - Saves full summary to Google Drive/Notion Response - Returns processed action items and task links Setup Steps Import this workflow into your n8n instance Configure credentials: Zoom OAuth - For downloading Zoom recordings Google OAuth - For Google Meet recordings and Drive storage OpenAI API - For Whisper transcription service Anthropic API - For Claude AI analysis Jira/ClickUp/Linear API - For task creation Slack/Teams - For notifications (optional) Set up team member mapping in the config node Configure your project management tool preferences Activate the workflow Sample Trigger Payload { "meetingSource": "zoom", "recordingUrl": "https://zoom.us/rec/share/...", "meetingTitle": "Q1 Planning Meeting", "meetingDate": "2024-01-15", "attendees": ["[email protected]", "[email protected]", "[email protected]"], "projectKey": "PROJ-123", "taskTool": "jira", "defaultPriority": "medium", "autoAssign": true, "sendNotifications": true, "saveToNotion": false, "saveToDrive": true, "extractDecisions": true, "extractRisks": true, "dueDate": "2024-01-22" } Features Multi-platform support** (Zoom, Google Meet, MS Teams recordings) Accurate transcription** using OpenAI Whisper API AI-powered extraction** of action items, decisions, risks, and next steps Automatic task creation** in Jira, ClickUp, or Linear Smart assignment** - maps attendee names to task assignees Meeting summaries** - saves comprehensive notes to Drive/Notion Slack/Teams notifications** - alerts team members of new tasks Duplicate detection** - prevents creating duplicate tickets Priority detection** - AI assigns urgency levels to tasks

What This Workflow Does Monitors incoming invoice emails and catches extraction failures before they slip through. When easybits Extractor can't extract the invoice number from an attachment, the workflow sends a Slack alert to finance so nothing gets lost. Successfully extracted invoices are archived to Google Drive – only clean, validated files land there. How It Works Gmail Trigger – Polls for new emails with attachments every minute Extraction – The attachment is sent to easybits Extractor Validation – An IF node checks if invoice_number was successfully extracted On failure – A Slack alert is sent to finance for manual review On success – The file is merged back with its extracted data and archived to Google Drive Why This Matters Extractor returns null when it can't confidently identify a data point – which is the right behavior (better than hallucinating a value). But without a safety net, those nulls can propagate into your Sheets, your approval flow, or your accounting system. This workflow makes silent failures visible. Setup Guide Set Up Your easybits Extractor Pipeline Go to extractor.easybits.tech and create a pipeline for invoice extraction Make sure your pipeline includes an invoice_number field (this is the field the validation step checks) Click "Auto-Map Fields" to let the Extractor suggest fields from a sample invoice, then review and save Copy your Pipeline ID and API Key from Pipeline Details → View Pipeline > 💡 Tip: You can validate against any field that's critical for your use case – just swap invoice_number in the IF node for whatever field you define as mandatory (e.g. total_amount, vendor_name). Install the easybits Extractor Node n8n Cloud:* The node is verified* – just search for "easybits Extractor" in the node panel Self-hosted:* Go to Settings → Community Nodes → Install* and enter @easybits/n8n-nodes-extractor Connect Your Credentials Gmail Trigger: New Invoice – Add your Gmail OAuth2 credential and confirm the polling interval easybits: Extract Invoice Number – Enter your Pipeline ID and API Key Slack: Notify – Extraction Failed – Add your Slack credential and update the target user or channel Upload to Invoice Folder – Add your Google Drive credential and select the folder where archived invoices should land Adjust the Validation Field (Optional) The IF node currently checks {{ $json.data.invoice_number }} with the is empty operator. If your pipeline uses a different critical field, update this expression to point at that field. Activate & Test Click Active in the top-right corner of n8n Send yourself a test email with an invoice that's hard to read (blurry photo, scanned copy with poor contrast) to force an extraction failure Confirm you receive the Slack alert Send a clean invoice to confirm the success branch uploads correctly to Google Drive 🔄 Extending This Pattern This error handling branch can sit in front of any workflow in the easybits series: Invoice Approval Pipeline** – catch failed extractions before they hit Slack approval Document Classification Pipeline** – flag documents that couldn't be classified confidently Receipt-to-Sheet** – prevent null rows from polluting your expense tracker The pattern is always the same: Extractor → IF (is empty) → error branch alongside your main path.

Who’s it for This workflow is designed for Japanese-speaking professionals, and learners who want to efficiently stay up to date with practical productivity, lifehack, and efficiency-related insights from Japanese content platforms such as blogs and media sites. It is particularly suitable for individuals who prefer actionable, real-world tips—such as workflow improvements, time management strategies, and daily efficiency techniques—rather than abstract motivational content. This workflow is also ideal for users who want to consume information not only as text but also as audio, enabling hands-free learning during commuting or multitasking. What it does This workflow automatically collects, evaluates, summarizes, and delivers high-quality Japanese productivity and lifehack articles from multiple RSS sources such as Roomie, Lifehacker, and note. It retrieves articles published within the last 24 hours, merges multiple RSS feeds, and filters them for relevance. Then, AI evaluates the articles based on practical usefulness, reproducibility, and clarity, selecting only the top 10 most valuable pieces. For each selected article, the workflow: Fetches the full article content Cleans and extracts readable text Generates structured summaries in Japanese, including: Summary Target audience Use cases Expected effects Additionally, the workflow converts the summarized content into natural, audio-friendly narration using AI, allowing users to listen to the information like a daily news briefing. Finally, it sends text summaries to Slack for easy daily consumption, while optionally saving audio outputs to Google Drive for later access and playback. How it works A scheduled trigger starts the workflow automatically at a specified time. RSS feeds from multiple sources (Roomie, Lifehacker, note hashtags) are fetched. All articles are merged into a single dataset. Articles are filtered to include only those published within the last 24 hours. Article data is normalized into a structured format for AI processing. Gemini AI evaluates and ranks articles based on practical value and selects the top 10. Each article link is accessed and HTML content is retrieved. HTML is cleaned and converted into readable text data. OpenAI generates structured summaries in Japanese. Another AI step converts summaries into natural, spoken-style Japanese scripts. The scripts are converted into audio files (text-to-speech) and stored in Google Drive. The summarized text results are formatted and delivered to Slack. Requirements Google Gemini API credentials OpenAI API credentials Slack OAuth2 credentials (Optional) Google Drive credentials for audio file storage A Slack channel for receiving notifications How to set up Set up your API credentials within n8n, configure the Slack destination channel, and activate the workflow. If audio generation is enabled, ensure your OpenAI API has access to text-to-speech features and optionally connect Google Drive for file storage. You can also adjust scheduling settings and AI prompts to match your preferences. How to customize the workflow You can customize this workflow by: Adding or replacing RSS sources (e.g., specific Japanese productivity blogs or niche communities) Adjusting the filtering window (e.g., last 48 hours instead of 24 hours) Modifying AI scoring criteria (e.g., prioritize beginner-friendly or advanced content) Changing summary structure (e.g., adding “key takeaway” or “action steps”) Customizing Slack message format for readability Enabling or disabling audio generation Changing narration tone or style for audio output Switching output language if needed

AI Proposal Comparison & Gap Analysis Workflow for Salesforce CRM This workflow automatically analyzes newly uploaded proposals by comparing them with past winning proposals using AI. It extracts proposal content, identifies the client, fetches reference data from Google Sheets and generates actionable insights. These insights are saved in Salesforce and shared on Slack for team visibility. Quick Implementation Steps Connect Google Drive, Google Sheets, Salesforce, Slack and Groq AI credentials in your n8n account. Set your Google Drive folder to monitor proposal uploads. Ensure your Google Sheet contains winning proposals with status = Won. Activate the workflow. Upload a proposal file to trigger analysis automatically. What It Does This workflow automates the process of analyzing business proposals by leveraging AI and historical data. When a new proposal file is uploaded to a specific Google Drive folder, the workflow downloads and extracts its content. It then identifies the client name using a simple pattern from the text. At the same time, the workflow fetches past winning proposals from a Google Sheets database filtered by status. Both the current and past proposals are combined and sent to an AI model for comparison. The AI generates concise insights highlighting missing elements, weak positioning, pricing gaps and improvement suggestions. Finally, the insights are formatted and stored in Salesforce as an Opportunity record. A notification is sent to Slack, ensuring the team is informed and can act quickly to improve proposal quality. Who It's For Sales teams managing multiple proposals Business development professionals Proposal review and strategy teams Organizations using Salesforce CRM Teams looking to improve win rates using AI Requirements n8n account (self-hosted or cloud) Google Drive account (with folder for proposals) Google Sheets account (with winning proposals data) Salesforce account (Opportunity access enabled) Slack workspace (channel for notifications) Groq API credentials (for AI model access) How It Works & Set Up Setup Google Drive Trigger Configure New Proposal Upload Trigger Select the folder where proposals will be uploaded Event: fileCreated Download and Extract Proposal Use Download Proposal node to fetch file Use Read Proposal Text node to extract content Extract Client Information Use Extract Client Info (Code node) Extract clientName using regex from text Store full proposal as currentProposal Fetch Winning Proposals Configure Get Winning Proposal Data (Knowledge Base) Connect Google Sheet Filter where status = Won Combine Data Use Combine Proposal Data (Merge node) Combine current proposal and past proposal AI Analysis Use AI Proposal Gap Analyzer Provide prompt to compare proposals Generate structured insights (8–10 bullet points) Format Output Use Format Analysis Output Map clientName and analysisSummary Save to Salesforce Use Save Insights to Salesforce Create Opportunity Add insights in description Prepare Final Output Use Prepare Final Output (Merge node) Add Delay (Optional Control) Use Wait for Save node (2 seconds delay) Send Slack Notification Use Send Notification to Slack Send formatted message with insights How To Customize Nodes Extract Client Info:** Modify regex if proposal format changes Google Sheets Node:** Change filter or add more columns AI Prompt:** Customize output format or analysis depth Salesforce Node:** Change stage, fields or object type Slack Node:** Update message format or channel Wait Node:** Adjust delay time if needed Add-ons Add email notification (Gmail node) Store results in Google Sheets for history Add error handling with IF node Add multiple proposal comparison logic Integrate dashboard (Notion, Airtable, etc.) Use Case Examples Improving proposal quality before client submission Training new sales team members using past wins Automating proposal review workflows Identifying common gaps in losing proposals Tracking proposal insights in CRM There can be many more use cases depending on how you extend this workflow. Troubleshooting Guide | Issue | Possible Cause | Solution | | --------------------------- | ------------------------------ | ----------------------------------------- | | No trigger on file upload | Incorrect folder selected | Verify Google Drive folder ID | | Client name not extracted | Proposal format mismatch | Update regex in Code node | | No data from Google Sheets | Filter mismatch (status = Won) | Check column name and values | | AI output empty | Prompt or input missing | Verify merged data structure | | Salesforce error | Invalid credentials or field | Check API credentials and field mapping | | Slack message not sent | Wrong channel or auth issue | Reconnect Slack credentials | | Workflow stops before Slack | Wait node misconfigured | Ensure correct connection after Wait node | Need Help? If you need assistance setting up this workflow, customizing nodes or adding advanced features, we’re here to help. Whether it's integrating additional tools, improving AI analysis or building custom automation workflows tailored to your business needs, feel free to reach out to our n8n developers at WeblineIndia. Get expert help to scale your automation and build powerful AI-driven workflows efficiently.

Description Connect Fireflies to this workflow once and every meeting you record becomes a LinkedIn post draft automatically. The moment Fireflies finishes transcribing a call, it fires a signal to the workflow — which fetches the full transcript, extracts real insights, and uses GPT-4o-mini to write a 180–280 word scroll-stopping post with a hook, key learnings, and hashtags. The finished draft is saved to Google Drive and previewed in Slack so you can review and publish when ready. Built for founders, consultants, and sales leaders who want a consistent LinkedIn presence without spending time writing from scratch after every call. What This Workflow Does Triggers automatically when a call ends** — Fireflies sends a signal the moment transcription completes, so no manual input is ever needed Validates every incoming signal** — Checks that the signal contains a valid meeting ID and silently discards invalid or test pings Extracts real meeting insights** — Pulls speaker dialogue, Fireflies-detected pricing and question sentences, keywords, overview, and sentiment from the full transcript Writes a structured LinkedIn post** — GPT-4o-mini produces a hook, a specific insight paragraph, 3–5 emoji learnings, a closing question, and hashtags — all grounded in your actual meeting content Saves a complete Google Doc** — Stores the post alongside meeting reference details, participants, keywords, action items, and a link back to the Fireflies transcript Previews the post in Slack** — Posts the first 350 characters of the draft to your Slack channel so your team can review before the post goes live Exits cleanly for incomplete transcripts** — If Fireflies hasn't finished processing yet, the workflow stops silently without errors Setup Requirements Tools Needed n8n instance (self-hosted or cloud) Fireflies.ai account with webhook access OpenAI account with GPT-4o-mini API access Google Drive (one folder where posts will be saved) Slack workspace with OAuth2 app configured Credentials Required Fireflies API key (pasted directly into 5. Set — Config Values) OpenAI API key Google Drive OAuth2 Slack OAuth2 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 Activate the workflow and copy the webhook URL — Toggle the workflow to Active → click on node 1. Webhook — Fireflies Transcript Done → copy the webhook URL shown Register the webhook in Fireflies — Log in to fireflies.ai → go to Settings → Developer Settings → Webhooks → paste the webhook URL → save Get your Fireflies API key — In Fireflies, go to Settings → Integrations → copy your API key Fill in Config Values — Open node 5. Set — Config Values → replace all placeholders: | Field | What to enter | |---|---| | YOUR_FIREFLIES_API_KEY | Your Fireflies API key from step 4 | | YOUR_GOOGLE_DRIVE_FOLDER_ID | The folder ID from your Google Drive URL (the string after /folders/ in the URL when you open the folder) | | #content-team | Your Slack channel name including the # | | YOUR FULL NAME | The author's full name (used in the post sign-off) | | YOUR JOB TITLE | The author's job title (e.g. CEO, SEO Consultant) | | YOUR COMPANY NAME | Your company name (used in the AI prompt) | Connect OpenAI — Open node 11. OpenAI — GPT-4o-mini Model → click the credential dropdown → add your OpenAI API key → test the connection Connect Google Drive — Open node 13. Google Drive — Save LinkedIn Post → click the credential dropdown → add Google Drive OAuth2 → sign in with your Google account → authorize access Connect Slack — Open node 14. Slack — Send Post Preview → click the credential dropdown → connect your Slack workspace via OAuth2 → invite the n8n bot to your channel in Slack (/invite @n8n) > ⚠️ The workflow must be Active before registering the webhook in Fireflies. An inactive workflow will not receive signals from Fireflies. Activate first, then paste the URL. How It Works (Step by Step) Step 1 — Webhook: Fireflies Transcript Done This step listens for a signal from Fireflies. Every time Fireflies finishes transcribing a meeting, it sends a POST request to this webhook URL containing the meeting ID. No manual trigger is needed — it fires automatically after every recorded call. Step 2 — Code: Extract Meeting ID The meeting ID is extracted from the incoming signal. Fireflies can send the payload in several different formats, so this step checks all possible locations and pulls the ID safely. If no meeting ID is found at all, a flag is set to mark the signal as invalid. Step 3 — IF: Valid Meeting ID? This is the first gate check. If a valid meeting ID was found (YES path), the workflow continues to fetch the transcript. If the signal was invalid or contained no meeting ID (NO path), the workflow routes to 4. Set — Invalid Webhook Skip and stops cleanly. Step 4 — Set: Invalid Webhook Skip This step handles the invalid signal case. It sets a brief message confirming the webhook was skipped and the workflow ends here for that trigger. Step 5 — Set: Config Values Your Fireflies API key, Google Drive folder ID, Slack channel, author name, author title, and company name are stored here. The validated meeting ID from step 2 is also carried forward so the transcript fetch can use it directly. Step 6 — HTTP: Fetch Transcript A request is sent to the Fireflies API using your API key and the meeting ID. It retrieves the complete transcript including all sentences with speaker labels, AI-detected pricing and task sentences, keyword summary, overview, gist, bullet points, and sentiment percentages. Step 7 — Code: Process Transcript Data The raw transcript is processed into clean, usable fields. All sentences are combined into a readable text block (limited to 5,000 characters for GPT efficiency). Fireflies-flagged pricing sentences, question sentences, and task sentences are extracted separately. Sentiment percentages, keywords, action items, and overview are all pulled out. A formatted document title is generated automatically using the meeting name and date. If the transcript is empty or not yet available, a flag is set for the next gate check. Step 8 — IF: Transcript Ready? This is the second gate check. If transcript data is available (YES path), the workflow moves to AI post writing. If Fireflies hasn't finished processing the transcript yet (NO path), the workflow routes to 9. Set — Transcript Not Ready Skip and stops cleanly without errors. Step 9 — Set: Transcript Not Ready Skip This step handles the not-ready case. It logs the meeting ID and a message confirming the transcript was skipped. The workflow ends here for that run. Step 10 — AI Agent: Write LinkedIn Post GPT-4o-mini receives the author details, meeting context, Fireflies summary, bullet points, keywords, action items, questions raised in the call, and the transcript excerpt. It writes a 180–280 word LinkedIn post following a fixed structure: a scroll-stopping hook (not starting with "I" or "We"), a specific insight paragraph in first person, 3–5 emoji key learnings pulled from real transcript content, a closing question or call to action, and 4–5 hashtags. A sign-off with the author's name and title is added at the end. Step 11 — OpenAI: GPT-4o-mini Model This is the language model powering the writing step. It runs at temperature 0.8 for creative, varied output and is capped at 700 tokens to keep the post within the target word count. Step 12 — Code: Build Doc and Slack Message The AI-generated post is assembled into a complete Google Doc with the post text at the top, followed by meeting reference details: title, date, duration, participants, Fireflies transcript link, keywords, and action items. A Slack preview is also built here — the first 350 characters of the post plus meeting details and a link back to the Fireflies transcript. Step 13 — Google Drive: Save LinkedIn Post The complete document is saved to your specified Google Drive folder. The file is named automatically using the meeting title and date (e.g. "LinkedIn Post — Client Strategy Call — 14 Apr 2025"). Step 14 — Slack: Send Post Preview The preview message is posted to your Slack channel at the same time the Google Doc is being saved. Your team sees the post hook and first paragraph instantly, with the full document link available in Drive for review before publishing. Key Features ✅ Fully automatic — zero manual trigger — Fireflies fires the workflow the moment any call transcript is ready, no human action needed ✅ Two validation gates — Invalid webhook signals and unready transcripts both exit cleanly without causing errors or empty posts ✅ Grounded in real content — The AI prompt feeds actual transcript sentences, keywords, bullet points, and action items so posts are specific, not generic ✅ Fixed post structure every time — Hook, insight paragraph, emoji learnings, closing CTA, hashtags, and sign-off are enforced on every run ✅ Auto-named Google Docs — Files are named by meeting title and date automatically so your Drive folder stays organized without any manual renaming ✅ Slack preview before publishing — Your team sees the draft before it goes live — one review step, no surprises ✅ Handles all Fireflies payload formats — The extraction step checks every possible payload structure so the webhook never silently fails due to a format change ✅ Temperature tuned for creative writing — GPT runs at 0.8 so each post has a natural, human tone rather than a repetitive AI pattern Customisation Options Change the post length target — In node 10. AI Agent — Write LinkedIn Post, edit the instruction from "180 to 280 words" to a different range. Also adjust maxTokens in node 11. OpenAI — GPT-4o-mini Model accordingly (e.g. set to 900 for longer posts). Add a second post format — After node 10. AI Agent — Write LinkedIn Post, add a second AI Agent step with a different prompt structure (e.g. a short 3-sentence insight post or a carousel-style numbered list) to generate two post options per call instead of one. Route posts by meeting type — In node 5. Set — Config Values, add a postCategory field. Then add an IF check after step 7 that reads the meeting title — if it contains "demo" or "sales", use a sales-focused prompt; if it contains "team" or "internal", use a thought leadership prompt. Save to a dated subfolder in Drive — In node 12. Code — Build Doc and Slack Message, generate a folder path string using the meeting date (e.g. 2025/April) and use the Google Drive step to create or find that subfolder before saving, keeping your Drive organized by month automatically. Add a Notion database entry — After node 13. Google Drive — Save LinkedIn Post, add a Notion API HTTP request to create a new row in a content calendar database with the post title, meeting date, status (Draft), and Google Drive link for content planning visibility. Troubleshooting Workflow not triggering when a call ends: Confirm the workflow is Active before expecting Fireflies to fire it — inactive workflows do not receive webhooks Log in to Fireflies → Settings → Developer Settings → Webhooks → confirm the webhook URL is saved correctly and matches the URL from node 1. Webhook — Fireflies Transcript Done Check that your Fireflies plan includes webhook support — some plans restrict this feature Fireflies API key error or empty transcript: Confirm YOUR_FIREFLIES_API_KEY in node 5. Set — Config Values is replaced with your actual key — not the placeholder text Get your key from fireflies.ai → Settings → Integrations → API Key If the transcript returns empty, the call may not have been processed yet by Fireflies — the workflow exits cleanly via 9. Set — Transcript Not Ready Skip in this case OpenAI not generating the post: Confirm the API key is connected in node 11. OpenAI — GPT-4o-mini Model and your account has available credits Check the execution log of node 10. AI Agent — Write LinkedIn Post for the raw error message If the post is under 50 characters, node 12. Code — Build Doc and Slack Message catches this and outputs a failure message instead of a broken doc Google Drive not saving the file: Confirm the Google Drive OAuth2 credential in node 13. Google Drive — Save LinkedIn Post is connected and not expired — re-authorize if needed Check that YOUR_GOOGLE_DRIVE_FOLDER_ID in node 5. Set — Config Values is the folder ID from your Drive URL, not the full URL — copy only the string after /folders/ Make sure the Google account you authorized has write access to the target folder Slack preview not arriving: Confirm the Slack OAuth2 credential in node 14. Slack — Send Post Preview is connected and authorized Check that the channel name in node 5. Set — Config Values includes the # prefix and matches your Slack channel exactly Type /invite @n8n in the target Slack channel to ensure the bot has permission to post Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [email protected] 🌐 Website: https://www.incrementors.com/

Description Paste any text into a simple form — an email, social caption, blog paragraph, or proposal — and submit. GPT-4o-mini rewrites it simultaneously in five distinct tones: Professional, Casual, Persuasive, Concise, and Empathetic. All five versions are saved as a single document in your Google Drive folder, and your Slack channel gets an instant preview of the Concise version. Built for content teams, copywriters, and agencies who write the same message repeatedly for different audiences. What This Workflow Does Rewrites in five tones at once** — sends your text to GPT-4o-mini and gets back five complete versions in one AI call, saving you from rewriting manually Enforces structured output** — uses a schema parser to guarantee all five tones are always returned, even if the AI tries to skip one Saves everything to Google Drive** — assembles all five versions into one clearly labeled document and uploads it to your chosen Drive folder automatically Names files by project and date** — every document is titled with your project name and today's date so you can find it instantly later Sends a Slack preview** — posts the Concise version to your team channel the moment the document is ready, no waiting, no manual sharing Defaults gracefully** — fills in missing audience fields automatically so the workflow never fails due to a blank optional field Setup Requirements Tools you need: n8n instance (self-hosted or n8n Cloud) OpenAI account with API access Google account with Google Drive Slack workspace with a bot app Estimated Setup Time: 15–20 minutes Step-by-Step Setup Update your config values — Open the node named 2. Set — Config Values. Replace YOUR_GOOGLE_DRIVE_FOLDER_ID with the ID of your Drive folder (open the folder in Google Drive, look at the URL bar, and copy the string after /folders/). Replace #YOUR-SLACK-CHANNEL with your Slack channel name including the # symbol. Replace YOUR COMPANY NAME with your company or team name. > ⚠️ All three placeholder values are in 2. Set — Config Values — you must update all three before activating. Connect your OpenAI credential — Open the node named 4. OpenAI — GPT-4o-mini Model. Click the credential dropdown and connect your OpenAI API key. If you do not have one, go to platform.openai.com, sign in, click your account name, select API Keys, and create a new key. Connect your Google Drive credential — Open the node named 8. Google Drive — Upload Tone Doc. Click the credential dropdown and connect your Google account using OAuth2. n8n will prompt you to sign in and grant Drive access. Connect your Slack credential — Open the node named 9. Slack — Send Concise Preview. Click the credential dropdown and connect your Slack OAuth2 app. After connecting, invite the Slack bot to your target channel by typing /invite @your-bot-name inside that channel. Activate the workflow — Click Activate in the top right of n8n. Copy the form URL from node 1. Form — Content Tone Rewriter and bookmark it or share it with your team. How It Works (Step by Step) Step 1 — Form Trigger: Content Tone Rewriter You open the form in your browser and fill in four fields: your original text, the content type (Email, Social Media Caption, Blog Paragraph, Client Proposal, Product Description, or Other), your name or project name, and an optional target audience. When you submit, the workflow starts immediately. Step 2 — Set: Config Values This step loads your configuration and maps every form field into clean variables. It sets the Drive folder ID, Slack channel, and company name from your placeholders. It also builds the document title automatically — combining your project name with today's date — and records the exact time the workflow ran. Step 3 — AI Agent: Tone Rewriter (with GPT-4o-mini and Structured Output Parser) This step sends your original text to GPT-4o-mini along with the content type, target audience, and company name. The AI is instructed to return exactly five rewrites: Professional, Casual, Persuasive, Concise, and Empathetic. The 5. Parser — Structured Tone Output enforces a strict schema on the AI response, so if any tone version is missing or malformed, the parser catches it. All five versions must be present before the workflow moves forward. Step 4 — Code: Assemble Document Content This step takes the five AI-generated versions and combines them into one complete document. It adds a header showing the project name, content type, target audience, and run timestamp. Each tone version is separated by a clear divider line and labelled. It also prepares the Slack message, which shows the Concise version as a quick preview along with the project name and date. Step 5 — Code: Convert to Binary This step converts the assembled text document into a binary file that Google Drive can accept. It encodes the content and sets the filename to match the document title with a .txt extension. This step also passes the Slack channel and preview message forward for the parallel Slack step. Step 6 — Google Drive Upload: Upload Tone Doc This step uploads the binary file to the Google Drive folder you configured. The file is named with your project name and today's date. After this step, the complete five-version document is permanently saved in your Drive. Step 7 — Slack: Send Concise Preview This step runs in parallel with the Drive upload. It posts the Concise tone version to your configured Slack channel. The message includes the project name, content type, run time, and the full Concise rewrite. Your team can read and use the shortest version immediately without opening Drive. Key Features ✅ Five tones in one submission — no need to run the form five times or manually rewrite anything yourself ✅ Schema-enforced AI output — the structured parser guarantees all five versions are always returned, preventing incomplete results ✅ Auto-dated Drive documents — files are named with project name and date so your library stays organized with zero manual effort ✅ Parallel delivery — Drive upload and Slack notification run at the same time, so your team gets the preview while the document is saving ✅ Configurable defaults — target audience falls back to "General audience" if left blank, so the workflow never breaks on optional fields ✅ Any content type — the form dropdown covers six common content types so GPT-4o-mini adapts its rewrites appropriately to each format ✅ Single config node — all three configuration values live in one place (2. Set — Config Values), making updates fast and error-free Customisation Options Add more content types to the dropdown — Open node 1. Form — Content Tone Rewriter, find the Content Type field, and add new options such as "LinkedIn Post", "Press Release", or "SMS Message". Change the AI temperature — Open node 4. OpenAI — GPT-4o-mini Model and adjust the temperature value (currently 0.7). Lower it to 0.3 for more consistent, conservative rewrites. Raise it to 0.9 for more creative variation between versions. Swap GPT-4o-mini for a different model — Open node 4. OpenAI — GPT-4o-mini Model and change the model to gpt-4o if you want higher-quality rewrites and your usage allows the extra cost. Save to a dated subfolder in Drive — Add a Google Drive "Create Folder" step before node 8. Google Drive — Upload Tone Doc that creates a folder named by month, then pass that new folder's ID into the upload step instead of the static folderId. Email the document link after upload — Add a Gmail node after node 8. Google Drive — Upload Tone Doc to send the Drive file link to yourself or a client automatically after every submission. Add a sixth tone — In node 3. AI Agent — Tone Rewriter, add a sixth instruction inside the prompt (for example, "humorous"). Then update the schema in 5. Parser — Structured Tone Output to include the new key, and update node 6. Code — Assemble Document Content to include the sixth version in the document. Troubleshooting OpenAI credential not connecting: Confirm the API key is active and has not expired in your OpenAI account Make sure your OpenAI account has credit available — the workflow calls the API on every submission Re-enter the credential in 4. OpenAI — GPT-4o-mini Model if the connection shows an error Google Drive upload failing: Confirm the folder ID in 2. Set — Config Values is correct — open the Drive folder, look at the URL, and copy only the string after /folders/ Reconnect your Google Drive OAuth2 credential in 8. Google Drive — Upload Tone Doc if access was revoked Make sure the Google account you connected has edit access to that folder Slack message not appearing: Confirm the channel name in 2. Set — Config Values includes the # symbol Make sure you invited the Slack bot to the target channel using /invite @your-bot-name Reconnect the Slack OAuth2 credential in 9. Slack — Send Concise Preview if it shows as disconnected AI returning incomplete tone versions: The 5. Parser — Structured Tone Output enforces all five keys — if the AI skips one, the parser will throw an error visible in the execution log Check the prompt in 3. AI Agent — Tone Rewriter has not been accidentally edited to remove any of the five tone instructions Reduce the temperature in 4. OpenAI — GPT-4o-mini Model to 0.5 for more reliable structured responses Form submits but workflow does not run: Confirm the workflow is Activated — the toggle must be on in the top right of n8n Check that the form URL you are using matches the active webhook URL shown in node 1. Form — Content Tone Rewriter Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [email protected] 🌐 Website: https://incrementors.com/

What This Workflow Does Receive any business document via email. The attachment is automatically classified (Invoice, Contract, or Purchase Order) using easybits Extractor, then routed down the correct path where a second Extractor pulls out document-specific data. Each route stores the file in Google Drive and triggers the appropriate action – Invoices go to a finance spreadsheet, Contracts and Purchase Orders trigger Slack notifications. How It Works Receive – Gmail polls for new emails with attachments every minute Classify – easybits Extractor identifies the document type and returns a class label Route – A Switch node sends the item down the matching path (Invoice / Contract / PO) Merge Binary – The original file is merged back into the routed item (classification strips the binary) Extract – A second easybits Extractor pulls fields specific to that document type Merge Data + File – Extracted JSON and original binary are combined for upload Store & Notify – The file is uploaded to Google Drive; Invoices update a spreadsheet, Contracts and POs trigger Slack alerts Setup Guide Create Your easybits Classification Pipeline Go to extractor.easybits.tech and create a new pipeline Add one field called document_class In the field prompt, describe your classification categories and how to identify each one (see the "easybits: Classify Document" node for a reference prompt) The prompt should instruct the model to return exactly one category label – no explanations, no extra text Adjust the categories and identification criteria to match your specific document types Copy your Pipeline ID and connect the credential in the classification node > 💡 Tip: The classification prompt is the heart of this workflow. The more specific your category descriptions and decision rules are, the more accurate your results will be. Create Three Extraction Pipelines Create one pipeline per document type on extractor.easybits.tech: Invoice pipeline** – fields: invoice_number, total_amount, currency, due_date, vendor_name Contract pipeline** – fields: client_name, contract_type, contract_value, currency, start_date, notice_period Purchase Order pipeline** – fields: supplier_name, po_number, order_date, expected_delivery_date, total_amount, currency Connect each pipeline's credentials to the matching Extractor node. Set Up Gmail Connect your Gmail account via OAuth2. Optionally filter by label to only process specific emails. Make sure Download Attachments is enabled in the node options. Set Up Google Drive Create three folders in Google Drive: Invoices, Contracts, Purchase Orders. Select the correct folder in each Upload node. Set the Input Binary Field to attachment_0 (or whichever field carries the PDF). Set Up Google Sheets Create a spreadsheet (or use an existing Master Finance File). Make sure the column headers match the field mappings in the "Update Master Finance Sheet" node. Set Up Slack Connect your Slack workspace. Select the channel for contract notifications (e.g. #contracts) and the channel for PO updates (e.g. #operations). Adjust the message templates if your extracted field names differ. Activate & Test Set the workflow to active and send a test email with an invoice, contract, and purchase order attached to verify each route works end to end.

What This Workflow Does Upload a document (PDF, PNG, JPEG) via a web form and let easybits Extractor classify it into one of your defined categories. Based on the classification result and a confidence score, the document is automatically sorted into the correct Google Drive folder. Low-confidence or unrecognized documents are flagged for manual review via Slack. How It Works User uploads a file through the hosted web form The binary file is converted to base64 and sent to easybits easybits returns a document_type and confidence_score The classification result is merged with the original file binary If confidence > 0.5 → routed to the matching Google Drive folder If confidence ≤ 0.5 or no category match → uploaded to Needs Review folder + Slack alert Supported categories: medical_invoice · restaurant_invoice · hotel_invoice · trades_invoice · telecom_invoice Setup Guide Set Up Your easybits Extractor Pipeline Go to extractor.easybits.tech and create a new pipeline Add two fields to the mapping: document_class and confidence_score In each field's description, paste the corresponding classification or confidence prompt that tells the model how to analyze the document The classification prompt should return exactly one category label – or null if uncertain The confidence prompt should return a decimal number between 0.0 and 1.0 Save & test the pipeline, then copy your Pipeline ID and API Key Set Up Google Drive Create a folder in Google Drive for each category: Medical, Restaurant, Hotel, Trades, Telecom, and Needs Review In n8n, go to Settings → Credentials and create a Google Drive OAuth2 credential This requires a Client ID and Client Secret from the Google Cloud Console (APIs & Services → Credentials → OAuth 2.0 Client ID) Make sure the Google Drive API is enabled in your Google Cloud project Open each of the 6 Google Drive upload nodes in this workflow and select the correct target folder Set Up Slack In n8n, go to Settings → Credentials and create a Slack API credential You'll need a Slack Bot Token – create a Slack App at api.slack.com/apps, add the chat:write scope, and install it to your workspace Create a channel for review notifications (e.g. #n8n-invoice-review) Invite the bot to that channel Open the Review Message node and select the correct channel Connect the easybits Node Open the easybits Extractor (Classification) node Replace the pipeline URL with your own: https://extractor.easybits.tech/api/pipelines/YOUR_PIPELINE_ID Create a Bearer Auth credential using your easybits API Key and assign it to the node Activate & Test Click Active in the top-right corner of n8n Open the form URL and upload a test document Check the execution log to verify the classification result Confirm the file lands in the correct Google Drive folder Test with an unrecognized document to verify the Slack notification fires

📘 Description This workflow is an AI-powered virtual cinematography and previs generation pipeline designed for film and VFX production. It transforms a director’s shot description into multiple camera choreography options, generates AI-driven previs videos, extracts key frames, and delivers a complete previs board package for supervisor review—enabling faster creative decision-making with zero manual setup. ⚙️ Step-by-Step Flow The workflow begins with a form-based trigger that captures a structured shot brief from the production team, including shot code, script snippet, camera and lens specifications, plate image reference, and movement complexity. This input is validated and normalized into a clean data structure, ensuring consistency across the pipeline. The processed brief is then sent to an AI agent powered by GPT-4o, which interprets the creative intent and generates three distinct camera choreography options. Each option includes a cinematic description, technical movement style, supervisor guidance, and a fully structured Seedance-ready prompt—effectively translating creative direction into executable camera logic. These AI-generated options are parsed and expanded into individual processing units, where each one is converted into a structured API request for video generation. The pipeline attaches the provided plate image as a visual reference to ensure all outputs remain grounded in the real environment. Each request is then submitted to the Seedance AI model as an asynchronous job, enabling parallel generation of all camera variations. A polling system continuously checks the status of each render at fixed intervals, ensuring that the workflow proceeds only after successful completion of all outputs. Once rendering is complete, the system collects each generated video and enriches it with production-ready metadata, including resolution, duration, and predefined key frames representing the opening, peak motion, and final composition. In parallel, the workflow downloads each video and archives it to Google Drive, creating a structured library of lighting references for downstream teams such as compositing and look development. An aggregation layer then compiles all camera options into a unified previs board package, formatting them into structured outputs for different platforms, including visual option cards, Jira descriptions, and a complete HTML lookbook. Finally, the delivery system distributes the previs package across multiple production tools simultaneously. A Slack message presents all options in an easy A/B/C selection format for supervisors, a Jira task is created for tracking and approval, a ClickUp record is logged for production management, and a Telegram message is sent for quick mobile access. This ensures that all stakeholders receive synchronized, actionable outputs, enabling fast and informed decision-making in the previs stage. 🚨 Error Handling • AI parsing fallback to handle invalid JSON outputs • Retry loop for incomplete Seedance jobs (polling system) • Dedicated error trigger with instant Slack alerts • Telegram alert if AI agent fails to generate valid output • Prevents pipeline breaks and ensures reliability 🧩 Prerequisites • Azure OpenAI (GPT-4o or similar model) • Seedance API (AI video generation) • Google Drive OAuth2 (asset storage) • Slack OAuth2 (team communication) • Jira API (task tracking) • ClickUp API (production management) • Telegram Bot (optional notifications) • Form/Webhook trigger (input layer) 💡 Key Benefits ✔ Converts creative intent into technical camera choreography automatically ✔ Generates multiple previs options for faster decision-making ✔ Maintains visual consistency using plate image reference ✔ Auto-extracts key frames for editorial and layout guidance ✔ Centralized previs board generation (ready for review) ✔ Multi-platform delivery (Slack, Jira, ClickUp, Telegram) ✔ Builds a reusable lighting reference archive 👥 Perfect For Directors and cinematographers VFX previs and layout teams Virtual production workflows Film and episodic production pipelines Studios handling complex camera choreography

📘 Description This workflow is an AI-powered lighting and look development pipeline designed for VFX production. It transforms a single lighting brief into multiple high-quality cinematic lighting references using AI, automates rendering, organizes assets, builds a visual lookbook, and delivers structured outputs to the lighting team—bridging the gap between creative lighting direction and CG execution. ⚙️ Step-by-Step Flow The workflow begins with a form-based trigger that acts as the lighting brief intake layer, allowing artists or supervisors to submit structured inputs such as shot code, sequence, project ID, plate image, lighting mood description, scene type, and CG subject type. This input flows into a validation and normalization stage, where required fields are verified, scene and subject types are mapped into standardized pipeline values, and the payload is structured for downstream processing. The system then performs prompt engineering and expands the single lighting brief into five distinct lighting variations: a key light setup for strong directional lighting, a soft diffuse setup for ambient lighting conditions, a high-contrast dramatic setup for stylized visuals, a plate-matched reference for accurate scene integration, and a final comp-grade preview simulating cinematic color grading. Each variation is enriched with detailed lighting instructions, scene context, and subject-specific attributes to guide realistic AI generation. At the core of the pipeline, an image-to-video rendering layer constructs structured API requests and submits each variation as an independent job to the Seedance AI model, always using the plate image as a reference to maintain lighting consistency with the scene. A polling mechanism continuously monitors each job at regular intervals, ensuring that processing advances only after successful completion. Once rendering is complete, a metadata layer structures detailed information for each asset, including video URLs, lighting types, scene context, subject details, and generation timestamps, along with tagging for pipeline tracking and review status. The asset pipeline then downloads the generated lighting reference videos and uploads them to Google Drive using a structured naming convention aligned with shot and variation identifiers. An aggregation layer consolidates all variations into a unified output and dynamically generates an HTML-based lookbook, presenting all lighting setups in a structured visual format with preview links, technical details, and usage guidance. This lookbook is stored in a Notion database for centralized tracking and documentation. Finally, an AI-driven messaging layer generates a clean, professional Slack notification summarizing the lighting brief, listing all generated variations with preview links, and prompting the lighting team to review and select the preferred direction before proceeding with CG lighting setup—ensuring seamless collaboration between creative intent and technical execution. 🚨 Error Handling • Global error trigger across the workflow • Sends instant Slack alerts with failure details • Prevents silent failures and ensures production reliability 🧩 Prerequisites • Seedance API (AI video generation) • n8n Form Trigger (input layer) • Google Drive OAuth2 (asset storage) • Notion API (lookbook tracking) • Slack OAuth2 (team notifications) • OpenAI API (AI-generated Slack messaging) 💡 Key Benefits ✔ Rapid lighting look development with multiple variations instantly ✔ Structured prompt engineering for consistent cinematic outputs ✔ Automated asset storage and organized lookbook generation ✔ AI-generated team communication for faster decision-making ✔ Seamless integration between creative direction and CG execution ✔ Scalable pipeline for production-ready lighting workflows 👥 Perfect For Lighting artists and look development teams VFX supervisors and creative directors CG and rendering pipelines Film and post-production studios AI-assisted lighting and visualization workflows

Finance Research Analyst for Boutique M&A Agencies This workflow acts as a junior finance research analyst for a UK boutique M&A or corporate finance team. It listens for Slack messages, classifies the request, gathers company or market data, and produces structured outputs in Google Docs, Google Slides, Google Sheets, and PostgreSQL. It supports three user intents: Research this company X Prepare pitch materials for X Industry briefing on vertical X The workflow is designed for internal team use. It is not intended to send client-facing materials automatically without human review. Why This Template This template shows how a junior research analyst LIVE job and some of the key responsibilities might be automated with help of AI. 120+ junior analyst roles are live in London right now. This template does most of what they do. What This Template Does Company Research When a user asks to research a company, the workflow: searches Companies House for the best UK entity match retrieves company profile, officers, and filing history gathers company and website context using Firecrawl retrieves public market quote data from Alpha Vantage when a ticker is available asks an LLM to synthesize the research into a structured company profile creates a Google Doc with the company profile upserts the company into PostgreSQL stores the generated research as reusable memory updates the client database in Google Sheets replies in the original Slack thread with the output link Pitch Materials When a user asks to prepare pitch materials, the workflow: loads the stored company record from PostgreSQL pulls the most recent stored research memory asks an LLM to produce compact slide-ready bullet content copies a Google Slides pitch template replaces the template placeholders with generated content creates a Google Doc press release draft updates the pitch deck URL in PostgreSQL updates the client database in Google Sheets replies in the original Slack thread with the deck and document links Industry Briefing When a user asks for a sector briefing, the workflow: gathers sector web and news context using Firecrawl retrieves ONS macro M&A context asks an LLM to generate a concise one-page industry briefing creates a Google Doc with the briefing replies in the original Slack thread with the document link Who This Is For This template is built for: boutique M&A advisory firms corporate finance teams fundraising advisors internal research analysts supporting pitch and origination work It is optimized for UK company research because it relies on Companies House as the authoritative company registry. Prerequisites Before using this template, you need: an n8n instance a Slack app configured for message triggers and posting replies a Google account with Drive, Docs, Slides, and Sheets access (Free) a PostgreSQL database (Free self hosted or use supabase) an OpenRouter credential for the LLM calls (Models used= haiku4.5, Sonnet 4.5) a Companies House API key configured as Basic Auth (Free) a Firecrawl API key configured as HTTP Header Auth (Free) API key for Alpha Vantage (free) fixed ONS URL for macro M&A context Required n8n Credentials Create or connect the following credentials in n8n before testing: Slack Trigger credential for incoming Slack events Slack credential for posting replies OpenRouter API Companies House Basic Auth Firecrawl Header Auth Google Drive OAuth2 Google Docs OAuth2 Google Slides OAuth2 Google Sheets OAuth2 Postgres Required External Assets Google Drive Root Folder The workflow creates subfolders under a given root folder: research outputs pitch outputs briefing outputs Current root folder used in the workflow: Modify this to your own folder: https://drive.google.com/drive/u/0/folders/1GH-YouAAImKugZ11IbqA6Ouw8B9U17-I Google Sheets Client Database The workflow writes to this spreadsheet: Modify this to your own google sheet: https://docs.google.com/spreadsheets/d/1yJ-UKOEUqIruCv-IBA33oN4taQTB1TA8M4a6D2iSiOU/edit?gid=0#gid=0 Required sheet name: Sheet1 Required columns: company_name sector companies_house_number market_cap last_researched profile_doc_url pitch_deck_url Best practice: make companies_house_number unique if possible keep column names exactly as shown above Google Slides Pitch Template The workflow copies this Slides template: 1zQv_cbafHzd4JNsr711Rm0558O6W_S1SODc-u6tVS0k Required placeholders in text boxes: {company_name} {sector} {profile_summary} {financials} {opportunity_summary} {comps_note} Input Examples Use messages like these in Slack: Research Monzo, fintech Prepare pitch for Wise Industry briefing UK fintech Outputs Research Intent Outputs: Google Doc company profile PostgreSQL company record update PostgreSQL research memory insert Google Sheets client DB update Slack thread reply with doc link Pitch Intent Outputs: copied and populated Google Slides deck Google Doc press release draft PostgreSQL pitch deck URL update Google Sheets client DB update Slack thread reply with deck and doc links Brief Intent Outputs: Google Doc industry briefing Slack thread reply with doc link Database Expectations This template expects PostgreSQL tables to exist for: company records research memory At minimum, your database must support the queries used by the workflow for: upserting company records loading a company record by company_name storing research memory retrieving the latest research memory for pitch generation updating pitch_deck_url Limitations UK company research is strongest because the workflow depends on Companies House. private companies will not have public market quote data public-company quote data comes from Alpha Vantage GLOBAL_QUOTE, which is not a true market-cap endpoint the workflow does not create dynamic charts in Google Slides. the workflow does not replace human judgment on valuation, comps, or client-facing strategy

APK Upload Monitoring and Automated MobSF Analysis with Slack Reporting This workflow monitors a Google Drive folder for newly uploaded APK files, automatically downloads them, triggers a MobSF static analysis scan, processes the output to detect unused or risky libraries and sends a developer-friendly summary directly to Slack. It is ideal for teams who want fast, automated insights into Android app dependencies. ⚡ Quick Start: Rapid Implementation Steps Connect Google Drive and select the APK upload folder. Add your MobSF server URL in both HTTP Request nodes. Add your OpenAI API credentials. Connect Slack and choose your preferred channel. Activate the workflow — you're ready to automate APK analysis. What It Does This workflow automates the complete static analysis process for Android APK files. When an APK is uploaded to a specific Google Drive folder, n8n immediately retrieves the file and sends it to MobSF for scanning. MobSF returns detailed JSON-based findings, including code, library usage and component insights. The workflow then uses a series of JavaScript code nodes to extract relevant package information, compare used vs. detected packages, identify unused dependencies and classify them by risk. These results are transformed into a concise summary using an AI model. Finally, the summary is posted automatically to a Slack channel for fast team visibility. This enables developers to take quick action on dependency cleanup, performance optimizations or security risks without manually reading the full MobSF report. Who’s It For Android developers wanting automated dependency insights QA/security teams needing MobSF scans on every APK upload DevOps engineers maintaining CI/CD pipelines Mobile teams who frequently share build artifacts Organizations wanting fast Slack-based reporting Requirements to Use This Workflow A Google Drive account with access to an APK upload folder A running MobSF instance (Docker supported) OpenAI API credentials Slack workspace with API access n8n installed (self-hosted or cloud) How It Works & How To Set Up Google Drive Trigger Setup Connect your Google Drive credentials. Choose the folder dedicated to APK uploads. Event type: fileCreated (fires whenever a new APK is added). Downloading the APK The workflow uses the Google Drive node to download the uploaded file. No manual configuration required beyond credential setup. Configure MobSF Upload Replace the provided local URL with your MobSF instance URL. Ensure MobSF is reachable (via Docker or local network). Use multipart/form-data to upload the binary file. Trigger MobSF Static Scan The next HTTP Request node triggers a static scan using the returned hash. No further configuration needed. Code Nodes (Package Processing) These three nodes: extract used/detected packages, identify unused libraries, classify them as safe, maybe-required or risky. You can customize logic if needed. AI-Based Summary Generation Connect OpenAI credentials. The node generates a clean, non-markdown summary for Slack. Slack Notification Connect your Slack account. Select any desired channel. Summary is pushed instantly on every APK upload. Activate the Workflow Once all credentials are added, enable the workflow and test by uploading an APK. How To Customize Nodes Google Drive Trigger Modify polling interval (e.g., every 5 minutes). Change folder for different build pipelines. MobSF Request Nodes Replace URL to support remote servers or Kubernetes deployments. Add additional headers if needed. Code Nodes Adjust package detection rules. Add tagging, filtering or extra metadata extraction. OpenAI Summary Node Customize the prompt for different reporting styles (e.g., shorter, more technical). Slack Node Add formatting, mentions or route to multiple channels. Add-Ons (Optional Extensions) Email Notifications** – Send the same report to email via Gmail or SMTP. Jira Ticket Auto-Creation** – Open issues when risky dependencies are detected. Save Reports to Database** – Store unused package data for long-term trends. CI/CD Integration** – Trigger analysis via GitHub Actions or Jenkins. VirusTotal Scan** – Add an extra malware check layer. Use Case Examples Automated Dependency Cleanup Quickly identify unused libraries after each build upload. Security Monitoring for Android Releases Ensure risky system packages aren’t unintentionally included. Team Collaboration Enhancement Send automated insights to Slack for faster decision-making. QA Validation Before Deployment Confirm that declared dependencies match actual usage. Build Optimization Remove unnecessary packages to reduce APK size and performance overhead. > There are many more possible uses depending on team needs and environment. Troubleshooting Guide | Issue | Possible Cause | Solution | | ------------------------------ | --------------------------------------- | ------------------------------------------------------ | | Workflow not triggering | Wrong Google Drive folder | Re-select the correct APK folder in the trigger node | | MobSF upload failing | Wrong URL or server not running | Check MobSF Docker container and update the URL | | MobSF scan shows empty results | APK not parsed successfully | Verify the APK is valid and not corrupted | | Slack message not delivered | Channel permissions or wrong channel ID | Reconnect Slack credentials and select a valid channel | | AI summary node fails | Missing OpenAI credentials | Add OpenAI API key in the credentials section | Need Help? If you need assistance setting up, extending or customizing this workflow, our n8n automation experts at WeblineIndia are available to help. Whether you want to add new features, integrate more systems or build similar automation workflows, feel free to reach out to us for professional support.

📘 Description This workflow is an AI-driven FX concept generation pipeline that transforms a single VFX brief into multiple high-quality simulation-ready video concepts. It automates ideation, rendering, storage, and team review—bridging the gap between creative direction and simulation execution. ⚙️ Step-by-Step Flow The process begins with a webhook trigger that serves as the FX brief intake layer, receiving a POST request containing the core FX brief, shot code, and optional parameters such as FX type, scale, intensity, and camera details. This input then moves through a validation and normalization stage, where required fields are verified and key attributes—such as FX type (fire, smoke, explosion), camera movement, frame range, FPS, scale, intensity, and speed—are standardized for consistency. Following this, the system performs prompt engineering and fans out the single brief into four creative variations: a primary reference (balanced), a high-intensity version (extreme simulation), a subtle version (controlled low-intensity FX), and an alternate camera variation offering a different perspective. Each variation is enriched with detailed cinematic instructions, including camera behavior, speed dynamics, and frame timing. At the core of the workflow, a dynamic generation mode determines whether to use image-to-video (if a reference image is provided) or text-to-video (if not), ensuring flexibility across both concepting and plate-matching use cases. Each variation is then submitted as an independent job to the Seedance API for AI rendering, returning unique job IDs for asynchronous tracking. A polling system manages execution by checking the job status every 20 seconds and continues until rendering is complete, handling each variation independently. Once completed, the system structures detailed metadata for each asset, including the video URL, FX type, scale, intensity, camera movement, frame specifications, and relevant tags for tracking and review. The asset storage pipeline then downloads the generated videos, uploads them to Google Drive using a structured naming convention, and logs all associated metadata into a Notion database for organized tracking. An aggregation layer consolidates all variations into a single structured output, combining video links, Notion records, and technical metadata. Finally, a Slack review dispatch sends a well-formatted message to the FX team, presenting all variations in one place with direct video previews, along with a technical breakdown covering scale, intensity, camera settings, and FPS, as well as Notion links for streamlined tracking and review. 🚨 Error Handling • Global error trigger • Sends Slack alert with failure details • Ensures no lost jobs or silent failures 🧩 Prerequisites • Seedance API (AI video generation) • Google Drive OAuth2 • Notion API • Slack OAuth2 • Webhook integration 💡 Key Benefits ✔ Rapid FX concept iteration (4 variations instantly) ✔ Structured prompt engineering for consistent outputs ✔ Automatic handling of camera, timing, and simulation context ✔ Integrated storage (Drive + Notion) ✔ Centralized team review via Slack ✔ Supports both concept art and simulation previsualization 👥 Perfect For VFX studios Simulation teams (Houdini, FX artists) Previsualization pipelines Creative direction teams AI-assisted film production systems

📘 Description This workflow is an AI-assisted clean plate and object removal pipeline built for modern VFX production environments. It transforms a single plate image and removal brief into multiple high-quality clean plate variations, complete with automated quality evaluation, compositing-ready assets, and production-ready Nuke scripts—bridging the gap between manual paint workflows and fully automated AI-driven cleanup pipelines. ⚙️ Step-by-Step Flow 1 . The workflow begins with a webhook trigger that acts as the clean plate request intake layer, receiving a POST request containing the plate image URL, removal brief, shot code, and optional parameters such as object type, frame range, and QC thresholds. This input flows into a validation and data structuring stage, where required fields are verified, default values are assigned, and the payload is normalized to ensure consistency across downstream processes. The system then performs prompt engineering and expands the single removal brief into four specialized passes: a primary production-ready clean plate, an alternative variation, a foreground removal pass for background isolation, and a difference map for quality control visualization. Each pass is enriched with object-specific removal instructions, reconstruction constraints, and technical shot metadata to guide accurate AI generation. 2 . At the core of the pipeline, an image-to-video rendering process leverages the provided plate image as a reference and submits each variation as an independent job to the Seedance AI API, generating video-based clean plate outputs. A polling mechanism continuously tracks each job at fixed intervals, ensuring that processing only advances once rendering is successfully completed. Once outputs are available, a metadata and automated QC layer evaluates each pass by assigning a quality score based on resolution and consistency logic, comparing it against a predefined threshold to classify results as either auto-approved or flagged for review. A decision routing layer then determines the next step—allowing approved outputs to continue through the pipeline while immediately notifying the team via Slack in case of failures. 3 . Following this, the system generates a fully production-ready Nuke compositing script, automatically configuring nodes for the original plate, AI-generated clean plate, difference map visualization, merge operations, grading adjustments, and final output writes, all aligned with standardized folder structures and naming conventions. The asset pipeline then downloads the generated videos, uploads them to Google Drive using structured shot-based organization, and logs all associated metadata—including plate references, output variations, and project details—into a Notion database for centralized tracking. An aggregation layer consolidates all outputs into a unified structured response, combining QC results, video links, compositing scripts, and storage paths. Finally, a multi-channel notification system dispatches a detailed message to Slack and Telegram, presenting all clean plate variations with QC status, video previews, inline Nuke scripts, and direct access to delivery folders for seamless team review and integration into production workflows. 🚨 Error Handling • Global error trigger • Sends failure alerts to Slack instantly • Prevents silent pipeline failures and data loss 🧩 Prerequisites • Seedance API (AI video generation) • Google Drive OAuth2 • Notion API • Slack + Telegram credentials • Webhook integration 💡 Key Benefits ✔ Fully automated clean plate generation with zero manual prep ✔ Multiple AI-generated passes for flexible compositing workflows ✔ Built-in QC validation with intelligent decision routing ✔ Auto-generated Nuke scripts ready for production use ✔ Structured asset storage and centralized tracking ✔ Real-time notifications for faster team collaboration 👥 Perfect For VFX paint and prep teams Compositors working in Nuke pipelines Film and post-production studios AI-assisted cleanup and restoration workflows Studios managing high-volume plate processing

What This Workflow Does Upload a document (PDF, PNG, JPEG) via a web form and let easybits Extractor classify it into one of your defined categories. Based on the classification result and a confidence score, the document is automatically sorted into the correct Google Drive folder. Low-confidence or unrecognized documents are flagged for manual review via Slack. How It Works User uploads a file through the hosted web form The binary file is converted to base64 and sent to easybits easybits returns a document_type and confidence_score The classification result is merged with the original file binary If confidence > 0.5 → routed to the matching Google Drive folder If confidence ≤ 0.5 or no category match → uploaded to Needs Review folder + Slack alert Supported categories: medical_invoice · restaurant_invoice · hotel_invoice · trades_invoice · telecom_invoice Setup Guide Set Up Your easybits Extractor Pipeline Go to extractor.easybits.tech and create a new pipeline Add two fields to the mapping: document_class and confidence_score In each field's description, paste the corresponding classification or confidence prompt that tells the model how to analyze the document The classification prompt should return exactly one category label – or null if uncertain The confidence prompt should return a decimal number between 0.0 and 1.0 Save & test the pipeline, then copy your Pipeline ID and API Key Set Up Google Drive Create a folder in Google Drive for each category: Medical, Restaurant, Hotel, Trades, Telecom, and Needs Review In n8n, go to Settings → Credentials and create a Google Drive OAuth2 credential This requires a Client ID and Client Secret from the Google Cloud Console (APIs & Services → Credentials → OAuth 2.0 Client ID) Make sure the Google Drive API is enabled in your Google Cloud project Open each of the 6 Google Drive upload nodes in this workflow and select the correct target folder Set Up Slack In n8n, go to Settings → Credentials and create a Slack API credential You'll need a Slack Bot Token – create a Slack App at api.slack.com/apps, add the chat:write scope, and install it to your workspace Create a channel for review notifications (e.g. #n8n-invoice-review) Invite the bot to that channel Open the Review Message node and select the correct channel Connect the easybits Node Open the easybits Extractor (Classification) node Replace the pipeline URL with your own: https://extractor.easybits.tech/api/pipelines/YOUR_PIPELINE_ID Create a Bearer Auth credential using your easybits API Key and assign it to the node Activate & Test Click Active in the top-right corner of n8n Open the form URL and upload a test document Check the execution log to verify the classification result Confirm the file lands in the correct Google Drive folder Test with an unrecognized document to verify the Slack notification fires

Who’s it for Affiliate managers, partner programs, and teams collecting leads via public forms who want automated, error-free routing to separate spreadsheets per affiliate — no more manual copying or sheet hunting. What it does This workflow captures new submissions from a Tally.so form, extracts the affiliate code, finds or creates the corresponding Google Sheet, appends the lead data, and sends a real-time Slack notification. New affiliates are handled automatically: if no sheet exists for the submitted code, the workflow creates one and places it in a designated Google Drive folder. Key features 📝 Real-time Tally form capture (Name, Email, Affiliation Code, Phone) 🔍 Smart routing by affiliation code 📊 Auto-creates new affiliate sheets when needed 📁 Organized storage in a single Google Drive folder 🔔 Instant Slack notifications with full lead details 🔄 How it works Tally submission → Webhook trigger Extract fields: Name, Email Address, Phone Number, Affiliation Code Add current Submission Date and Submission Time Search Google Drive for sheet matching the Affiliation Code ✅ Found → Append row with all data ❌ Not found → Create new sheet → Move to folder → Append row Send formatted Slack alert with full lead info 📋 Requirements Tally.so form including Name, Email Address, Phone Number, and Affiliation Code fields Google Drive folder for storing affiliate sheets Google Sheets & Drive OAuth2 credentials (with Drive + Sheets APIs enabled) Slack bot token with chat:write scope Slack channel ID where notifications will be sent ⚙️ How to set up Import the workflow into n8n Create credentials: Tally API Google Sheets OAuth2 Google Drive OAuth2 Slack Bot Configure nodes: Select your Tally form in the webhook Set the parent Folder ID for affiliate sheets Enter your Slack Channel ID Activate the workflow and start receiving leads! 🛠️ How to customize Add extra fields: Capture additional data (e.g., UTM parameters, notes, referral source) by adding the fields to your Tally form, then map them in the webhook parsing and Google Sheets **Append nodes. Change notification channels: Replace the **Slack node with Discord Webhook, Send Email, Microsoft Teams, or any other notification node to fit your team’s preferred platform. Add validation & duplicate checks: Insert **IF nodes or a Code node before the sheet append to validate data quality, reject incomplete entries, or check for duplicate emails/phone numbers. Support multiple programs or priority routing: Extend the routing logic with **Switch nodes or additional Drive searches to handle different affiliate programs, tiers, or priority queues.

A smart, fully automated coding pipeline built inside n8n that leverages Cursor AI to write, refactor, review, and optimize code projects — triggered by a webhook, schedule, or manual prompt. Every output is versioned, stored, and delivered with a detailed review report. 🎯 What's the Goal? Eliminate the repetitive overhead of writing boilerplate code, performing code reviews, and refactoring legacy code manually. This workflow turns a plain-text task description into production-ready, reviewed, and optimized code — automatically and at scale — using Cursor AI's deep coding intelligence inside n8n. 💡 Why Does It Matter? Software teams lose hundreds of hours to boilerplate writing, manual code reviews, and inconsistent refactoring. AI-assisted coding with Cursor is powerful, but still requires manual triggering. By wiring Cursor into n8n, you get a repeatable, auditable, hands-free coding pipeline that integrates directly with your Git repos, Slack, and storage — making AI code generation a true part of your CI/CD culture, not just a one-off tool. ⚙️ How It Works Webhook or Schedule triggers the flow with a coding task description Task is classified (Generate / Review / Refactor / Optimize) Cursor AI API is called with the appropriate system prompt & task Raw code output is received and parsed A second Cursor pass performs automated code review & scoring If quality score passes threshold → code is committed to GitHub If score is below threshold → Cursor runs an optimization pass Final code + review report saved to Google Drive Summary logged to Google Sheets Slack notification sent with code snippet preview & Drive link 🔧 Configuration Requirements Cursor AI API key** (via Cursor developer access or proxy endpoint) GitHub Personal Access Token** (for auto-commit & PR creation) Google Drive OAuth2** (for storing code files & reports) Google Sheets OAuth2** (for logging task history & quality scores) Slack Bot Token** (for team notifications) Optional: OpenAI API key** (for task classification fallback) 🚀 Setup Guide Import this workflow into your n8n instance Connect all credentials: Cursor API, GitHub, Google Drive, Google Sheets, Slack Open the Set Task Config node and fill in: repo_owner and repo_name (your GitHub target repo) target_branch (e.g. ai-generated or main) quality_threshold (score 0–100, recommended: 75) storage_folder (Google Drive folder name) log_sheet_id (Google Sheets document ID) Test with a manual webhook POST containing { "task": "Write a Python FastAPI CRUD endpoint for users" } Review output in Drive and check Slack notification Activate the webhook for live use Optionally activate the daily schedule for batch processing queued tasks Monitor quality scores in Google Sheets and tune the threshold as needed

This workflow automatically detects duplicate files uploaded to a specific Google Drive folder by generating an MD5 hash of each file and comparing it against a Supabase database. If a duplicate is found, the file is moved to a dedicated Duplicates folder and a Slack notification is sent. All events, including unique uploads, duplicates, race conditions, and errors, are logged for audit purposes. It is designed for teams that handle high file volumes and need reliable, content based deduplication instead of simple filename checks. How it works Monitors a specific Google Drive folder for new files. Normalizes file metadata and downloads the binary content. Generates an MD5 hash from the file binary. Checks Supabase to see if the hash already exists. If duplicate, moves the file to a Duplicates folder and sends a Slack alert. If unique, stores the hash in Supabase. Logs every outcome, including errors and race conditions, in an audit table. Setup steps Connect your Google Drive account and select the folder to monitor. Connect your Supabase account and create the required tables: file_hashes dedup_audit_log Connect your Slack account and select a channel for duplicate alerts. Update the Duplicates folder ID in the Google Drive Move node. Setup typically takes 10 to 15 minutes if your Supabase project is ready.

Talent Sovereign: AI-Powered Resume Screener & Recruitment Hub 🎯 Description This is an elite enterprise-grade solution for Talent Acquisition and HR Ops teams. It automates the high-volume task of resume screening by transforming unstructured PDF applications into structured candidate profiles. Leveraging an advanced PDF-to-JSON parsing engine and a multi-factor scoring algorithm, it ensures only the highest-quality candidates reach your CRM while maintaining a professional feedback loop for all applicants. ✨ The Sovereign Lifecycle Intelligent Intake & Validation - Monitors Gmail for new submissions. A pre-validation layer ensures only healthy PDF binaries under 10MB enter the stream, filtering out noise and irrelevant attachments. Atomic Data Extraction - Utilizes the HTML to PDF (Parse PDF to JSON) node to decompose resumes into structured text data. Advanced AI Resume Parser - A sophisticated Code Node acts as a virtual Recruiter. It extracts contact info, LinkedIn URLs, and maps 45+ specific skills across 7 categories (Programming, Cloud, Data, etc.). It even calculates "Total Years of Experience" by analyzing date ranges within the text. Multi-Factor Scoring & Tiering - Candidates are automatically ranked on a 100-point scale: A+ Tier (90+): Exceptional talent; priority alerts. Qualified (70+): Standard qualified candidates. Below Threshold: Automatically prepared for the rejection track. Smart Routing Matrix - Green Track: Qualified leads are created in HubSpot CRM, archived in a "Qualified" Google Drive folder, and announced via Slack. Red Track: Unqualified candidates receive a personalized Gmail rejection including constructive feedback on skills they could improve. Closed-Loop Analytics - Logs every data point to PostgreSQL, calculating funnel metrics such as skill-match percentages and processing latency for continuous hiring strategy optimization. 💡 Key Technical Features Heuristic Skill Detection:** Uses NLP pattern matching to identify technical competencies even if they are phrased differently. Personalized Rejection Engine:** Automatically suggests specific skill areas (e.g., Cloud or Certifications) for candidates to work on based on what was missing from their resume. Forensic Archival:** Maintains a clean, searchable archive of all applicants in a hierarchical cloud structure. 🚀 Benefits ✅ 90% Faster Screening - Moves from manual reading to high-level candidate oversight instantly. ✅ Professional Employer Brand - Ensures every applicant receives a timely, personalized response. ✅ Data-Driven Hiring - Track exactly which sources and skill sets are performing best in your funnel. Tags: #recruitment #hr-tech #resume-parser #ai #hubspot #automation #pdf-to-json Category: Human Resources | Difficulty: Advanced

Automated Invoice Intelligence: PDF-to-JSON Financial Orchestrator 🎯 Description This is an elite enterprise-grade solution for Accounts Payable and Finance Ops teams. It automates the high-volume extraction of unstructured data from PDF invoices using the HTML to PDF (Parse PDF to JSON) node, transforming raw email attachments into validated, audit-ready financial records across multiple platforms. ✨ The Sovereign Lifecycle Intelligent Intake & Validation - Monitors Gmail for incoming invoices. Implements a strict validation layer to ensure only valid PDF binaries enter the intelligence stream, filtering out noise and non-invoice attachments. Atomic JSON Transformation - Leverages the HTML to PDF (Parse PDF to JSON) node to decompose monolithic PDF files into structured data objects. This allows the system to treat document text as actionable data points. AI Ledger Mapping - A sophisticated hybrid-intelligence Code Node acts as a virtual "Financial Controller." It uses advanced pattern matching to extract key fields (Vendor Name, Invoice Number, Tax, and Total Amount) and calculates a Confidence Score for every entry. Conditional Approval Gating - Implements a "Trust-but-Verify" architecture: Auto-Process: High-confidence extractions of standard value invoices are posted immediately. Human-in-the-Loop (HITL): Low-confidence results (<0.7) or high-value invoices (>$5,000) are automatically diverted to a Review Queue in Google Sheets. Multi-Platform Ledger Sync - Simultaneously synchronizes data across Google Sheets (for real-time reporting) and Airtable (for project management), ensuring a single source of truth. Forensic Archival & Alerts - Moves original files to a secure Google Drive archive. High-priority items trigger instant Slack and Gmail alerts for the finance team. 💡 Key Technical Features Heuristic Pattern Matching:** Dynamically handles various invoice layouts by analyzing financial context and keywords. Math Integrity Check:** Automatically verifies if (Subtotal + Tax = Total) to boost extraction confidence. Bi-Directional Governance:** Keeps track of every document with a unique Processing ID and metadata log for regulatory compliance. 🚀 Benefits ✅ 95% Reduction in Data Entry - Shifts human effort from manual typing to high-level oversight. ✅ Financial Risk Mitigation - Automatically flags high-value transactions and extraction anomalies before they hit the books. ✅ Real-Time Visibility - Instant updates to financial dashboards the moment an invoice is received. Tags: #finance #accounts-payable #pdf-to-json #automation #fintech #google-sheets #airtable Category: Finance & Operations | Difficulty: Advanced

Bulk Archival Decryption: AI-Powered Compliance Audit & Unlocking Engine 🎯 Description This is a high-security enterprise solution for LegalOps and Compliance departments. It automates the high-stakes process of decrypting batches of legacy, password-protected PDF assets to facilitate forensic indexing and search discovery. By utilizing the HTML to PDF (Unlock) node, it bridges the gap between inaccessible "dark data" and searchable compliance archives. ✨ The Sovereign Lifecycle Phase 1: Secure Intake & Forensic Fingerprinting - Fetches legacy binaries and generates an initial SHA-256 hash. This establishes a strict "Chain of Custody" before any modification occurs. Phase 2: Key Vault Orchestration - Integrates with a PostgreSQL Key Vault to automatically retrieve historical passwords based on file metadata, enabling the decryption of thousands of documents without manual intervention. Phase 3: Atomic Unlock sovereign - Utilizes the HTML to PDF (Unlock) node to strip owner and user passwords with cryptographic precision, restoring full text-extraction and print capabilities. Phase 4: Integrity Guard & Validation - A dedicated Code Node compares the original and unlocked file hashes to verify successful decryption. It calculates processing latency and logs comprehensive integrity statuses. Phase 5: Compliance-Ready Archival - Unlocked files are vaulted in a secure Google Drive "Audit Vault." Forensic metadata, including custody IDs and timestamps, are permanently logged to PostgreSQL. Phase 6: Incident Management - Features a robust error-handling "Quarantine Zone." Failed decryptions or invalid keys trigger immediate Slack alerts and moves the problematic files to a restricted folder for manual legal review. 💡 Key Technical Features Forensic Audit Trail:** Every processing event is recorded with non-repudiation tokens for regulatory auditors. Bi-Directional Governance:** Simultaneously updates PostgreSQL audit logs while managing physical file movements in cloud storage. Fail-Safe Validation:** Implements strict MIME-type and file-size validation to prevent the processing of malicious or corrupted binaries. 🚀 Benefits ✅ Zero Audit Gaps - Ensures 100% of legacy data is accessible for regulatory search and indexing. ✅ Reduced Legal Risk - Provides an immutable record of the decryption process for internal and external discovery. ✅ Instant Discovery - Drastically reduces the time required to "open" legacy archives for litigation or audits. Tags: #legalops #compliance #pdf-unlock #audit #governance #enterprise #cybersecurity Category: Legal & Compliance | Difficulty: Advanced

This workflow automatically converts unstructured internal documentation into clear, actionable Standard Operating Procedures (SOPs). Instead of manually rewriting internal knowledge, teams can upload or update documents and let AI generate consistent, step-by-step SOPs that are easy to follow and scale across the organization. How it works When a new or updated document is detected in Google Drive, the workflow extracts the content and splits it into manageable sections. AI then analyzes the material, identifies implicit steps, and generates a structured SOP with clear actions, responsibilities, and outcomes. A second AI pass refines clarity and consistency. Completed SOPs are saved to Google Docs, logged in Google Sheets, and shared with stakeholders via Slack or email. Who it’s for Operations teams Consulting firms Agencies and service businesses Scaling startups Internal enablement teams Requirements Google Drive & Docs Google Sheets OpenAI credentials Slack or Gmail Built by QuarterSmart Created by Hyrum Hurst, AI Automation Engineer at QuarterSmart, specializing in practical, production-ready AI automation systems. For custom SOP automation or enterprise setups: [email protected]

Who’s it for Property management teams handling leases, IDs, and compliance documents. What it does Automates document validation, reminders, escalation, and compliance reporting using AI and Google Sheets. How it works Uploaded documents are analyzed for completeness, logged, and monitored until compliant. Setup Connect Webhook, Drive, Sheets, AI, Email, and Slack. Customization Change reminder timing, add more document types, or expand validation rules. Created by QuarterSmart — Hyrum Hurst

Intelligent Financial Invoice Hub: AI Parsing, 3-Way Matching & Multi-Channel Alerting 🎯 Description This is an enterprise-grade solution designed for complex finance departments. It automates the entire accounts payable lifecycle by combining secure document handling, intelligent vendor mapping, 3-way reconciliation, and a sophisticated multi-channel notification engine. ✨ What This Workflow Does Multi-Channel Ingestion - Consolidates invoices arriving via Gmail, legacy IMAP servers, and direct vendor portal webhooks into a single processing stream. Advanced Security Layer - Automatically retrieves rotating encryption keys from a secure database and uses the HTML to PDF (Unlock) node to decrypt protected vendor statements. Fuzzy Vendor Identification - Uses intelligent string analysis to identify vendors despite name variations (e.g., "Amazon" vs. "AWS"), ensuring data consistency. Automated 3-Way Matching - Fetches the associated Purchase Order (PO) and Delivery Receipt, then uses the HTML to PDF (Merge) engine to create a verified "Audit Bundle" for compliance. AI-Driven Data Extraction - Parses line-item details, converts international currencies using live exchange rates, and detects early payment discounts to optimize cash flow. Enterprise Notification Engine - Slack: Instant escalation for high-value outliers (e.g., >$10k) or urgent invoices. Microsoft Teams: Direct alerts to Department Heads when items impact their specific budgets. Gmail: Delivers a daily processing success digest to the Finance Lead. 💡 Key Features 3-Way Reconciliation:** Prevents fraud and overpayment by validating quantities and prices across three distinct documents before ERP synchronization. Encrypted Document Handling:** Seamlessly manages password-protected PDFs without manual intervention. Currency Intelligence:** Automatically handles international vendor payments with real-time conversion and tax mapping. Budget Allocation:** Smartly assigns costs to specific department codes and project tags in your accounting software. 🔧 Technical Highlights Binary Buffer Management:** High-performance handling of multiple large PDF streams during the merge process. Fuzzy Matching Logic:** Robust vendor recognition that handles typos and naming variations. Hybrid Trigger Support:** Reliable execution via polling (Email) and real-time events (Webhooks). Modular Architecture:** Easy to adapt for Xero, QuickBooks, or custom SQL databases. 📦 What You'll Need HTML to PDF Node - Essential for the Unlock and Merge operations. Google Sheets - To serve as the Vendor Vault (decryption keys) and Master Audit Log. ERP Credentials - Access to Xero, QuickBooks, or Sage for bill creation. Communication Tools - Slack, Microsoft Teams, and a Gmail account. 🚀 Benefits ✅ Zero Manual Data Entry - Complete "Email-to-ERP" automation saves hours of administrative work. ✅ Eliminate Overpayments - 3-way matching ensures you only pay for exactly what was ordered and received. ✅ Real-Time Financial Visibility - Department heads are notified the moment their budget is impacted. ✅ Audit Readiness - Automatically maintains a complete digital paper trail for every single invoice. 🎨 Customization Options Thresholds:** Adjust the "High Value" IF-node to match your internal approval policies. Channels:** Easily swap Slack for Discord or Teams for SMS alerts (via Twilio). Currency:** Add or remove currency pairs in the Intelligence Engine code node. Tags: #finance #accounting #xero #3-way-match #pdf-automation #slack #enterprise #security Category: Finance & Accounting Difficulty: Advanced