Webhook and Discord integration

Who it's for This n8n workflow is designed for businesses, consultants, and service providers who want to automate their meeting scheduling process. The workflow creates a seamless booking system that can handle meeting requests, check availability, create calendar events, set up video conferences, and send notifications through multiple channels. Features Integrates with web forms to receive booking requests Checks Google Calendar availability automatically Creates calendar events with booking details Sets up Zoom meetings instantly Sends notifications via email, WhatsApp, Discord, and Teams Notifies politely if requested slots aren’t available Supports Your time zone conversions Requirements Google Calendar API Credentials**: For checking availability and creating events Zoom API Credentials**: For generating meeting links and video conferences Gmail OAuth2 Credentials**: For sending email confirmations Notification Service Credentials**: Discord Bot API, Microsoft Teams API, Rapiwa API (for WhatsApp) Important Notes Time Zone Configuration**: The workflow is set to Asia/Dhaka time zone but can be customized Meeting Settings**: Default meeting duration (40 minutes) and password can be adjusted Notification Templates**: All notification messages can be customized to match your brand voice Calendar Selection**: Ensure the correct Google Calendar ID is configured for your booking system Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

How it works This workflow automatically evaluates refund and chargeback risk for incoming e-commerce orders. Orders are received via a webhook, processed individually, and checked to avoid duplicate analysis. Each transaction is normalized and sent to OpenAI for structured risk scoring and classification. Results are logged for auditing, alerts are triggered for high-risk cases, and processed orders are marked to prevent reprocessing. Step-by-step Step 1 – Ingest incoming orders** Webhook – Receives single or bulk order payloads from external systems. Split Out – Breaks array-based payloads into individual order records. Split In Batches – Iterates through each order in a controlled loop. Step 2 – Deduplication check** IF (DEDUPE CHECK) – Verifies whether an order was already processed and skips duplicates. Step 3 – Normalize transaction data** Code (Normalize Data) – Validates required fields and standardizes order, customer, and behavioral attributes. Step 4 – AI risk assessment** OpenAI (Message a model) – Sends normalized transaction data to the AI model and requests a strict JSON risk evaluation. Step 5 – Parse AI output** Code (Parse AI Output) – Cleans the AI response and extracts risk score, risk level, key drivers, and recommendations. Step 6 – Log results** Google Sheets (Append) – Stores timestamps, order details, and AI risk outcomes for reporting and audits. Step 7 – Risk decision and alerts** IF (High Risk) – Filters only transactions classified as HIGH risk. Discord – Sends real-time alerts to operations or finance teams. Gmail – Emails finance stakeholders with full risk context. Step 8 – Mark order as processed** Google Sheets (Update) – Updates the source row to prevent duplicate processing. Why use this? Automatically detects high refund or chargeback risk before losses occur. Eliminates manual review with consistent, AI-driven risk scoring. Sends instant alerts so teams can act quickly on high-risk orders. Maintains a clear audit trail for compliance and reporting. Scales easily to handle single or bulk order evaluations.

