Workflow Templates

🛡️ Automated AWS Key Compromise Remediation Description This n8n workflow provides a secure, enterprise-grade response system for AWS IAM access key compromises with built-in form submission and human approval mechanisms. When an AWS access key is suspected to be compromised, this workflow enables rapid containment through a secure web form interface with basic authentication, human approval via Slack, and automated damage prevention through immediate key deactivation, credential invalidation, and comprehensive security reporting. How This Workflow is Useful Secure Form-Based Response Authenticated Form Submission**: Secure web form with basic authentication for capturing compromise details Human Approval Workflow**: Slack-based approval system for sensitive security operations Rapid Key Deactivation**: Instantly disables compromised access keys after approval Credential Invalidation**: Creates and applies security policies to invalidate existing temporary credentials Policy Analysis**: Automatically scans and analyzes both inline and attached IAM policies for the affected user AI-Powered Reporting**: Generates detailed security reports with intelligent analysis and team notifications Business Value Reduces Mean Time to Response (MTTR)**: Automates manual security procedures that typically take hours Minimizes Security Exposure**: Immediate containment prevents potential data breaches and unauthorized resource access Ensures Compliance**: Provides audit trails and documentation required for security compliance frameworks Cost Prevention**: Prevents potential financial damage from compromised credentials being used maliciously Rapid Response Capability**: Streamlines security response procedures when incidents are detected Technical Benefits AWS Best Practices**: Implements official AWS security recommendations for key compromise response Scalable Architecture**: Handles multiple access keys and complex IAM policy structures Error Handling**: Robust error handling ensures workflow continues even if individual steps fail Audit Trail**: Complete logging of all actions taken during the incident response Integration Ready**: Easily integrates with existing security tools and notification systems Use Cases 1. Incident Response Automation Automated response to security alerts from AWS CloudTrail Integration with SIEM systems for immediate key compromise response 24/7 security monitoring and automated containment 2. Compliance and Audit Meeting regulatory requirements for incident response documentation Providing audit trails for security compliance frameworks (SOC 2, ISO 27001, PCI DSS) Demonstrating due diligence in security incident handling 3. Multi-Account Management Centralized security response across multiple AWS accounts Consistent incident response procedures across different environments Standardized security automation for enterprise AWS deployments 4. Security Training and Testing Security team training on AWS incident response procedures Tabletop exercises and security drills Testing and validation of security response capabilities Key Features Core Functionality ✅ Secure Form Interface: Web form with basic authentication for secure data submission ✅ Human Approval Gate: Slack-based approval workflow for sensitive operations ✅ Authenticated Data Processing: Secure handling of form submissions with validation ✅ Immediate Key Deactivation: Instant disabling of compromised credentials after approval ✅ Security Policy Generation: Automatic creation and attachment of credential invalidation policies ✅ Policy Analysis: Deep analysis of user permissions and attached policies ✅ AI Security Analysis: Intelligent security report generation with risk assessment ✅ Team Notifications: Real-time Slack notifications to security teams ✅ Comprehensive Logging: Complete audit trail of all response actions Technical Specifications Secure Form Interface**: Web form with basic authentication for secure data capture Human Approval System**: Slack-based approval workflow for sensitive operations AWS API Integration**: Direct integration with AWS IAM APIs Authentication Layer**: Basic auth protection for form submissions Error Handling**: Robust error handling with continuation on non-critical failures Scalable Processing**: Handles multiple policies and complex IAM structures Security Best Practices**: No hardcoded credentials, uses AWS credential management Modular Design**: Easy to customize and extend for specific organizational needs Prerequisites Required Credentials AWS Credentials** with IAM permissions for: ListAccessKeys, UpdateAccessKey ListUserPolicies, ListAttachedUserPolicies CreatePolicy, AttachUserPolicy GetPolicy, GetPolicyVersion, GetUserPolicy Required Integrations Slack Workspace** for approval workflow and team notifications Basic Authentication Setup** for secure form access Optional Integrations AI Language Model** (Claude/OpenAI) for intelligent security analysis and report generation Installation and Setup Import the workflow into your n8n instance Configure AWS credentials in n8n credential manager Set up basic authentication for the secure form interface Configure Slack integration for approval notifications and team alerts Set up AI model (optional) for enhanced security analysis and reporting Configure approval workflow in Slack for human oversight Test in development environment before production use Workflow Inputs Secure Form Submission This workflow uses a secure web form with basic authentication to capture compromise details: Username**: The AWS IAM username of the compromised account Access Key ID**: The specific access key ID that has been compromised Authentication & Approval Process Form Authentication: Basic authentication protects the submission form Data Processing: Secure handling and validation of submitted credentials Human Approval: Slack notification sent to security team for approval Automated Execution: Upon approval, the workflow executes the security response This multi-layered approach ensures that sensitive security operations require both authentication and human oversight before execution. 🚀 Automate with Slack Integration Want to fully automate and simplify this workflow? Connect it with Slack for seamless team collaboration and instant response capabilities! Interactive Slack Automation Combine this AWS Key Compromise Response workflow with our Interactive Slack Approval & Data Submission System to create a fully automated incident response pipeline: Instant Slack Alerts**: Receive immediate notifications when key compromises are detected One-Click Response**: Trigger the AWS response workflow directly from Slack with interactive buttons Team Collaboration**: Enable security teams to respond collectively through Slack channels Approval Workflows**: Add human approval gates before executing critical security actions Real-time Updates**: Get live status updates and completion notifications in Slack How the Complete Solution Works Detection: External security monitoring tools (CloudTrail, SIEM, etc.) detect potential key compromise Secure Form Access: Security team accesses the authenticated web form to submit compromise details Form Submission: Credentials are securely submitted through the basic auth-protected form Human Approval: Slack notification sent to security team for review and approval Approved Execution: Upon approval, the AWS security response executes automatically Real-time Updates: Progress and completion notifications sent back to Slack Security Analysis: AI-powered analysis and comprehensive reporting delivered to the team Get Started with Full Automation To enable automatic notifications and complete the automation pipeline, use the Interactive Slack Approval & Data Submission System with Webhooks workflow: https://n8n.io/workflows/5049-interactive-slack-approval-and-data-submission-system-with-webhooks/ This integration transforms manual security responses into streamlined, team-collaborative automation that reduces response time from hours to minutes. Security Considerations Form Authentication**: Basic authentication protects the submission interface Human Approval Gate**: Slack-based approval prevents unauthorized execution AWS Credential Management**: Uses AWS credential management best practices No Sensitive Data Storage**: No sensitive data stored in workflow configuration Least-Privilege Access**: Implements least-privilege access principles Complete Audit Trails**: Provides complete audit trails for compliance Secure Data Processing**: Encrypted handling of form submissions and approvals Immediate Damage Prevention**: Designed for rapid containment after approval ⚠️ Important Disclaimer Use with Caution: Disabling access keys without proper understanding can significantly impact your personal or business operations. This workflow immediately deactivates AWS access keys, which may disrupt running applications, automated processes, or services that depend on these credentials. AWS Best Practices Recommendation: Use IAM Roles instead of Access Keys** whenever possible for enhanced security IAM roles provide temporary credentials and eliminate the need for long-term access keys Follow the principle of least privilege when assigning permissions Regularly rotate and audit your AWS credentials Implement proper monitoring and alerting for credential usage Before Using This Workflow: Ensure you understand which services and applications use the target access key Have a rollback plan in case of accidental disruption Test in a non-production environment first Coordinate with your team before executing in production For comprehensive AWS security best practices, refer to the AWS Security Best Practices Guide. For more workflows and automation solutions, visit: https://n8n.io/creators/niranjan/

