Skip to main content

Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing

Workflow preview

Workflow preview
100%
Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Who is this for? IT teams and support organizations looking to automate Level 1 support with AI ...

Best for

  • Support Chatbot automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.slacktrigger, n8n-nodes-base.slack, @n8n/n8n-nodes-langchain.memorybufferwindow, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.vectorstoresupabase, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by inderjeet Bhambra.

Original n8n.io source

1.1 Workflow description

Title
Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing
Workflow name
Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

Who is this for?

IT teams and support organizations looking to automate Level 1 support with AI-powered assistance while maintaining proper ticket management workflows.

What problem does this solve?

Eliminates repetitive manual support tasks by providing instant, context-aware assistance that references organizational knowledge and creates structured tickets when needed.

What this workflow does

  • RAG Pipeline: Processes PDF/CSV documents into searchable vector database
  • Intelligent Slack Bot: This AI-helpdesk assistant handles support requests with thread-aware conversations
  • Vector Knowledge Search: Searches embedded knowledge base articles and historical case data
  • JIRA Integration: Creates, searches, and manages support tickets automatically
  • Emoji Reactions: Users can trigger actions (create tickets, escalate) via emoji reactions

Requirements

Required Accounts:

  • n8n Cloud or self-hosted instance
  • Slack workspace with admin access
  • Supabase account (vector database)
  • JIRA Cloud instance
  • OpenAI API key

Technical Prerequisites:

  • Basic n8n workflow knowledge
  • Slack app creation experience
  • Understanding of vector databases

Setup Steps

1. Slack App Configuration

  • Create new Slack app with Bot Token Scopes: app_mentions:read, channels:history, channels:read, groups:history, groups:read, im:history, im:read, mpim:history, mpim:read, users:read
  • Configure Event Subscriptions: app_mention, message.channels, message.groups, reaction_added
  • Set Request URL to your n8n Slack Trigger webhook

2. Supabase Vector Database Setup

  • Create new Supabase project
  • Enable pgvector extension
  • Create documents table with vector column (1536 dimensions for OpenAI embeddings)
  • Configure RLS policies for secure access

3. JIRA Configuration

  • Generate API token from JIRA Cloud
  • Create helpdesk project with appropriate issue types
  • Note project ID and issue type IDs for workflow configuration

4. n8n Workflow Configuration

  • Import workflow and configure credentials
  • Update Slack channel IDs in trigger nodes
  • Set OpenAI API key in all OpenAI nodes
  • Configure Supabase connection in vector store nodes
  • Update JIRA project settings in MCP server nodes

5. Knowledge Base Data Format

Supported file formats: PDF, CSV CSV Structure: Structure your data with columns, but not limited to, Ticket#, Issue Description, Issue Summary, Resolution Provided, Case Status, Contact User PDF Content: Technical documentation, troubleshooting guides, policy documents

Upload documents via the form trigger to automatically embed in vector database.

Customization Options

AI Agent Behavior

  • Modify system prompt in AIHelpdesk Agent node
  • Adjust conversation memory window (default: 20 messages)
  • Change AI model (GPT-4o, GPT-3.5-turbo, etc.)

Reaction Mappings

  • Customize emoji-to-action mappings in Reaction Handler code
  • Add new reaction types for department-specific workflows
  • Configure escalation rules and priority levels

JIRA Integration

  • Customize ticket templates and fields
  • Add auto-assignment rules based on issue type
  • Configure SLA and priority mappings

Vector Search

  • Adjust similarity thresholds for knowledge retrieval
  • Modify search result limits and relevance scoring
  • Add metadata filtering for departmental knowledge bases

Advanced Features

  • Thread-aware conversation memory
  • Automatic bot loop prevention
  • Context-preserving ticket creation
  • Multi-modal file processing (PDF + CSV)
  • Scalable MCP architecture for tool integration

Use Cases

  • Level 1 IT Support: Automate common troubleshooting workflows
  • Employee Onboarding: Answer policy and procedure questions
  • Internal Help Desk: Route and track internal service requests
  • Knowledge Management: Make organizational knowledge searchable and actionable

Template includes

  • Complete Slack integration with thread support
  • RAG pipeline for document processing
  • Vector similarity search implementation
  • JIRA ticket lifecycle management
  • Emoji reaction-based user interactions
  • Comprehensive error handling and validation

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Slack Trigger

Type / Role
n8n-nodes-base.slackTrigger - slackTrigger
Config choices
Version 1

Block 2 - Send a message

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 3 - Simple Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

Block 4 - Format Output

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - Supabase Vector Store

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreSupabase - vectorStoreSupabase
Config choices
Version 1.3

Block 6 - Embeddings OpenAI

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 7 - Default Data Loader

Type / Role
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices
Version 1.1

Block 8 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - On form submission

Type / Role
n8n-nodes-base.formTrigger - formTrigger
Config choices
Version 2.2

Block 10 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - MCP Server Trigger

Type / Role
@n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices
Version 2

Block 14 - Supabase Vector Store1

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreSupabase - vectorStoreSupabase
Config choices
Version 1.3

Block 15 - Embeddings OpenAI1

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 16 - Create Ticket

Type / Role
n8n-nodes-base.jiraTool - jiraTool
Config choices
Version 1

Block 17 - Search

Type / Role
n8n-nodes-base.jiraTool - jiraTool
Config choices
Version 1

Block 18 - Get Status

Type / Role
n8n-nodes-base.jiraTool - jiraTool
Config choices
Version 1

Block 19 - helpdesk_tools

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1

Block 20 - Change Priority

Type / Role
n8n-nodes-base.jiraTool - jiraTool
Config choices
Version 1

Block 21 - changelog

Type / Role
n8n-nodes-base.jiraTool - jiraTool
Config choices
Version 1

Block 22 - Check app_mention

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 23 - OpenAI

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 24 - AIhelpdesk

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.1

Showing the first 24 of 25 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing
Complexity advanced
Nodes 25
Categories Support Chatbot, AI RAG
Author inderjeet Bhambra
Published 28 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6549/6549.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automated Slack IT helpdesk with GPT, Supabase vector search, and JIRA ticketing do?

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Who is this for? IT teams and support organizations looking to automate Level 1 support with AI ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI RAG use case.