Who Is This For? This workflow is designed for space enthusiasts, science educators, journalists, fact-checkers, and researchers who want to stay informed about near-Earth asteroid threats while filtering out media sensationalism. It's also valuable for anyone studying how different regions cover space-related news. What It Does This workflow creates an automated planetary defense monitoring system that: Scans NASA's Near Earth Object database for potentially hazardous asteroids over a 7-day window Searches news coverage across three regions (US, Japan, EU) to compare media reporting Uses AI (GPT-4o-mini) to fact-check news claims against official NASA data Detects misinformation and measures media sensationalism levels Generates visual charts comparing actual threat levels vs media panic Sends alerts through multiple channels (Slack, Discord, Email) Logs all alerts to Google Sheets for historical analysis How It Works Trigger: Runs daily at 9 AM or on-demand via webhook NASA Data Fetch: Retrieves 7-day asteroid forecast from NASA NeoWs API Threat Analysis: Identifies potentially hazardous asteroids and assigns alert levels (LOW/MEDIUM/HIGH) News Search: Searches news in US, Japan, and EU using Apify's Google Search Scraper AI Fact-Check: GPT-4o-mini compares news claims against NASA data, detecting misinformation Visualization: Generates gauge charts for threat level and media panic, plus regional comparison bar chart Multi-Channel Alerts: Sends formatted reports to Slack, Discord, Email, and logs to Google Sheets Set Up Steps Estimated time: 15-20 minutes NASA API (Required): Get your free API key at api.nasa.gov Apify (Required): Create account and connect via OAuth OpenAI (Required): Add your API key from platform.openai.com Notification Channels (Choose at least one): Slack: Create OAuth app and connect Discord: Create webhook URL Email: Configure SMTP settings Google Sheets (Optional): Create a sheet for logging with columns: Date, Alert Level, Hazardous Count, Threat Score, Media Panic Score, Misinformation Detected, Top Asteroid, Most Accurate Region Requirements NASA API key (free) Apify account (free tier available) OpenAI API key (paid) At least one notification channel configured n8n version 1.0+ How to Customize Change scan frequency**: Modify the Schedule Trigger node Add more regions**: Edit the "Configure Regional Search" code node Adjust alert thresholds**: Modify lunar distance threshold (currently 10) in "Analyze Asteroid Threats" Disable channels**: Simply remove connections to notification nodes you don't need Customize messages**: Edit the "Format Multi-Channel Messages" node

Automate Bug Reports: GitHub Issues → AI Analysis → Jira Tickets with Slack & Discord Alerts Automatically convert GitHub issues into analyzed Jira tickets with AI-powered severity detection, developer assignment, and instant team alerts. Overview This workflow captures GitHub issues in real-time, analyzes them with GPT-4o for severity and categorization, creates enriched Jira tickets, assigns the right developers, and notifies your team across Slack and Discord—all automatically. Features AI-Powered Triage**: GPT-4o analyzes bug severity, category, root cause, and generates reproduction steps Smart Assignment**: Automatically assigns developers based on mentioned files and issue context Two-Way Sync**: Posts Jira ticket links back to GitHub issues Multi-Channel Alerts**: Rich notifications in Slack and Discord with action buttons Time Savings**: Eliminates 15-30 minutes of manual triage per bug Customizable Routing**: Easy developer mapping and priority rules What Gets Created Jira Ticket: Original GitHub issue details with reporter info AI severity assessment and categorization Reproduction steps and root cause analysis Estimated completion time Automatic labeling and priority assignment GitHub Comment: Jira ticket link AI analysis summary Assigned developer and estimated time Team Notifications: Severity badges and quick-access buttons Developer assignment and root cause summary Color-coded priority indicators Use Cases Development teams managing 10+ bugs per week Open source projects handling community reports DevOps teams tracking infrastructure issues QA teams coordinating with developers Product teams monitoring user-reported bugs Setup Requirements Required: GitHub repository with admin access Jira Software workspace OpenAI API key (GPT-4o access) Slack workspace OR Discord server Customization Needed: Update developer email mappings in "Parse GPT Response & Map Data" node Replace YOUR_JIRA_PROJECT_KEY with your project key Update Slack channel name (default: dev-alerts) Replace YOUR_DISCORD_WEBHOOK_URL with your webhook Change your-company.atlassian.net to your Jira URL Setup Time: 15-20 minutes Configuration Steps Import workflow JSON into n8n Add credentials: GitHub OAuth2, Jira API, OpenAI API, Slack, Discord Configure GitHub webhook in repository settings Customize developer mappings and project settings Test with sample GitHub issue Activate workflow Expected Results 90% faster bug triage (20 min → 2 min per issue) 100% consistency in bug analysis Zero missed notifications Better developer allocation Improved bug documentation Tags GitHub, Jira, AI, GPT-4, Bug Tracking, DevOps, Automation, Slack, Discord, Issue Management, Development, Project Management, OpenAI, Webhook, Team Collaboration