Quick overview Three specialized AI agents: Researcher, Writer, and Reviewer, collaborate autonomously to research a topic, draft content, and quality-check it through a self-correcting review loop with a circuit breaker. Approved content is published directly to Notion with full audit metadata. How it works A form submission captures the research topic, content format (blog post, exec summary, or LinkedIn post), target audience, and maximum revision cycles allowed before the circuit breaker fires. The Researcher Agent uses GPT-4o and Tavily Search to gather authoritative sources, extract key facts and contradictions, and produce a validated research brief. Search depth and result count are automatically scaled to the requested format. The Writer Agent receives the research brief and produces a structured draft in the correct format. On revision cycles it also receives the Reviewer's specific rejection notes and must address them directly. A Circuit Breaker sits between the Writer and Reviewer. If the number of Reviewer rejections reaches the user-defined maximum, the draft is force-approved and the pipeline proceeds to publishing without another LLM call. The Reviewer Agent evaluates the draft against the original sources on three axes — accuracy, clarity, and completeness — each scored 0–10. All three must score 7 or above for approval. On rejection, detailed revision notes are injected back into the Writer's next prompt. Once approved (or circuit-broken), the pipeline builds a full Notion block structure including a metadata callout with scores and revision stats, then creates the Notion page and appends content blocks in rate-limited batches of 25. After the batch loop completes, a post-loop aggregation step checks for any failed batches and appends a warning callout to the Notion page if needed. A separate Error Trigger path logs any pipeline failures to a Notion monitoring database. Setup Open the Initialize State Variables code node and replace the two placeholder constants at the top: NOTION_CONTENT_DB_ID with your content database ID and NOTION_MONITORING_DB_ID with your monitoring database ID. Add your OpenAI API credential to all three chat model nodes: OpenAI GPT-4 Agent 1 (Researcher), OpenAI GPT-4 Agent 2 (Writer), and OpenAI GPT-4 Agent 3 (Reviewer). Add your Tavily API credential to the Perform Tavily Search tool node inside the Researcher Agent. Add your Notion API credential to the Generate Notion Page and Log to Notion on Error nodes. The two HTTP Request nodes that append blocks (Append Blocks to Notion, Add Warning Notification) use the same Notion credential type and will prompt you on first run. In your Notion workspace, share both databases (content and monitoring) with your Notion integration. The content database needs at minimum a Title property. The monitoring database needs Title, and optionally text properties for Failed Node, Error Message, and Execution ID. Requirements OpenAI API key (GPT-4o) Tavily API key Notion API integration with access to a content database and a monitoring database Customization Swap GPT-4o for any other n8n-compatible chat model by replacing the three OpenAI Chat Model nodes Adjust the Reviewer's approval threshold (currently 7/10 on all three axes) inside the Reviewer Agent prompt Change the circuit breaker limit at form submission — no code changes needed, it's a form field Modify batch size (default 25 blocks) or rate-limit wait (default 350ms) in Prepare Notion Block Batches and Wait 350ms nodes Edit agent system prompts and format requirements to support additional content types beyond blog post, exec summary, and LinkedIn post

