Back to Integrations
integrationWebhook node
integrationSlack node

Webhook and Slack integration

Save yourself the work of writing custom integrations for Webhook and Slack and use n8n instead. Build adaptable and scalable Development, Core Nodes, Communication, and HITL workflows that work with your technology stack. All within a building experience you will love.

How to connect Webhook and Slack

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Webhook and Slack integration: Create a new workflow and add the first step

Step 2: Add and configure Webhook and Slack nodes

You can find Webhook and Slack in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure Webhook and Slack nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Webhook and Slack integration: Add and configure Webhook and Slack nodes

Step 3: Connect Webhook and Slack

A connection establishes a link between Webhook and Slack (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

Webhook and Slack integration: Connect Webhook and Slack

Step 4: Customize and extend your Webhook and Slack integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Webhook and Slack with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Webhook and Slack integration: Customize and extend your Webhook and Slack integration

Step 5: Test and activate your Webhook and Slack workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Webhook to Slack or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

Webhook and Slack integration: Test and activate your Webhook and Slack workflow

IT ops AI SlackBot workflow - chat with your knowledge base

Video Demo:

Click here to see a video of this workflow in action.

Summary Description:

The "IT Department Q&A Workflow" is designed to streamline and automate the process of handling IT-related inquiries from employees through Slack. When an employee sends a direct message (DM) to the IT department's Slack channel, the workflow is triggered. The initial step involves the "Receive DMs" node, which listens for new messages. Upon receiving a message, the workflow verifies the webhook by responding to Slack's challenge request, ensuring that the communication channel is active and secure.

Once the webhook is verified, the workflow checks if the message sender is a bot using the "Check if Bot" node. If the sender is identified as a bot, the workflow terminates the process to avoid unnecessary actions. If the sender is a human, the workflow sends an acknowledgment message back to the user, confirming that their query is being processed. This is achieved through the "Send Initial Message" node, which posts a simple message like "On it!" to the user's Slack channel.

The core functionality of the workflow is powered by the "AI Agent" node, which utilizes the OpenAI GPT-4 model to interpret and respond to the user's query. This AI-driven node processes the text of the received message, generating an appropriate response based on the context and information available. To maintain conversation context, the "Window Buffer Memory" node stores the last five messages from each user, ensuring that the AI agent can provide coherent and contextually relevant answers.

Additionally, the workflow includes a custom Knowledge Base (KB) tool (see that tool template here) that integrates with the AI agent, allowing it to search the company's internal KB for relevant information. After generating the response, the workflow cleans up the initial acknowledgment message using the "Delete Initial Message" node to keep the conversation thread clean. Finally, the generated response is sent back to the user via the "Send Message" node, providing them with the information or assistance they requested. This workflow effectively automates the IT support process, reducing response times and improving efficiency.

To quickly deploy the Knowledge Ninja app in Slack, use the app manifest below and don't forget to replace the two sample urls:

{
"display_information": {
"name": "Knowledge Ninja",
"description": "IT Department Q&A Workflow",
"background_color": "#005e5e"
},
"features": {
"bot_user": {
"display_name": "IT Ops AI SlackBot Workflow",
"always_online": true
}
},
"oauth_config": {
"redirect_urls": [
"Replace everything inside the double quotes with your slack redirect oauth url, for example: https://n8n.domain.com/rest/oauth2-credential/callback"
],
"scopes": {
"user": [
"search:read"
],
"bot": [
"chat:write",
"chat:write.customize",
"groups:history",
"groups:read",
"groups:write",
"groups:write.invites",
"groups:write.topic",
"im:history",
"im:read",
"im:write",
"mpim:history",
"mpim:read",
"mpim:write",
"mpim:write.topic",
"usergroups:read",
"usergroups:write",
"users:write",
"channels:history"
]
}
},
"settings": {
"event_subscriptions": {
"request_url": "Replace everything inside the double quotes with your workflow webhook url, for example: https://n8n.domain.com/webhook/99db3e73-57d8-4107-ab02-5b7e713894ad",
"bot_events": [
"message.im"
]
},
"org_deploy_enabled": false,
"socket_mode_enabled": false,
"token_rotation_enabled": false
}
}

Nodes used in this workflow

Popular Webhook and Slack workflows

+2

Automate client onboarding with Asana, Google Docs, Gmail, Slack and Sheets

📊 Description Automate short-term trading research by generating high-quality trade ideas using MCP (Market Context Protocol) signals and AI-powered analysis. 📈🤖 This workflow evaluates market context, catalysts, momentum, and risk factors to produce structured trade ideas with clear reasoning, confidence scores, and execution notes. Designed for fast-moving markets, it helps traders and analysts spot actionable opportunities consistently—without manual screening or emotional bias. Perfect for systematic traders, research teams, and AI-driven trading desks. ⚡📊 🔁 What This Template Does 1️⃣ Ingests market context and asset data from MCP inputs. 📥 2️⃣ Normalizes symbols, sectors, and time horizons for analysis. 🧾 3️⃣ Evaluates short-term momentum and catalyst strength. 🚀 4️⃣ Analyzes risk, volatility, and downside exposure. ⚠️ 5️⃣ Uses AI to generate a structured trade thesis. 🤖 6️⃣ Assigns a confidence score and risk level to each idea. 📊 7️⃣ Produces clear entry logic, rationale, and trade direction. 🧠 8️⃣ Filters out low-quality or low-conviction setups. 🚫 9️⃣ Outputs clean JSON-ready trade ideas for downstream systems. 🔁 ⭐ Key Benefits ✅ Automates short-term trade idea generation ✅ Reduces emotional bias with AI-based scoring ✅ Combines market context, catalysts, and momentum ✅ Produces structured, repeatable trade logic ✅ Saves hours of manual chart and news analysis ✅ Ideal for fast-paced trading environments 🧩 Features MCP (Market Context Protocol) data ingestion AI-powered trade thesis generation Confidence and risk scoring logic Short-term momentum and catalyst analysis Strict structured output for automation reliability Easy integration into dashboards or execution systems 🔐 Requirements MCP-compatible market data source OpenAI API credentials (GPT-4o or GPT-4o-mini recommended) n8n instance with AI nodes enabled Defined schema for trade idea output 🎯 Target Audience Short-term and swing traders Quant and discretionary trading teams Market research analysts Fintech platforms generating trade signals Automation engineers building trading workflows
+4

Generate continuous PRD updates in Google Docs from Slack, Zoom, Jira, Zendesk, Figma and analytics using OpenAI

This workflow creates an automated Product Intelligence Engine that continuously collects signals from multiple product sources and generates structured PRD updates using AI. It ingests conversations, feedback, support tickets, analytics, and design comments, standardizes them, analyzes them with an AI PRD Agent, and automatically updates a Google Doc with structured PRD recommendations. Instead of manually reviewing Slack threads, Zoom calls, Jira comments, support tickets, and customer forms, this workflow centralizes everything into one intelligent PRD analysis system. High-Level Architecture - The workflow runs in 4 layers: Signal Ingestion Layer Captures product signals from: • Slack (channel messages + app mentions) • Customer Form submissions • Zoom recordings (scheduled) • Jira comments (scheduled) • Zendesk tickets (scheduled) • Figma comments (file updates) • Platform analytics via webhook • (Extendable to Salesforce / HubSpot) Standardization Layer Each source passes through a Format Node that: • Extracts relevant text • Normalizes metadata • Adds timestamps • Labels source type All inputs are converted into a unified "product signal" object. Intelligence Layer (AI PRD Agent) All signals are merged into a single stream using a Merge node. The PRD Analysis Agent then: • Extracts feature requests • Detects scope changes • Identifies risks and constraints • Evaluates priority signals • Detects target user shifts • Generates structured PRD updates PRD Governance Layer - output in a Google Doc The structured AI output is appended to a Google Doc, which is fully traceable. This creates a living PRD that continuously evolves based on real product signals. Required Credentials (And How To Add Them): You will need to configure the following credentials in n8n: Slack Used for Slack Trigger. Steps: Create a Slack App at api.slack.com Enable: app_mentions:read channels:history chat:write (optional if you want replies) Install app to workspace Copy Bot OAuth Token In n8n → Create Slack API credential Paste token Reference - https://www.youtube.com/watch?v=qk5JH6ImK0I Zoom (OAuth2) Used to fetch recordings. Steps: Create an OAuth App in Zoom Marketplace Add the Redirect URL from n8n Copy Client ID + Secret Add Zoom OAuth2 credential in n8n Connect account Reference - https://www.youtube.com/watch?v=BC6O_3LYgac Google Docs (OAuth2) Used to update PRD document. Steps: Create Google Cloud Project Add Doc URl to n8n Replace the example Google Doc URL with your own PRD document. Reference - https://www.youtube.com/watch?v=iieEHvu93dc Jira (Cloud) Steps: Generate API token from Atlassian Create Jira Software Cloud credential Enter: Email API token Domain Reference - https://www.youtube.com/watch?v=T4z7lzqSZDY Zendesk Steps: Generate API token Add Zendesk credential Enter: Subdomain Email API token Figma Steps: Generate a personal access token in Figma Add Figma credentials with the team ID Paste token Platform Analytics Webhook Replace: <PLACEHOLDER_VALUE__your_analytics_api_endpoint> With your real analytics endpoint. You can: • Send Mixpanel exports • Send Amplitude exports • Or POST custom JSON What Makes This Powerful • Eliminates product signal silos • Creates AI-driven PRD governance • Ensures traceability of decisions • Enables continuous PRD evolution • Scales across teams
+3

Send AI pre-op reminders with Google Calendar, Gmail, Sheets, Slack and GPT-4o

📘 Description This workflow automates end-to-end pre-surgery checklist reminders and confirmation tracking for healthcare operations teams. It ensures patients receive timely preparation instructions, can confirm completion with a single click, and allows staff to monitor confirmation status in real time—without manual coordination. Every day at 9:00 AM, the workflow fetches surgery events from Google Calendar, extracts patient details from event descriptions, and generates a unique confirmation link for each patient. An AI assistant then creates a personalized, patient-friendly pre-op checklist email (subject + styled HTML body) that includes surgery details and a confirmation button. When a patient clicks the confirmation link, a webhook captures the confirmation, updates Google Sheets as the source of truth, and records the timestamp. A separate periodic scheduler scans the sheet for patients who have not confirmed within the expected window. If confirmation is missing, the assigned nurse or owner is alerted in Slack with full patient and surgery context for immediate follow-up. This creates a closed-loop system: reminder → confirmation capture → tracking → escalation. ⚙️ What This Workflow Does (Step-by-Step) ▶️ Daily 9:00 AM Trigger Starts the pre-op reminder cycle automatically each morning. 📅 Fetch Today’s Surgery Events (Google Calendar) Pulls calendar events and filters only surgery-related entries. 🧾 Extract Patient Details from Event Description Parses patient name, email, phone, ID, procedure, and surgery time. 🔗 Generate Unique Confirmation Link Creates a secure confirmUrl per patient with tracking parameters. ✉️ AI Email Generation (Subject + HTML Body) Uses Azure OpenAI (gpt-4o) to generate a calm, professional checklist email with: Surgery details Basic preparation checklist Green confirmation button linked to confirmUrl 📤 Send Pre-Op Reminder via Gmail Delivers the styled HTML email directly to the patient. ✅ Confirmation Webhook (GET /confirm) Captures patient clicks, parses query parameters, and marks the checklist as confirmed. 🧾 Upsert Confirmation Status (Google Sheets) Stores and updates patient confirmation records as the operational source of truth. ⏳ Periodic Confirmation Check Runs on a schedule to scan all patient rows for missing confirmations. 🚨 Slack Alert for Missing Confirmations Notifies the nurse or owner with full patient context when confirmation is not received in time. 🧩 Prerequisites • Google Calendar OAuth2 • Gmail OAuth2 • Azure OpenAI (gpt-4o) credentials • Google Sheets OAuth2 • Slack API credentials • Publicly accessible webhook URL for confirmation tracking 💡 Key Benefits ✔ Automated pre-op reminders at a fixed daily time ✔ Personalized AI-generated patient emails ✔ One-click confirmation tracking ✔ Google Sheets audit trail for operations ✔ Proactive Slack alerts for missing confirmations ✔ Reduced manual follow-ups and missed preparations 👥 Perfect For Hospitals and surgical centers Clinic operations teams Care coordinators Day-surgery facilities Healthcare admin automation systems
+4

Create script-to-video avatar videos with GPT-4.1-mini, HeyGen, Google Drive, Gmail and Slack

📘 Description This workflow automates the entire process of taking a raw user-submitted script, rewriting it into a polished HeyGen-ready narration, generating a full avatar video, handling all processing checks, retrieving the final MP4, uploading it to Google Drive, and notifying the user through email and Slack. It turns an unstructured script into a complete, ready-to-share video package without any manual intervention. The system rewrites scripts into structured sections (intro → narration sections → closing), ensures the final narration fits HeyGen’s free-tier limits, submits the script to HeyGen’s video API, initiates a polling loop until the video is fully rendered, downloads the finished file, uploads it to Drive with metadata, and generates clean notification messages containing the file links. Errors at any point trigger automated Slack alerts for debugging. This workflow replaces manual rewriting, video rendering, download/upload, and team communication—providing a fully-managed script-to-video pipeline. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Receive Script Request via Webhook Captures the raw script payload submitted by the user. 🧹 Parse Incoming Script Payload Converts stringified JSON body into structured data for processing. ✍️ Rewrite & Structure Video Script Using AI Transforms the raw script into: • Video title • Intro • Multiple sections (title + narration) • Closing • Combined full_script optimized for HeyGen’s ~300–350 word limit Ensures natural, human narration with smooth transitions. 🧠 Script Writing Memory + LLM Engine Maintains writing consistency and uses GPT-4.1-mini to generate polished narration. 🧪 Validate Structured Script Output Enforces strict JSON schema for titles, sections, closing, and full_script. 🎞️ Submit Video Generation Request to HeyGen Sends structured script to HeyGen API with avatar, voice, and background settings for 1280×720 export. ⏳ Wait Before Polling Loop Initial delay before the first status check. 📡 Check HeyGen Video Status Queries the HeyGen API to check progress of the video generation. ⏳ Wait Before Rechecking Adds timed spacing between repeated polls. 🔍 Evaluate Video Completion If status = completed → proceed If still processing → loop back to polling sequence 📥 Download Generated HeyGen Video Retrieves the completed MP4 using the returned video_url. ☁️ Upload Video to Google Drive Uploads the MP4 to a specific Google Drive folder, returning: • File name • View link • Download link • Timestamp • Size metadata 📣 Generate Completion Notifications Using AI Creates two outputs: • A friendly short email summary • A concise Slack message Both containing the Google Drive file link. 🧠 Notification Memory + LLM Engine Maintains tone and ensures consistent messaging across channels. 🧪 Validate Notification Output JSON Ensures email_subject, email_body, and slack_message follow schema. 💬 Send Video Ready Slack Notification Posts the final Slack message containing file details and Drive link. 📧 Send Video Ready Email Notification Emails the summary and file link to the designated recipient. 🚨 Error Handler Trigger → Slack Alert Any workflow failure sends a detailed diagnostic alert with node name, message, and timestamp. 🧩 Prerequisites • HeyGen API key • Google Drive OAuth connection • Slack API credentials • Gmail OAuth connection • Valid webhook endpoint to receive scripts 💡 Key Benefits ✔ Converts raw script → structured HeyGen-ready narration automatically ✔ Produces full HD avatar video with zero manual steps ✔ Polls HeyGen until the video is fully rendered ✔ Securely uploads final MP4 to Google Drive ✔ Auto-generates polished email + Slack notifications ✔ Ensures narrative consistency using memory context ✔ Provides real-time error alerts via Slack 👥 Perfect For HR teams automating onboarding videos Marketing teams producing quick avatar explainers Training content creators Founders creating rapid how-to or announcement videos Anyone needing instant script-to-video automation

Automated URL Phishing & Threat Analysis with NixGuard AI

Stop manually checking suspicious links. This free n8n workflow provides the foundation for a powerful, automated URL analysis pipeline. Using the NixGuard AI engine, you can instantly analyze suspicious URLs from emails, logs, or tickets to uncover phishing attempts, malware hosting sites, and malicious redirects. What You Will Automate: 🤖 Instant Threat Triage: Get an immediate AI-powered summary of why a URL is malicious, saving you critical investigation time. 🎯 Actionable IOC Extraction: Automatically extract the final redirected URL, malicious domains, and IPs to fuel your threat hunting and blocking rules. 🚀 SOAR-Ready Foundation: This workflow is the perfect starting point for your security playbooks. Use the output to: Alert: Send instant notifications to Slack or Teams. Respond: Create tickets in Jira or TheHive. Block: Add malicious domains to your firewall or DNS filter. Download this free template and automate your first line of defense against web-based threats in minutes! Don't have the main workflow yet? Get it HERE! 🔗 Learn more about NixGuard: thenex.world 🔗 Get started with a free security subscription: thenex.world/security/subscribe For search: URL Scanning, Phishing, Threat Intelligence, SOAR, SOC Automation, NixGuard, Free, AI, Incident Response, Cybersecurity, Automation, Link Analysis, MTTR, Malware, VirusTotal

Summarize Calls & Notify Teams via HubSpot, Slack, Email, WhatsApp

This workflow automates the process of handling conversation transcriptions and distributing key information across your organization. Here's what it does: Trigger: The workflow is initiated via a webhook that receives a transcription (e.g., from a call or meeting). Summarization & Extraction: Using AI, the transcription is summarized, and key information is extracted — such as action items, departments involved, and client details. Department Notifications: The relevant summarized information is automatically routed to specific departments via email based on content classification. CRM Sync: The summarized version is saved to the associated contact or deal in HubSpot for future reference and visibility. *Multi-Channel Alerts: *The summary is also sent via WhatsApp and Slack to keep internal teams instantly informed, regardless of platform. Use Case: Ideal for sales, customer service, or operations teams who manage client conversations and want to ensure seamless cross-departmental communication, documentation, and follow-up. Apps Used: Webhook (Trigger) OpenAI (or other AI/NLP for summarization) HubSpot Email Slack WhatsApp (via Twilio or third-party provider)

Build your own Webhook and Slack integration

Create custom Webhook and Slack workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Slack supported actions

Archive
Archives a conversation
Close
Closes a direct message or multi-person direct message
Create
Initiates a public or private channel-based conversation
Get
Get information about a channel
Get Many
Get many channels in a Slack team
History
Get a conversation's history of messages and events
Invite
Invite a user to a channel
Join
Joins an existing conversation
Kick
Removes a user from a channel
Leave
Leaves a conversation
Member
List members of a conversation
Open
Opens or resumes a direct message or multi-person direct message
Rename
Renames a conversation
Replies
Get a thread of messages posted to a channel
Set Purpose
Sets the purpose for a conversation
Set Topic
Sets the topic for a conversation
Unarchive
Unarchives a conversation
Get
Get Many
Get & filters team files
Upload
Create or upload an existing file
Delete
Get Permalink
Search
Send
Send and Wait for Response
Update
Add
Adds a reaction to a message
Get
Get the reactions of a message
Remove
Remove a reaction of a message
Add
Add a star to an item
Delete
Delete a star from an item
Get Many
Get many stars of autenticated user
Get
Get information about a user
Get Many
Get a list of many users
Get User's Profile
Get a user's profile
Get User's Status
Get online status of a user
Update User's Profile
Update a user's profile
Add Users
Create
Disable
Enable
Get Many
Get Users
Update

Webhook and Slack integration details

integrationWebhook node
Webhook

Webhooks are automatic notifications that apps send when something occurs. They are sent to a certain URL, which is effectively the app's phone number or address, and contain a message or payload. Polling is nearly never quicker than webhooks, and it takes less effort from you.

Use case

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQs

  • Can Webhook connect with Slack?

  • Can I use Webhook’s API with n8n?

  • Can I use Slack’s API with n8n?

  • Is n8n secure for integrating Webhook and Slack?

  • How to get started with Webhook and Slack integration in n8n.io?

Need help setting up your Webhook and Slack integration?

Discover our latest community's recommendations and join the discussions about Webhook and Slack integration.
Benjamin Hatton
Albert Ashkhatoyan
Víctor González
Salomão
sg tech

Looking to integrate Webhook and Slack in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate Webhook with Slack

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon