Moderate your Discord server using chatGPT-5 & Google Sheets (Learning system)
Discord AI Content Moderator with Learning System
This n8n template demonstrates how to automatically moderate Discord messages using AI-powered content analysis that learns from your community standards. It continuously monitors your server, intelligently flags problematic content while allowing context-appropriate language, and provides a complete audit trail for all moderation actions.
Use cases are many:
Try moderating a forex trading community where enthusiasm runs high, protecting a gaming server from toxic behavior while keeping banter alive, or maintaining professional standards in a business Discord without being overly strict!
Good to know
- This workflow uses OpenAI's GPT-5 Mini model which incurs API costs per message analyzed (approximately $0.001-0.003 per moderation check depending on message volume)
- The workflow runs every minute by default - adjust the Schedule Trigger interval based on your server activity and budget
- Discord API rate limits apply - the batch processor includes 1.5-second delays between deletions to prevent rate limiting
- You'll need a Google Sheet to store training examples - a template link is provided in the workflow notes
- The AI analyzes context and intent, not just keywords - "I **cking love this community" won't be deleted, but "you guys are sh*t" will be
- Deleted messages cannot be recovered from Discord - the admin notification channel preserves the content for review
How it works
- The Schedule Trigger activates every minute to check for new messages requiring moderation
- We'll fetch training data from Google Sheets containing labeled examples of messages to delete (with reasons) and messages to keep
- The workflow retrieves the last 10 messages from your specified Discord channel using the Discord API
- A preparation node formats both the training examples and recent messages into a structured prompt with unique indices for each message
- The AI Agent (powered by GPT-5 Mini) analyzes each message against your community standards, considering intent and context rather than just keywords
- The AI returns a JSON array of message indices that violate guidelines (e.g., [0, 2, 5])
- A parsing node extracts these indices, validates them, removes duplicates, and maps them to actual Discord message objects
- The batch processor loops through each flagged message one at a time to prevent API rate limiting and ensure proper error handling
- Each message is deleted from Discord using the exact message ID
- A 1.5-second wait prevents hitting Discord's rate limits between operations
- Finally, an admin notification is posted to your designated admin channel with the deleted message's author, ID, and original content for audit purposes
How to use
- Replace the Discord Server ID, Moderated Channel ID, and Admin Channel ID in the "Edit Fields" node with your server's specific IDs
- Create a copy of the provided Google Sheets template with columns: message_content, should_delete (YES/NO), and reason
- Connect your Discord OAuth2 credentials (requires bot permissions for reading messages, deleting messages, and posting to channels)
- Add your OpenAI API key to access GPT-5 Mini
- Customize the AI Agent's system message to reflect your specific community standards and tone
- Adjust the message fetch limit (default: 10) based on your server activity - higher limits cost more per run but catch more violations
- Consider changing the Schedule Trigger from every minute to every 3-5 minutes if you have a smaller community
Requirements
- Discord OAuth2 credentials for bot authentication with message read, delete, and send permissions
- Google Sheets API connection for accessing the training data knowledge base
- OpenAI API key for GPT-5 Mini model access
- A Google Sheet formatted with message examples, deletion labels, and reasoning
- Discord Server ID, Channel IDs (moderated + admin) which you can get by enabling Developer Mode in Discord
Customising this workflow
- Try building an emoji-based feedback system where admins can react to notifications with ✅ (correct deletion) or ❌ (wrong deletion) to automatically update your training data
- Add a severity scoring system that issues warnings for minor violations before deleting messages
- Implement a user strike system that tracks repeat offenders and automatically applies temporary mutes or bans
- Expand the AI prompt to categorize violations (spam, harassment, profanity, etc.) and route different types to different admin channels
- Create a weekly digest that summarizes moderation statistics and trending violation types
- Add support for monitoring multiple channels by duplicating the Discord message fetch nodes with different channel IDs
- Integrate with a database instead of Google Sheets for faster lookups and more sophisticated training data management
If you have questions
Feel free to contact me here:
elijahmamuri@gmail.com elijahfxtrading@gmail.com
Moderate Your Discord Server Using AI and Google Sheets
This n8n workflow automates the moderation of your Discord server by leveraging AI (via OpenAI's ChatGPT) and Google Sheets to manage flagged content and user warnings. It helps maintain a healthy community by automatically detecting and acting on inappropriate messages.
What it does
This workflow simplifies Discord server moderation by:
- Periodically Checking for New Data: It is triggered on a schedule (e.g., every 5 minutes) to check for new entries in a Google Sheet.
- Retrieving Moderation Data: It reads specific columns (like
message,user,channel,action,reason) from a designated Google Sheet. - Processing Data in Batches: It processes the retrieved data in batches to efficiently handle multiple entries.
- Enriching with AI (Placeholder): It includes an AI Agent node, likely intended to process messages for moderation, classify content, or suggest actions. Note: The current JSON does not explicitly define the AI Agent's specific function or connection to a Language Model, but its presence suggests AI-driven analysis.
- Setting/Editing Fields: It includes a "Set" node, which is typically used to transform or add data fields, potentially preparing data for Discord or further AI processing.
- Sending Discord Messages: It interacts with Discord, likely to send warnings, notifications, or moderate messages based on the processed data.
- Introducing Delays: A "Wait" node is included, possibly to prevent rate limiting on Discord or other services, or to introduce a pause between actions.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running instance of n8n.
- Google Sheets Account: A Google account with access to Google Sheets.
- You will need to create a Google Sheet with columns for moderation data (e.g.,
message,user,channel,action,reason).
- You will need to create a Google Sheet with columns for moderation data (e.g.,
- Discord Account & Bot: A Discord account and a Discord bot with appropriate permissions to send messages and potentially moderate users in your server.
- OpenAI API Key (or compatible LLM): Access to an OpenAI API key or another Large Language Model (LLM) service if the "AI Agent" node is configured to use one. (The "OpenAI Chat Model" node suggests this is the intended LLM).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Google Sheets: Set up your Google Sheets credential to allow n8n to read from your designated spreadsheet.
- Discord: Configure your Discord credential with your bot token and any necessary permissions.
- OpenAI: If using the AI Agent, configure your OpenAI credential with your API key.
- Customize Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name where your moderation data is stored.
- Ensure the columns configured in the Google Sheets node match your actual sheet columns (e.g.,
message,user,channel,action,reason).
- Configure AI Agent (if applicable):
- If the AI Agent is intended to perform specific moderation tasks, you will need to configure its prompt, tools, and connection to the "OpenAI Chat Model" node as per your requirements.
- Customize Discord Node:
- Configure the Discord node to send messages to the correct channel or user, using data from previous nodes (e.g.,
user,reason,action).
- Configure the Discord node to send messages to the correct channel or user, using data from previous nodes (e.g.,
- Adjust Schedule Trigger:
- Set the "Schedule Trigger" node to your desired interval for checking the Google Sheet (e.g., every 5 minutes).
- Activate the Workflow: Once configured, activate the workflow to start automated moderation.
This workflow provides a robust foundation for AI-assisted Discord moderation, allowing you to streamline the process of identifying and addressing inappropriate content and behavior in your community.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.