Quick overview This scheduled workflow scrapes BizQuest listings via an Apify API, deduplicates them against a Google Sheet, scores buyer fit with Anthropic Claude, and for high-fit deals generates broker outreach copy and sends a formatted alert to Slack while logging all scored listings to Google Sheets. How it works Runs daily on a cron schedule (default 5:00 AM). Sends a POST request to the Apify BizQuest scraper task using your buy-box filters and normalizes the returned listings, estimating SDE as 10% of revenue when missing. Sorts listings by SDE, keeps the top 100, and processes them one by one. Checks Google Sheets for the listing link and skips any listing that already exists. Uses Anthropic Claude (Haiku) to score buyer fit (1–5) and output a short rationale and confidence level for each new listing. Appends low-scoring deals (1–3) to Google Sheets for audit tracking. For deals scoring 4–5, uses Anthropic Claude (Sonnet) to draft a broker outreach message, appends the enriched row to Google Sheets, and posts a Slack message with the deal details and copy-ready outreach text. Setup Add credentials for Google Sheets (OAuth2), Slack (OAuth2), and Anthropic. Create a Google Sheet with matching columns (including Link, Fit Score, Fit Rationale, Fit Confidence, and Broker Message) and replace YOUR_GOOGLE_SHEET_ID in both Google Sheets nodes. Update the Apify task API URL in the HTTP request node and ensure it points to your BizQuest scraper task. Edit the buy-box fields (buyBox text, keyword, cashFlowMin, priceMax, listingAgeDays) and set the target Slack user/channel ID for alerts.