This n8n workflow automates WooCommerce order processing by capturing order updates via webhook and converting them into Discord notifications and Google Sheets entries. What This Workflow Does Automatically captures WooCommerce orders and sends real-time Discord notifications while logging paid orders to Google Sheets for tracking and reporting. Key Benefits Save 90% Time**: Eliminates manual order logging and monitoring Never Miss Orders**: Instant Discord alerts for all order activities 80% Faster Response**: Team gets structured order info immediately Dual Tracking**: Real-time alerts + permanent spreadsheet records Perfect For Ecommerce Teams**: Monitor orders without constantly checking admin panel Small Business Owners**: Professional order tracking without extra staff Fulfillment Teams**: Get organized order data for quick processing How It Works WooCommerce sends order webhook to n8n Order data is parsed and formatted beautifully All orders trigger Discord notifications (color-coded by status) Paid orders (PROCESSING status) are logged to Google Sheets Webhook confirms successful receipt to WooCommerce Features Smart Status Colors**: Yellow (pending), Blue (processing), Green (completed), Gray (cancelled) Rich Discord Embeds**: Customer info, items, shipping, totals - all formatted nicely Flexible Data Parsing**: Handles various WooCommerce webhook structures Indonesian Currency**: Proper IDR formatting for local businesses Product Thumbnails**: Shows product images in Discord notifications Setup Requirements n8n instance (self-hosted or cloud) Discord server with bot access Google account for Sheets WooCommerce admin access Quick Setup Import workflow JSON to n8n Add Discord bot token Connect Google Sheets OAuth Set WooCommerce webhook to n8n endpoint Create Google Sheet with required columns Test with a sample order Customization Options Change Discord embed colors for your brand Modify which order statuses get logged Add custom fields to Google Sheets Adjust currency and language settings Filter orders by specific conditions Google Sheets Columns Month (order date) Brand Name Web Order Number Expedition (shipping method) Tracking Number Status Future Enhancement Ideas Add SMS/WhatsApp customer notifications Connect to shipping label services Integrate with CRM for customer insights Add inventory management triggers Create sales analytics dashboard Support Created by Khmuhtadin Need customization? Contact us!

About this Workflow This workflow helps you repurpose your YouTube videos across multiple social media platforms with zero manual effort. It’s designed for creators, businesses, and marketers who want to maximize reach without spending hours re-uploading content everywhere. How It Works Trigger from YouTube The workflow checks your YouTube channel every 10 minutes via RSS feed. It compares the latest video ID with the last saved one to detect if a new video was uploaded. Tutorial: How to get YouTube Channel RSS Feed Generate Descriptions with AI Uses Gemini 2.5 Flash to automatically generate fresh, engaging descriptions for your posts. Create Images with ContentDrips ContentDrips offers multiple templates (carousel, single image, branding templates, etc.). The workflow generates a custom promotional image using your video description and thumbnail. Install node: npm install n8n-nodes-contentdrips Docs: ContentDrips Blog Tutorial Publish Across Social Platforms with SocialBu Instead of manually connecting each social media API, this workflow uses SocialBu. From a single connection, you can post to: Facebook, Instagram, TikTok, YouTube, Twitter (X), LinkedIn, Threads, Pinterest, and more. Website: SocialBu Get Real-Time Notifications via Discord After each run, the workflow sends updates to your Discord channel. You’ll know if the upload was successful, or if an error occurred (e.g., API limits). Setup guide: Discord OAuth Credentials Why Use This Workflow? Saves time by automating the entire repurposing process. Ensures consistent branding and visuals across platforms. Works around platform restrictions by leveraging SocialBu’s integrations. Keeps you updated with Discord notifications—no guessing if something failed. Requirements YouTube channel RSS feed link ContentDrips API key, template ID, and branding setup SocialBu account with connected social media platforms Discord credentials (for webhook updates) Need Help? Message me on LinkedIn: Shayan Ali Bakhsh Happy Automation 🚀

