Back to Catalog

Interactive Slack approval & data submission system with webhooks

Niranjan GNiranjan G
1471 views
2/3/2026
Official Page

Slack Bot n8n Integration Hub - Workflow Submission

πŸš€ Showcase: Endless Possibilities with n8n Integration

This repository demonstrates a powerful Slack Bot Socket App that seamlessly integrates with n8n for automation workflows. This is just a showcase of what's possible when combining Slack's interactive capabilities with n8n's automation power - the possibilities are truly endless!

πŸ“‹ Project Overview

Repository: slack-n8n-integration-hub

Status: βœ… Committed and Ready for Submission

This project showcases how to create seamless interactions between Slack users and n8n workflows, demonstrating:

  • Real-time Data Submission from Slack to n8n workflows
  • Interactive Approval/Rejection workflows triggered from Slack
  • Secure Webhook Communication with optional Basic Authentication
  • Dynamic Modal Interactions with immediate feedback
  • Error Handling and User Experience optimization

🎯 Key Features Demonstrated

1. Data Input Integration

  • Users can submit custom data directly from Slack
  • Data is instantly sent to n8n workflows for processing
  • Real-time feedback and confirmation messages

2. Approval Workflow Automation

  • Interactive approve/reject buttons in Slack modals
  • Decisions trigger different n8n workflow paths
  • Automated decision logging and processing

3. Enhanced User Experience

  • Modal closes automatically after actions
  • Submit button positioned below input for better UX
  • Comprehensive error handling and user feedback

4. Security & Authentication

  • Optional HTTP Basic Auth for webhook security
  • Environment-based configuration management
  • Secure credential handling

πŸ”§ Technical Implementation

Slack Bot Features:

  • Socket Mode for real-time communication
  • Custom slash commands (/automation)
  • Interactive modals with dynamic content
  • Button actions and form submissions

n8n Integration:

  • Webhook triggers for data reception
  • Structured payload formats
  • Authentication support
  • Error handling and response management

Workflow Payload Examples:

Data Submission:

{
  "type": "data_submission",
  "data": "User input data here",
  "user": {
    "id": "U1234567890",
    "name": "username"
  },
  "timestamp": "2024-01-01T12:00:00.000Z",
  "source": "slack_bot"
}

Approval Action:

{
  "type": "approval_action",
  "action": "approve",
  "user": {
    "id": "U1234567890",
    "name": "username"
  },
  "timestamp": "2024-01-01T12:00:00.000Z",
  "source": "slack_bot"
}

🌟 Why This Matters for n8n Community

This project demonstrates how n8n can be the backbone for:

  • Human-in-the-loop automation workflows
  • Interactive approval processes
  • Real-time data collection from team communication tools
  • Seamless integration between chat platforms and automation
  • Scalable workflow triggers from multiple sources

πŸš€ Endless Possibilities

This is just the beginning! With this foundation, you can build:

  • IT Service Desk automation with Slack approvals
  • Content Publishing workflows with team reviews
  • Data Collection and processing pipelines
  • Incident Management with automated escalations
  • Project Management with status updates and approvals
  • Customer Support ticket routing and responses
  • DevOps Deployments with approval gates
  • Financial Approvals with audit trails
  • HR Processes with automated workflows
  • Marketing Campaigns with content approvals

πŸ“ Repository Structure

slack-n8n-integration-hub/
β”œβ”€β”€ app.js                          # Main Slack Bot application
β”œβ”€β”€ package.json                    # Dependencies and scripts
β”œβ”€β”€ .env.example                    # Environment configuration template
β”œβ”€β”€ README.md                       # Complete setup documentation
β”œβ”€β”€ CONTRIBUTING.md                 # Contribution guidelines
β”œβ”€β”€ Slack_Bot_n8n_Integration_Hub.json  # n8n workflow export
β”œβ”€β”€ n8n-workflow-examples.json     # Additional workflow examples
└── test-webhook.js                 # Webhook testing utilities

πŸŽ‰ Ready for n8n Community

This workflow is:

  • βœ… Fully Tested and working
  • βœ… Well Documented with setup instructions
  • βœ… Open Source and ready for community use
  • βœ… Extensible for various use cases
  • βœ… Production Ready with error handling

πŸ”— Get Started

  1. Clone the repository: git clone https://github.com/iam-niranjan/slack-n8n-integration-hub.git
  2. Follow the setup guide in the main README.md
  3. Import the n8n workflows from the JSON files
  4. Customize for your use case and explore the possibilities!

This showcase demonstrates that with n8n and Slack integration, the automation possibilities are truly endless! πŸš€

Ready to submit to n8n community for sharing and collaboration.

n8n Interactive Slack Approval & Data Submission System

This n8n workflow provides a flexible and interactive system for submitting data and getting approvals via Slack. It acts as a backend for a data submission form, allowing for review and approval processes directly within Slack.

What it does

This workflow automates the following steps:

  1. Listens for Data Submission: It waits for incoming data via a webhook, typically from a form submission or another system.
  2. Prepares Data for Slack: It processes the received data using a Function node, likely formatting it into a message suitable for Slack.
  3. Posts to Slack for Approval: It sends an interactive message to a specified Slack channel, presenting the submitted data and offering approval/rejection buttons.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Slack Account: A Slack workspace with an app configured to allow incoming webhooks and interactive messages. You will need to set up a Slack credential in n8n.
  • Webhook Source: A system or application (e.g., a web form, another n8n workflow, an external API) that can send data to the n8n webhook URL.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Webhook:
    • Locate the "Webhook" node.
    • Copy the "Webhook URL" and configure your external system to send data to this URL using a POST request.
  3. Configure Slack Credentials:
    • Locate the "Slack" node.
    • Select or create a Slack credential. This typically involves providing a Slack Bot Token or a Webhook URL from your Slack app.
    • Specify the "Channel" where the approval messages should be posted.
  4. Customize Function Node:
    • The "Function" node (named "Function") is where the incoming data is transformed into the Slack message format. You will likely need to edit the JavaScript code within this node to match the structure of your incoming data and how you want it displayed in Slack.
  5. Activate the Workflow: Once configured, activate the workflow.

Now, whenever data is sent to the Webhook URL, the workflow will trigger, process the data, and send an interactive approval message to your designated Slack channel.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β€” Manually start the workflow or schedule it to run periodically. Input Setup β€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the β€œSet Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatβ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. πŸ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing πŸ”§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation πŸ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com β†’ API keys (sidebar) Click "Create new secret key" β†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β†’ Dashboard β†’ API Keys Generate a new API key β†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βš™οΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β†’ the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β†’ Download File From Google Download File From Google β†’ Extract from File β†’ Update File to One Drive Extract from File β†’ Message a model Message a model β†’ Create or update an account Create or update an account β†’ Create an opportunity Create an opportunity β†’ Build SOQL Build SOQL β†’ Query PricebookEntries Query PricebookEntries β†’ Code in JavaScript Code in JavaScript β†’ Create Opportunity Line Items --- Quick setup checklist πŸ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. πŸ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name β†’ Account upsert fields Invoice code/date/amount β†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. βœ… Test: Drop a sample PDF β†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep β€œReturn only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942