Meeting Notes Distributor – Mailchimp and MongoDB This workflow automatically converts raw meeting recordings or written notes into concise summaries, stores them in MongoDB for future reference, and distributes the summaries to all meeting participants through Mailchimp. It is ideal for teams that want to keep everyone aligned without manual copy-and-paste or email chains. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or cloud) Audio transcription service or written notes available via HTTP endpoint MongoDB database (cloud or self-hosted) Mailchimp account with an existing Audience list Required Credentials MongoDB** – Connection string with insert permission Mailchimp API Key** – To send campaigns (Optional) HTTP Service Auth** – If your transcription/notes endpoint is secured Specific Setup Requirements | Component | Example Value | Notes | |------------------|--------------------------------------------|-----------------------------------------------------| | MongoDB Database | meeting_notes | Database in which summaries will be stored | | Collection Name | summaries | Collection automatically created if it doesn’t exist| | Mailchimp List | Meeting Participants | Audience list containing participant email addresses| | Notes Endpoint | https://example.com/api/meetings/{id} | Returns raw transcript or note text (JSON) | How it works This workflow automatically converts raw meeting recordings or written notes into concise summaries, stores them in MongoDB for future reference, and distributes the summaries to all meeting participants through Mailchimp. It is ideal for teams that want to keep everyone aligned without manual copy-and-paste or email chains. Key Steps: Schedule Trigger**: Fires daily (or on-demand) to check for new meeting notes. HTTP Request**: Downloads raw notes or transcript from your endpoint. Code Node**: Uses an AI or custom function to generate a concise summary. If Node**: Skips processing if the summary already exists in MongoDB. MongoDB**: Inserts the new summary document. Split in Batches**: Splits participants into Mailchimp-friendly batch sizes. Mailchimp**: Sends personalized summary emails to each participant. Wait**: Ensures rate limits are respected between Mailchimp calls. Merge**: Consolidates success/failure results for logging or alerting. Set up steps Setup Time: 15-25 minutes Clone the workflow: Import or copy the JSON into your n8n instance. Configure Schedule Trigger: Set the cron expression (e.g., every weekday at 18:00). Set HTTP Request URL: Replace placeholder with your transcription/notes endpoint. Add auth headers if needed. Add MongoDB Credentials: Enter your connection string in the MongoDB node. Customize Summary Logic: Open the Code node to tweak summarization length, language, or model. Mailchimp Credentials: Supply your API key and select the correct Audience list. Map Email Fields: Ensure participant emails are supplied from transcription metadata or external source. Test Run: Execute once manually to verify MongoDB insert and email delivery. Activate Workflow: Enable the workflow so it runs on its defined schedule. Node Descriptions Core Workflow Nodes: Schedule Trigger** – Initiates the workflow at predefined intervals. HTTP Request** – Retrieves the latest meeting data (transcript or notes). Code** – Generates a summarized version of the meeting content. If** – Checks MongoDB for duplicates to avoid re-sending. MongoDB** – Stores finalized summaries for archival and audit. SplitInBatches** – Breaks participant list into manageable chunks. Mailchimp** – Sends summary emails via campaigns or transactional messages. Wait** – Pauses between batches to honor Mailchimp rate limits. Merge** – Aggregates success/failure responses for logging. Data Flow: Schedule Trigger → HTTP Request → Code → If If summary is new: MongoDB → SplitInBatches → Mailchimp → Wait Merge collates all results Customization Examples 1. Change Summary Length // Inside the Code Node const rawText = items[0].json.text; const maxSentences = 5; // adjust to 3, 7, etc. items[0].json.summary = summarize(rawText, maxSentences); return items; 2. Personalize Mailchimp Subject // In the Set node before Mailchimp items[0].json.subject = Recap: ${items[0].json.meetingTitle} – ${new Date().toLocaleDateString()}; return items; Data Output Format The workflow outputs structured JSON data: { "meetingId": "abc123", "meetingTitle": "Quarterly Planning", "summary": "Key decisions on roadmap, budget approvals...", "participants": [ "alice@example.com", "bob@example.com" ], "mongoInsertId": "65d9278fa01e3f94b1234567", "mailchimpBatchIds": ["2024-01-01T12:00:00Z#1", "2024-01-01T12:01:00Z#2"] } Troubleshooting Common Issues Mailchimp rate-limit errors – Increase Wait node delay or reduce batch size. Duplicate summaries – Ensure the If node correctly queries MongoDB using meeting ID as a unique key. Performance Tips Keep batch sizes under 500 to stay well within Mailchimp limits. Offload AI summarization to external services if Code node execution time is high. Pro Tips: Store full transcripts in MongoDB GridFS for future reference. Use environment variables in n8n for all API keys to simplify workflow export/import. Add a notifier (e.g., Slack node) after Merge to alert admins on failures. This is a community template provided “as-is” without warranty. Always validate the workflow in a test environment before using it in production.

Quick overview This workflow runs daily to audit rows in a Google Sheets ComplianceRecords tab using two OpenAI checks, automatically marking compliant items, fixing safe issues, and escalating unresolved violations to Telegram, while logging every outcome to an AuditLog sheet and posting errors to Slack. How it works Runs every 24 hours on a schedule trigger. Reads all records from the Google Sheets ComplianceRecords worksheet. Sends each record to OpenAI (GPT-4o-mini) for a first-pass compliance screen and parses the JSON result. Marks records with no violations as Compliant and routes flagged records to a second OpenAI (GPT-4o-mini) review to classify them as false positives, auto-fixable issues, or true violations. Updates Google Sheets with the corrected value for auto-fixable records, sends a Telegram message to the compliance team for records requiring human review, and labels false positives as resolved. Merges all outcomes and appends a timestamped entry to the Google Sheets AuditLog worksheet, while sending Slack alerts if the AI steps or overall workflow error. Setup Add OpenAI credentials for both OpenAI nodes and ensure the selected model (gpt-4o-mini) is available in your account. Add Google Sheets OAuth2 credentials, create a spreadsheet with ComplianceRecords and AuditLog tabs, and replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes. Add Telegram Bot credentials and replace YOUR_COMPLIANCE_TEAM_CHAT_ID with the destination chat ID for escalations. Add Slack OAuth2 credentials and replace YOUR_SLACK_CHANNEL_ID in all Slack alert nodes. Confirm ComplianceRecords includes the expected columns (for example RecordID, RecordType, DataField, Value, Description, Department, Status) and adjust the schedule interval if you want a different audit frequency.