Description: This n8n workflow automates a Discord bot to fetch messages from a specified channel and send AI-generated responses in threads. It ensures smooth message processing and interaction, making it ideal for managing community discussions, customer support, or AI-based engagement. This workflow leverages Redis for memory persistence, ensuring that conversation history is maintained even if the workflow restarts, providing a seamless user experience. How It Works The bot listens for new messages in a specified Discord channel. It sends the messages to an AI model for response generation. The AI-generated reply is posted as a thread under the original message. The bot runs on an Ubuntu server and is managed using PM2 for uptime stability. The Discord bot (Python script) acts as the bridge, capturing messages from Discord and sending them to the n8n webhook. The n8n workflow then processes these messages, interacts with the AI model, and sends the AI's response back to Discord via the bot. Prerequisites to host Bot Sign up on Pella, which is a managed hosting service for Discord Bots. (Easy Setup) A Redis instance for memory persistence. Redis is an in-memory data structure store, used here to store and retrieve conversation history, ensuring that the AI can maintain context across multiple interactions. This is crucial for coherent and continuous conversations. Set Up Steps 1️⃣ Create a Discord Bot Go to the Discord Developer Portal. Click “New Application”, enter a name, and create it. Navigate to Bot > Reset Token, then copy the Bot Token. Enable Privileged Gateway Intents (Presence, Server Members, Message Content). Under OAuth2 > URL Generator, select bot scope and required permissions. Copy the generated URL, open it in a browser, select your server, and click Authorize. 2️⃣ Deploy the Bot on Pella Create a new folder discord-bot and navigate into it: Create and configure an .env file to store your bot token: Copy the code to .env: (You can copy the webhook URL from the n8n workflow) TOKEN=your-bot-token-here WEBHOOK_URL=https://your-domain.tld/webhook/getmessage Create file main.py copy the below code and save it: Copy this Bot script to main.py: import discord import requests import json import os from dotenv import load_dotenv Load environment variables from .env file load_dotenv() TOKEN = os.getenv("TOKEN") WEBHOOK_URL = os.getenv("WEBHOOK_URL") Bot Configuration LISTEN_CHANNELS = ["YOUR_CHANNEL_ID_1", "YOUR_CHANNEL_ID_2"] # Replace with your target channel IDs Intents setup intents = discord.Intents.default() intents.messages = True # Enable message event intents.guilds = True intents.message_content = True # Required to read messages client = discord.Client(intents=intents) @client.event async def on_ready(): print(f'Logged in as {client.user}') @client.event async def on_message(message): if message.author == client.user: return # Ignore bot's own messages if str(message.channel.id) in LISTEN_CHANNELS: try: fetched_message = await message.channel.fetch_message(message.id) # Ensure correct fetching payload = { "channel_id": str(fetched_message.channel.id), # Ensure it's string "chat_message": fetched_message.content, "timestamp": str(fetched_message.created_at), # Ensure proper formatting "message_id": str(fetched_message.id), # Ensure ID is a string "user_id": str(fetched_message.author.id) # Ensure user ID is also string } headers = {'Content-Type': 'application/json'} response = requests.post(WEBHOOK_URL, data=json.dumps(payload), headers=headers) if response.status_code == 200: print(f"Message sent successfully: {payload}") else: print(f"Failed to send message: {response.status_code}, Response: {response.text}") except Exception as e: print(f"Error fetching message: {e}") client.run(TOKEN) Create requirements.txt and copy: discord python-dotenv 3️⃣ Follow the video to set up the bot which will run 24/7 Tutorial - https://www.youtube.com/watch?v=rNnK3XlUtYU Note: Free Plan will expire after 24 hours, so please opt for the Paid Plan in Pella to keep your bot running. 4️⃣ n8n Workflow Configuration The n8n workflow consists of the following nodes: Get Discord Messages (Webhook):** This node acts as the entry point for messages from the Discord bot. It receives the channel_id, chat_message, timestamp, message_id, and user_id from Discord when a new message is posted in the configured channel. Its webhook path is /getmessage and it expects a POST request. Chat Agent (Langchain Agent):** This node processes the incoming Discord message (chat_message). It is configured as a conversational agent, integrating the language model and memory to generate an appropriate response. It also has a prompt to keep the reply concise, under 1800 characters. OpenAI -4o-mini (Langchain Language Model):** This node connects to the OpenAI API and uses the gpt-4o-mini-2024-07-18 model for generating AI responses. It is the core AI component of the workflow. Message History (Redis Chat Memory):** This node manages the conversation history using Redis. It stores and retrieves chat messages, ensuring the Chat Agent maintains context for each user based on their user_id. This is critical for coherent multi-turn conversations. Calculator (Langchain Tool):** This node provides a calculator tool that the AI agent can utilize if a mathematical calculation is required within the conversation. This expands the capabilities of the AI beyond just text generation. Response fromAI (Discord):** This node sends the AI-generated response back to the Discord channel. It uses the Discord Bot API credentials and replies in a thread under the original message (message_id) in the specified channel_id. Sticky Note1, Sticky Note2, Sticky Note3, Sticky Note4, Sticky Note5, Sticky Note:** These are informational nodes within the workflow providing instructions, code snippets for the Discord bot, and setup guidance for the user. These notes guide the user on setting up the .env file, requirements.txt, the Python bot code, and general recommendations for channel configuration and adding tools. 5️⃣ Setting up Redis Choose a Redis Hosting Provider: You can use a cloud provider like Redis Labs, Aiven, or set up your own Redis instance on a VPS. Obtain Redis Connection Details: Once your Redis instance is set up, you will need the host, port, and password (if applicable). Configure n8n Redis Nodes: In your n8n workflow, configure the "Message History" node with your Redis connection details. Ensure the Redis credential ✅ redis-for-n8n is properly set up with your Redis instance details (host, port, password). 6️⃣ Customizing the Template AI Model:** You can easily swap out the "OpenAI -4o-mini" node with any other AI service supported by n8n (e.g., Cohere, Hugging Face) to use a different language model. Ensure the new language model node is connected to the ai_languageModel input of the "Chat Agent" node. Agent Prompt:** Modify the text parameter in the "Chat Agent" node to change the AI's persona, provide specific instructions, or adjust the response length. Additional Tools:** The "Calculator" node is an example of an AI tool. You can add more Langchain tool nodes (e.g., search, data lookup) and connect them to the ai_tool input of the "Chat Agent" node to extend the AI's capabilities. Refer to the "Sticky Note5" in the workflow for a reminder. Channel Filtering:** Adjust the LISTEN_CHANNELS list in the main.py file of your Discord bot to include or exclude specific Discord channel IDs where the bot should listen for messages. Thread Management:** The "Response fromAI" node can be modified to change how threads are created or managed, or to send responses directly to the channel instead of a thread. The current setup links the response to the original message ID (message_reference). 7️⃣ Testing Instructions Start the Discord Bot: Ensure your main.py script is running on Pella. Activate the n8n Workflow: Make sure your n8n workflow is active and listening for webhooks. Send a Message in Discord: Go to one of the LISTEN_CHANNELS in your Discord server and send a message. Verify Response: The bot should capture the message, send it to n8n, receive an AI-generated response, and post it as a thread under your original message. Check Redis: Verify that the conversation history is being stored and updated correctly in your Redis instance. Look for keys related to user IDs. ✅ Now your bot is running in the background! 🚀

Use Case This workflow retrieves all members of a Discord server or guild who have a specific role. Due to limitations in the Discord API, it only returns a limited number of users per call. To overcome this, the workflow uses Google Sheets to track which user we received last to return all Members (of a certain role) from a Discord server in batches of 100 members. Setup Add your Google Sheets and Discord credentials. Create a Google Sheets document that contains ID as a column. We're using this to remember which member we received last. Edit the fields in the setup node Setup: Edit this to get started. You can read up on how to get the Discord IDs via this link. Link to your Discord server in the Discord nodes Activate the workflow Call the production webhook URL in your browser Requirements Admin rights in the Discord server and access to the developer portal of discord Google Sheets Minimum n8n version 1.28.0 Potential Use cases Writing a direct message to all members of a certain role Analysing user growth on Discord regularly Analysing role distributions on Discord regularly Saving new members in a Discord ... Keywords Discord API, Getting all members from Discord via API, Google Sheets and Discord automation, How to get all Discord members via API

This workflow is a template example for making Discord GPT-powered bots. Incoming user requests are analysed and categorised via OpenAI node with the help of a hand-crafted prompt. The response message is then routed to a different Discord channel.