Automatically fetches daily sales, shifts, and receipts from Loyverse. Calculates gross profit, net operating profit, other key metrics, saves them to a Google Sheet and sends out a daily report via email. Who’s it for This template is for any business owner, manager, or analyst using Loyverse POS who needs more advanced financial reporting. If you're a restaurant, bar, or retail owner who wants to automatically track daily net profit, compare sales to historical averages, and build a custom financial dashboard in Google Sheets, this workflow is for you. How it works / What it does This workflow runs automatically on a daily schedule. It fetches all sales data and receipts from your Loyverse account for the previous business day, defined by your custom shift times (even past midnight). A powerful Code node then processes all the data to calculate the metrics that Loyverse either doesn't provide at all, or only spreads out across several separate reports instead of in one consolidated place. Already set up are metrics like... -Total Revenue, Gross Profit, and Net Operating Profit Cash handling differences (over/under) Average spend per receipt (ATV) 30-day rolling Net Operating Profit (NOP) Performance vs. your historical weekday average Finally, it appends the single, calculated row of daily metrics to a Google Sheet and sends an easily customizable summary report to your email. How to set up This workflow includes detailed Sticky Notes to guide you through the setup process. Because every business has a unique POS configuration (different POS devices, categories, and payment types), you'll need to set up a few things manually before executing the workflow. I've tried to make this as easy as possible to follow, and the entire setup should only take about 15 minutes. Preparations & Credential setup Subscribe to "Integrations" Add-on in Loyverse ($9 / month) to gain API access. Create an Access token in Loyverse Create Credentials: In your n8n instance, create credentials for Loyverse (use "Generic" > "Bearer Auth"), Google Sheets (OAuth2), and your Email (SMTP or other). Make a copy of a prep-configured Google Spreadsheet (Link in the second sticky note inside the workflow). Fill MASTER CONFIG: Open the MASTER CONFIG node. Follow the comments inside to add your Google Sheet ID, Sheet Names, business hours, timezone, and Loyverse IDs (for POS devices, payment types, and categories). Configure Google Sheet Nodes Configure Read Historical Data: Open this node. Follow the instructions in the nearby Sticky Note to paste the expressions for your Document ID and Sheet Name. Configure Save Product List: Open this node. Paste in the expressions for Document ID and Sheet Name. The column mapper will load; map your sheet columns (e.g., item_name) to the data on the left (e.g., {{ $json.item_name }}). Configure Save Latest Sales Data: Open this node. Paste in the expressions for Document ID and Sheet Name. Save and run the workflow. After that, the column mapper will load. This is the most important step: map your sheet's column names (e.g., "Total Revenue") to the calculated metrics from the Calculate All Metrics node (e.g., {{ $json.totalGrossRevenue }}). Activate the workflow. 🫡 Requirements Loyverse Integrations Subscription Loyverse Access Token Credentials for Loyverse (Bearer Auth) Credentials for Google Sheets (OAuth2) Credentials for Email/SMTP sender How to customize the workflow This template is designed to be highly flexible. Central Configuration: Almost all customization (POS devices, categories, payment types, sheet names) is done in the MASTER CONFIG node. You don't need to dig through other nodes. Add/Remove Metrics: The Calculate All Metrics node has additional metrics already set up, just add the relevant collumns to the SalesData sheet or even add your own calculations to the node. Any new metric you add (e.g., metrics.myNewMetric = 123) will be available to map in the Save Latest Sales Data node. Email Body: You can easily edit the Send email node to change the text or add new metrics from the Calculate All Metrics node.

Quick overview This workflow watches a Google Drive inbox folder for new files, posts an approval card with buttons to a Discord channel, and moves the file to an approved or rework folder based on the response, while logging each decision to Google Sheets. How it works Polls a specified Google Drive folder every 5 minutes and triggers when a new file is created. Loads review settings (Discord server/channel IDs, approved/rejected folder IDs, and logging sheet details) and formats the file metadata into a Discord-ready review card with a preview link. Posts the review card to a Discord channel with Approve and Send back buttons and waits up to the configured decision window for a response. Routes the outcome based on the button response, moving the file in Google Drive to the approved folder or the rejected/rework folder, or leaving it in the inbox if no one responds. Resolves the final status (including move failures) and appends a decision record to a Google Sheets log. Posts a receipt message back to the Discord review channel and continues to the next file. Setup Add Google Drive OAuth2 credentials and provide the inbox folder ID plus destination folder IDs for approved and rejected/rework files. Create a Discord application/bot, add Discord bot credentials in n8n, invite the bot to your server, and set the guild ID and review channel ID. Add Google Sheets OAuth2 credentials, create a decision log spreadsheet with the required columns, and set the sheet URL and tab name in the settings. Ensure your n8n instance is reachable via its public webhook URL (and WEBHOOK_URL is set correctly) so Discord button interactions can be completed. Review and adjust the decision window (hours) and polling interval to match your operational needs, then test by uploading a file to the inbox. Requirements A Discord server you can add a bot to with Send Messages on the review channel. No privileged intents, because this never reads message content or the member list. Three Google Drive folders: an inbox to watch, an approved destination and a rework destination. A Google account with a spreadsheet for the decision log. n8n with Discord Bot API, Google Drive and Google Sheets credentials. No paid plan, no AI model, no third-party service. Customization Set driveId in the settings node to a shared drive ID if your deliverables do not live in My Drive. It ships as My Drive. Rename the Approve and Send back button labels freely. The routing keys on the returned boolean, not on the wording. Point both destination folders at the same folder if you want a decision log without the filing. Extend the review card in the formatting step to carry anything Drive returns, such as the owner or the last editor. Additional info The detail worth knowing before you rely on this is what happens when nobody answers. The routing has three outcomes rather than two: an expired decision window leaves the file in the inbox and logs it as No response, so a Friday evening deliverable is never quietly demoted to the rework folder over the weekend and the log never records a rejection that no human made. The two Drive move nodes are likewise caught per file instead of being left to stop the run, so one file that Drive refuses cannot strand the rest of the batch behind it, and a failed move is logged with the error while the file stays put. Between those two, every row in the decision sheet is either something a person actually decided or an error you can act on, which is what makes the log usable as an audit trail rather than just a record of executions.

Zoho CRM → AI Sentiment Analysis for customer interactions & Automatic Alerts Workflow This workflow analyzes newly created Notes (in Any module) in Zoho CRM, detects customer sentiment using an AI model, updates the related CRM record with custom fields - sentiment label and score, and sends an instant alert whenever negative sentiment is detected. It runs on a scheduled interval and gives teams real-time visibility into customer emotions and potential risks. Quick Implementation Steps Connect Zoho CRM OAuth2 credentials Add custom fields in Zoho CRM: Sentiment_Label and Sentiment_Score Add AI provider credentials Set Gmail alert recipient Activate workflow and test by adding a Note What It Does This workflow automatically monitors Zoho CRM Notes. When a new Note is detected, the text is extracted and analyzed through an AI-powered sentiment model. The AI classifies the text as Positive, Neutral or Negative and produces a numeric sentiment score. The workflow updates the related CRM module with these values. If the sentiment is negative, a Gmail alert is triggered so your team can follow up quickly. This automation helps organizations maintain high customer satisfaction and detect potential issues early. Who’s It For Support teams Sales teams CRM administrators Customer success managers Businesses needing automated customer sentiment tracking Requirements n8n instance Zoho CRM OAuth2 credentials Gmail OAuth2 credentials AI provider key Custom fields in Zoho CRM: Sentiment_Label & Sentiment_Score (if you are using different field name then do changes in workflow accoredingly) How It Works & Setup Step 1: Schedule Trigger Runs periodically to check for new or updated Notes. Step 2: Fetch Latest Note Retrieves the most recently modified Note. Step 3: Extract Details Extracts Note text, note_id, parent_id and module name. Step 4: AI Sentiment Analysis Sends text to the AI (via LangChain chain) for sentiment classification. Step 5: Conditional Branching If Negative: Send Gmail alert and update CRM Otherwise: Just update CRM Step 6: Update CRM Writes sentiment data back into the related parent record. How to Customize Nodes Adjust sentiment output by modifying the AI prompt. Change field mappings in Zoho update nodes. Customize the Gmail alert message. Adjust Schedule Trigger frequency. Add additional metadata (e.g., emotion tags). Add‑Ons Slack/Teams alerts for negative sentiment. Historical sentiment logging. Weekly sentiment reports. Auto-task creation for negative interactions. Priority-based escalation logic. Use Case Examples Detect unhappy customers in support interactions. Monitor sentiment across sales conversations. Escalate negative feedback automatically. Quality assurance tracking for customer interactions. Early detection of churn indicators. Troubleshooting Guide | Issue | Possible Cause | Solution | |------|----------------|----------| | Sentiment not updating | Missing Zoho fields | Add custom fields in CRM | | Note not detected | Fetching only latest note | Increase frequency or widen fetch scope | | AI output invalid | Prompt mismatch | Update prompt and parser | | Alerts not sending | Gmail OAuth expired | Reconnect Gmail | | Incorrect sentiment | Weak prompt instructions | Refine prompt wording | Need Help? WeblineIndia can help you configure, customize and extend workflows like this. We specialize in: n8n automation CRM integrations AI/LLM-powered workflows Zoho CRM customization Reach out if you'd like assistance building or enhancing similar n8n automation solutions.

📊 Description Ensure your GitHub repositories stay configuration-accurate and documentation-compliant with this intelligent AI-powered validation workflow. 🤖 This automation monitors repository updates, compares configuration files against documentation references, detects inconsistencies, and alerts your team instantly—streamlining DevOps and compliance reviews. ⚡ What This Template Does Step 1: Triggers automatically on GitHub push or pull_request events. 🔄 Step 2: Fetches both configuration files (config/app-config.json and faq-config.json) from the repository. 📂 Step 3: Uses GPT-4o-mini to compare configurations and detect mismatches, missing keys, or deprecated fields. 🧠 Step 4: Categorizes issues by severity—critical, high, medium, or low—and generates actionable recommendations. 🚨 Step 5: Logs all discrepancies to Google Sheets for tracking and audit purposes. 📑 Step 6: Sends Slack alerts summarizing key issues and linking to the full report. 💬 Key Benefits ✅ Prevents production incidents due to config drift ✅ Ensures documentation stays in sync with code changes ✅ Reduces manual review effort with AI-driven validation ✅ Improves team response with Slack-based alerts ✅ Maintains audit logs for compliance and traceability Features Real-time GitHub webhook integration AI-powered config comparison using GPT-4o-mini Severity-based issue classification Automated Google Sheets logging Slack alerts with detailed issue context Error handling for malformed JSON or parsing issues Requirements GitHub OAuth2 credentials with repo and webhook permissions OpenAI API key (GPT-4o-mini or compatible model) Google Sheets OAuth2 credentials Slack API token with chat:write permissions Target Audience DevOps teams ensuring consistent configuration across environments Engineering leads maintaining documentation accuracy QA and Compliance teams tracking configuration changes and risks Setup Instructions Create GitHub OAuth2 credentials and enable webhook access. Connect your OpenAI API key under credentials. Add your Google Sheets and Slack integrations. Update file paths (config/app-config.json and faq-config.json) if your repo uses different names. Activate the workflow — it will start validating on every push or PR. 🚀

Description How it works This powerful workflow helps businesses and freelancers automatically manage invoices received on WhatsApp. It detects new messages, downloads attached invoices, extracts key data using OCR (Optical Character Recognition), summarizes the details with AI, updates Google Sheets for record-keeping, saves files to Google Drive, and instantly replies with a clean summary message all without manual effort. Perfect for small businesses, agencies, accountants, and freelancers who regularly receive invoices via WhatsApp. Say goodbye to manual data entry and hello to effortless automation. Set up steps Setup takes around 10–15 minutes: Connect your WhatsApp Cloud API to trigger incoming messages. Add your OCR.Space API key to extract invoice text. Link your Google Sheets and Google Drive accounts for data logging and storage. Enter your OpenAI API key for AI-based summarization. Import the template, test once, and you’re ready to automate your invoice workflow. Why use this workflow Save hours of manual data entry Keep all invoices safely stored and organized in Drive Get instant summaries directly in WhatsApp Improve efficiency for client billing, and expense tracking.

Automatically turns trending Reddit posts into punchy, first-person tweets powered by Google Gemini AI, Reddit, and Twitter API, with Google Sheets logging. 🧩 Overview This workflow repurposes Reddit content into original tweets every few hours. It’s perfect for creators, marketers, or founders who want to automate content inspiration while keeping tweets sounding human, edgy, and fresh. Core automation loop: Fetch trending Reddit posts from selected subreddits. Use Gemini AI to write a short, first-person tweet. Check your Google Sheet to avoid reusing the same Reddit post. Publish to Twitter automatically. Log tweet + Reddit reference in Google Sheets. 🧠 Workflow Diagram 🪄 How It Works 1️⃣ Every 2 hours → the workflow triggers automatically. 2️⃣ It picks a subreddit (like r/automation, r/n8n, r/SaaS). 3️⃣ Gemini AI analyzes a rising Reddit post and writes a fresh, short tweet. 4️⃣ The system checks your Google Sheet to ensure it hasn’t used that Reddit post before. 5️⃣ Once validated, the tweet is published via Twitter API and logged. 🧠 Example Tweet Output 📊 Logged Data (Google Sheets) Each tweet is automatically logged for version control and duplication checks. | Date | Subreddit | Post ID | Tweet Text | |------|------------|----------|-------------| | 08/10/2025 | n8n_ai_agents | 1o16ome | Just saw a wild n8n workflow on Reddit... | ⚙️ Key Components | Node | Function | |------|-----------| | Schedule Trigger | Runs every 2 hours to generate a new tweet. | | Code (Randomly Decide Subreddit) | Picks one subreddit randomly from your preset list. | | Gemini Chat Model | Generates tweet text in first person tone using custom prompt rules. | | Reddit Tool | Fetches top or rising posts from the chosen subreddit. | | Google Sheets (read database) | Keeps a record of already-used Reddit posts. | | Structured Output Parser | Ensures consistent tweet formatting (tweet text, subreddit, post ID). | | Twitter Node | Publishes the AI-generated tweet. | | Append Row in Sheet | Logs the tweet with date, subreddit, and post ID. | 🧩 Setup Tutorial 1️⃣ Prerequisites | Tool | Purpose | |------|----------| | n8n Cloud or Self-Host | Workflow execution | | Google Gemini API Key | For tweet generation | | Reddit OAuth2 API | To fetch posts | | Twitter (X) API OAuth2 | To publish tweets | | Google Sheets API | For logging and duplication tracking | 2️⃣ Import the Workflow Download Reddit Twitter Automation.json. In n8n, click Import Workflow → From File. Connect your credentials: Gemini → Gemini Reddit → Reddit account Twitter → X Google Sheets → Gsheet 3️⃣ Configure Google Sheet Your sheet must include these columns: | Column | Description | |--------|--------------| | PAST TWEETS | The tweet text | | Date | Auto-generated date | | subreddit | Reddit source | | post_id | Reddit post reference | 4️⃣ Customize Subreddits In the Code Node, update this array to choose which subreddits to monitor: const subreddits = [ "n8n", "microsaas", "SaaS", "automation", "n8n_ai_agents" ];

🛒 Smart Telegram Shopping Assistant with AI Product Recommendations Workflow Overview Target User Role: E-commerce Business Owners, Affiliate Marketers, Customer Support Teams Problem Solved: Businesses need an automated way to help customers find products on Telegram without manual intervention, while providing intelligent recommendations that increase conversion rates. Opportunity Created: Transform any Telegram channel into a smart shopping assistant that can handle both product queries and customer conversations automatically. What This Workflow Does This workflow creates an intelligent Telegram bot that: 🤖 Automatically detects** whether users are asking about products or just chatting 🛒 Scrapes Amazon** in real-time to find the best matching products 🎯 Uses AI to analyze and rank** products based on price, ratings, and user needs 📱 Delivers perfectly formatted** recommendations optimized for Telegram 💬 Handles casual conversations** professionally when users aren't shopping Real-World Use Cases E-commerce Support**: Reduce customer service workload by 70% Affiliate Marketing**: Automatically recommend products with tracking links Telegram Communities**: Add shopping capabilities to existing channels Product Discovery**: Help customers find products they didn't know existed Key Features & Benefits 🧠 Intelligent Intent Detection Uses Google Gemini AI to understand user messages Automatically routes to product search or conversation mode Handles multiple languages and casual typing styles 🛒 Real-Time Product Data Integrates with Apify's Amazon scraper for live data Fetches prices, ratings, reviews, and product details Processes up to 10 products per search instantly 🎯 AI-Powered Recommendations Analyzes multiple products simultaneously Ranks by relevance, value, and user satisfaction Provides top 5 personalized recommendations with reasoning 📱 Telegram-Optimized Output Perfect formatting with emojis and markdown Respects character limits for mobile viewing Includes direct purchase links for easy buying Setup Requirements Required Credentials Telegram Bot Token - Free from @BotFather Google Gemini API Key - Free tier available at AI Studio Apify API Token - Free tier includes 100 requests/month Required n8n Nodes @n8n/n8n-nodes-langchain (for AI functionality) Built-in Telegram, HTTP Request, and Code nodes Quick Setup Guide Step 1: Telegram Bot Creation Message @BotFather on Telegram Create new bot with /newbot command Copy the bot token to your credentials Step 2: AI Configuration Sign up for Google AI Studio Generate API key for Gemini Add credentials to all three AI model nodes Step 3: Product Scraping Setup Register for free Apify account Get API token from dashboard Add token to "Amazon Product Scraper" node Step 4: Activation Import workflow JSON Add your credentials Activate the Telegram Trigger Test with a product query! Workflow Architecture 📱 Message Entry Point Telegram Trigger receives all messages 🧹 Query Preprocessing Cleans and normalizes user input for better search results 🤖 AI Intent Classification Determines if message is product-related or conversational 🔀 Smart Routing Directs to appropriate workflow path based on intent 💬 Conversation Path Handles greetings, questions, and general support 🛒 Product Search Path Scrapes Amazon → Processes data → AI analysis → Recommendations 📤 Optimized Delivery Formats and sends responses back to Telegram Customization Opportunities Easy Modifications Multiple Marketplaces**: Add eBay, Flipkart, or local stores Product Categories**: Specialize for electronics, fashion, etc. Language Support**: Translate for different markets Branding**: Customize responses with your brand voice Advanced Extensions Price Monitoring**: Set up alerts for price drops User Preferences**: Remember customer preferences Analytics Dashboard**: Track popular products and queries Affiliate Integration**: Add commission tracking links Success Metrics & ROI Performance Benchmarks Response Time**: 3-5 seconds for product queries Accuracy**: 90%+ relevant product matches User Satisfaction**: 85%+ positive feedback in testing Business Impact Reduced Support Costs**: Automate 70% of product inquiries Increased Conversions**: Personalized recommendations boost sales 24/7 Availability**: Never miss a customer inquiry Scalability**: Handle unlimited concurrent users Workflow Complexity Intermediate Level - Requires API setup but includes detailed instructions. Perfect for users with basic n8n experience who want to create something powerful.