Zendesk to Jira Issue Sync with Duplicate Detection
High-Level Summary
This workflow automatically creates Jira issues from new Zendesk tickets and intelligently handles duplicates. When a new Zendesk ticket comes in, it checks whether a Jira issue already exists for that ticket (by looking at a custom field on the Zendesk ticket). If no Jira issue exists, it creates a new one and updates the Zendesk ticket with the Jira issue key. If a Jira issue already exists, it simply adds a comment to the existing Jira issue with the new Zendesk ticket comment. This prevents duplicate Jira issues and keeps both systems in sync.
Node-by-Node Breakdown
-
On new Zendesk ticket (Webhook) — No auth
- Listens for incoming webhook POST requests from Zendesk at the configured path
- Triggered automatically when a new ticket is created or updated in Zendesk
- Requires Zendesk to be configured to send webhook notifications to this n8n webhook URL
-
Get ticket (Zendesk) — OAuth2
- Fetches the full Zendesk ticket details using the ticket ID from the webhook payload
- Retrieves all custom fields, including the one that stores the Jira issue key
- Uses the Zendesk node with OAuth2 authentication
-
Determine (Function) — No auth
- Custom JavaScript code that extracts the Jira issue key from the Zendesk ticket's custom fields
- Checks a specific custom field ID (configurable in the code) to see if a Jira issue key already exists
- Outputs an object with the Jira issue key (empty string if none exists)
-
IF (IF) — No auth
- Checks if the Jira issue key from the previous node is not empty
- If the key exists (true branch): routes to "Create comment to existing issue"
- If the key is empty (false branch): routes to "Create issue"
-
Create comment to existing issue (Jira) — OAuth2
- Adds a comment to the existing Jira issue using the issue key from the Determine node
- The comment content comes from the original Zendesk ticket's comment field
- Only executed when a Jira issue already exists for this ticket
-
Create issue (Jira) — OAuth2
- Creates a new Jira issue in the specified project (ID: 10000) with issue type (ID: 10003)
- The summary is taken from the Zendesk ticket subject
- The description includes a link back to the original Zendesk ticket
- Only executed when no Jira issue exists yet
-
Update ticket (Zendesk) — OAuth2
- Updates the original Zendesk ticket by setting the custom field (ID: 6689934837021) with the newly created Jira issue key
- This ensures future updates to the same Zendesk ticket will find the existing Jira issue
- Only executed after a new Jira issue is created
Setup Instructions
Required Accounts & Services
- Zendesk account with admin access to create webhooks and custom fields
- Jira Cloud account with API access (Jira Software or Jira Service Management)
- n8n instance (self-hosted or cloud)
Configuration Steps
-
Zendesk Setup:
- Create a custom text field in Zendesk called "Jira Issue Key" (note the field ID)
- Configure a Zendesk webhook to POST to your n8n webhook URL when tickets are created/updated
- Set up OAuth2 credentials in n8n for Zendesk
-
Jira Setup:
- Note your Jira project ID and issue type ID (found in Jira admin)
- Set up OAuth2 credentials in n8n for Jira
-
n8n Workflow Configuration:
- Update the custom field ID in the "Determine" node's JavaScript code (currently 6689934837021)
- Update the Jira project ID (currently 10000) and issue type ID (currently 10003) in the "Create issue" node
- Activate the workflow and copy the webhook URL
Use Cases & Variations
Primary Use Case
- IT Support Teams: Automatically create Jira tickets from Zendesk support requests while preventing duplicates
- DevOps Integration: Link customer support tickets to development issues with bidirectional tracking
Possible Adaptations
- Different Trigger: Replace the webhook with a Schedule trigger to batch-process tickets periodically
- Additional Fields: Map more Zendesk fields (priority, assignee, tags) to Jira issue fields
- Status Sync: Add nodes to update Zendesk ticket status when Jira issue status changes
- Multiple Projects: Route tickets to different Jira projects based on Zendesk ticket category
- Error Handling: Add error handling nodes to notify admins if sync fails
- Slack Notification: Add a Slack node to notify team members when a new Jira issue is created
Alternative Services
- Replace Zendesk with Freshdesk, Intercom, or HubSpot tickets
- Replace Jira with Linear, Asana, or Trello for project management
Workflow JSON
{
"meta": {
"instanceId": "237600ca44303ce91fa31ee72babcdc8493f55ee2c0e8aa2b78b3b4ce6f70bd9"
},
"nodes": [
{
"id": "b374f136-0050-40ea-b889-03c1e20a161e",
"name": "IF",
"type": "n8n-nodes-base.if",
"position": [
1000,
300
],
"parameters": {
"conditions": {
"string": [
{
"value1": "={{$node[\"Determine\"].json[\"Jira issue key\"]}}",
"operation": "isNotEmpty"
}
]
}
},
"typeVersion": 1
},
{
"id": "52e85300-9a2f-45e9-973e-0fda49a50bf1",
"name": "Create issue",
"type": "n8n-nodes-base.jira",
"position": [
1180,
400
],
"parameters": {
"project": "10000",
"summary": "={{$node[\"Get ticket\"].json[\"subject\"]}}",
"issueType": "10003",
"additionalFields": {
"description": "=See Zendesk issue at: https://n8n.zendesk.com/agent/tickets/{{$node[\"Get ticket\"].json[\"id\"]}}"
}
},
"credentials": {
"jiraSoftwareCloudApi": {
"id": "23",
"name": "[UPDATE ME]"
}
},
"typeVersion": 1
},
{
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
AI Customer Support Chatbot with Elasticsearch Knowledge Base
Overview This workflow transforms a webhook endpoint into an intelligent customer support chatbot. It receives a customer question, searches a knowledge base stored in Elasticsearch, and generates a helpful, context-aware reply using OpenAI's GPT-4. The bot is designed to reduce human workload by answering common queries instantly, and gracefully escalates to a human agent when the answer is not found. It's ideal for embedding into a website, messaging app, or any frontend that can send HTTP POST requests. Node-by-Node Breakdown Chatbot Webhook (Frontend Trigger) — Type: (No auth) - Listens for POST requests at the path . The webhook ID is . This is the entry point where your frontend sends the customer's question as JSON body (e.g., ). Extract Customer Query — Type: (No auth) - Extracts from the incoming JSON body using a simple JavaScript code snippet: . This prepares the query for the next steps. Search Knowledge Base (Elasticsearch) — Type: (Requires Elasticsearch credentials – basic auth / API key) - Performs a search on the index using the extracted question as the query. The parameter is set to . It returns matching documents from the knowledge base. Generate AI Response with GPT-4 — Type: (API Key auth) - Uses the model to generate a response. The system message instructs the assistant to use the provided knowledge base content and to politely escalate if the answer is not found. The user message combines the customer question and the top knowledge base result (). Format Chatbot Reply — Type: (No auth) - Extracts the final reply from the OpenAI response: . This ensures the output is properly structured. Return Chatbot Reply — Type: (No auth) - Sends the formatted reply back to the caller (the frontend) as a JSON response. Setup Instructions Elasticsearch: You need a running Elasticsearch instance (cloud or self-hosted) with an index named . Populate it with documents containing your knowledge base articles (e.g., each document should have a field). Configure the Elasticsearch node in n8n with your host, port, and authentication credentials (API key or username/password). OpenAI: Obtain an API key from OpenAI. Add it as a credential in n8n (type: OpenAI API). Webhook URL: After activating the workflow, n8n will generate a unique webhook URL (e.g., ). Use this URL in your frontend (website, chatbot widget, etc.) to send POST requests. Activate the workflow: Toggle the workflow to active in n8n for the webhook to start listening. Use Cases & Adaptations Customer Support Portal: Embed the webhook URL in a live chat widget on your website to answer FAQs instantly. Slack or Discord Bot: Replace the webhook trigger with a Slack/Discord trigger and adjust the response format to send messages back to the channel. Multiple Knowledge Bases: Modify the Elasticsearch query to search across multiple indices or filter by category. Fallback to Human: Customize the GPT-4 system message to trigger a notification (e.g., email or Slack message) when the answer is not found. Model Upgrade: Swap for to reduce cost or use a custom fine-tuned model. Language Support: Add a language detection step before the query to route to different knowledge bases or translate the response.
HR & IT Helpdesk Chatbot with Audio Transcription on Telegram
Overview This workflow builds a fully functional HR & IT helpdesk chatbot that operates through Telegram. It ingests internal policy documents (e.g., employee handbooks, IT FAQs), creates a searchable knowledge base using vector embeddings stored in PostgreSQL, and then answers employee questions via text or voice messages. The chatbot uses Retrieval-Augmented Generation (RAG) to provide accurate, context-aware responses based on your company's specific policies. This is particularly useful for organizations that want to automate common HR and IT inquiries, reduce the burden on support teams, and provide 24/7 self-service to employees. The inclusion of voice message transcription makes it accessible for users who prefer speaking over typing. Workflow Steps Phase 1: Knowledge Base Ingestion (Run Once or on Update) When clicking 'Test workflow' (Manual Trigger — No auth) — This node starts the ingestion process manually. It is intended to be run once when setting up the workflow or whenever the policy documents are updated. HTTP Request (HTTP Request — No auth) — Fetches a PDF file from a public URL (in this example, an employee handbook from an S3 bucket). The URL can be changed to point to any PDF hosted online or on a shared drive. Extract from File (Extract from File — No auth) — Parses the downloaded PDF and extracts its text content. The operation is set to "pdf" to handle PDF documents. Recursive Character Text Splitter (Text Splitter — No auth) — Splits the extracted text into smaller chunks of 2000 characters each. This is necessary for creating meaningful vector embeddings and for efficient retrieval. Default Data Loader (Document Loader — No auth) — Converts the text chunks into document objects that can be stored in the vector store. It takes the text from the Extract from File node using the expression . Embeddings OpenAI (Embeddings — OpenAI API Key auth) — Generates vector embeddings for each text chunk using OpenAI's embedding models. These embeddings represent the semantic meaning of the text. Create HR Policies (PostgreSQL PGVector Store — Database credentials auth) — Inserts the document chunks and their embeddings into a PostgreSQL database with pgvector extension. This creates the searchable knowledge base. Phase 2: Chatbot Runtime Telegram Trigger (Telegram Trigger — Telegram Bot Token auth) — Listens for incoming messages on a Telegram bot. It captures all messages (text, voice, etc.) sent to the bot. Verify Message Type (Switch — No auth) — Routes messages based on their type: - Text messages (containing ) → sent to the AI agent - Voice messages (containing ) → sent for transcription - Other types → sent to a fallback response Edit Fields (Set — No auth) — For text messages, extracts the text content and passes it to the AI agent. Uses the expression . Telegram1 (Telegram — Telegram Bot Token auth) — For voice messages, downloads the audio file from Telegram using the from the incoming message. OpenAI (OpenAI — OpenAI API Key auth) — Transcribes the downloaded voice message into text using OpenAI's Whisper transcription API. The operation is set to "transcribe" and the binary property is set to "data". Unsupported Message Type (Telegram — Telegram Bot Token auth) — Sends a fallback message "I'm not able to process this message type." for unsupported message types (e.g., stickers, locations). AI Agent (AI Agent — No auth) — The core conversational agent. It receives the user's text (either directly or transcribed from voice) and generates a response. The system message is set to "You are a helpful assistant for HR and employee policies". OpenAI Chat Model (Chat Model — OpenAI API Key auth) — The language model powering the AI agent. It generates natural language responses based on the context and retrieved information. Postgres Chat Memory (Memory — Database credentials auth) — Maintains conversation history per user, using the Telegram chat ID as the session key. This allows the chatbot to remember context across multiple messages. Answer questions with a vector store (Vector Store Tool — No auth) — A tool that the AI agent uses to query the knowledge base. It is configured with the name "hremployeepolicies" and description "data for HR and employee policies". Postgres PGVector Store (Vector Store — Database credentials auth) — The actual vector store connection that retrieves relevant document chunks based on the user's query. OpenAI Chat Model1 (Chat Model — OpenAI API Key auth) — A second language model instance used specifically by the vector store tool for re-ranking or summarizing retrieved results. Embeddings OpenAI1 (Embeddings — OpenAI API Key auth) — A second embeddings instance used by the vector store tool to embed the user's query for similarity search. Telegram (Telegram — Telegram Bot Token auth) — Sends the AI agent's response back to the user in the same Telegram chat. Uses the expression for the response text. Setup Instructions Prerequisites OpenAI Account: You need an OpenAI API key with access to: - GPT-4 or GPT-3.5 for chat completion - text-embedding-ada-002 for embeddings - Whisper for audio transcription Telegram Bot: Create a bot via @BotFather on Telegram and obtain the bot token. PostgreSQL Database: A PostgreSQL database with the pgvector extension installed. You can use: - A local PostgreSQL instance - A cloud provider like Supabase, Aiven, or AWS RDS Configuration Steps Set up credentials in n8n: - OpenAI API: Add your OpenAI API key as a credential - Telegram Bot: Add your bot token as a credential - PostgreSQL: Add your database connection details (host, port, database name, user, password) Update the PDF URL: In the HTTP Request node, change the URL to point to your own policy documents (e.g., company handbook, IT policies, FAQs). Run the ingestion: Click "Test Workflow" on the When clicking 'Test workflow' node to populate the vector store with your documents. Set the webhook: Activate the workflow and set the Telegram webhook URL to your n8n instance's webhook URL (provided by the Telegram Trigger node). Test the chatbot: Send a text or voice message to your Telegram bot and verify it responds with relevant information from your policies. Use Cases and Variations Primary Use Cases HR Helpdesk: Answer questions about leave policies, benefits, payroll, company culture, and onboarding procedures. IT Support Desk: Provide troubleshooting steps for common IT issues, password reset instructions, software access requests, and hardware policies. Employee Onboarding: New hires can ask questions about company policies, team structures, and first-day procedures. Possible Variations Multiple Document Sources: Instead of a single PDF, use multiple HTTP Request nodes or connect to Google Drive, SharePoint, or Confluence to ingest documents from various sources. Different Channels: Replace the Telegram trigger with Slack, Microsoft Teams, or a web chat widget to deploy the chatbot on other platforms. Multi-language Support: Configure the OpenAI model to respond in multiple languages based on user preference or detected language. Human Handoff: Add a condition to escalate complex queries to a human agent via email or a ticketing system. Feedback Loop: Add a mechanism for users to rate responses and use that feedback to improve the knowledge base. Scheduled Re-indexing: Add a Cron trigger to periodically re-ingest documents to keep the knowledge base up to date.
Receive and Reply to Messages Across WhatsApp, Instagram, and Facebook Messenger with Fiwano
Overview This workflow provides a unified integration for receiving and replying to messages from WhatsApp, Instagram Direct Messages, and Facebook Messenger using the Fiwano platform. It demonstrates how to handle incoming messages from all three Meta-owned messaging channels through a single trigger and action node set, eliminating the need to build separate integrations for each platform. The workflow is ideal for customer support, lead response, or any scenario where you need to manage multi-channel messaging from one n8n instance. Workflow Steps Fiwano Trigger (API Key auth) — This node listens for incoming messages from all connected channels (WhatsApp, Instagram, Facebook Messenger). It uses the parameter to automatically register the workflow for every active channel in your Fiwano account. The trigger fires on "Message Received" events and provides a normalized payload regardless of which channel the message came from. Example — route by message type (No auth) — This is an IF node that checks the field from the incoming message. It routes messages into two branches: one for text messages (where equals "text") and another for all other message types (images, audio, video, documents, etc.). This demonstrates how to implement different reply logic based on message content type. Example — send text reply (API Key auth) — This Fiwano Send node replies to text messages. It uses the following parameters: - : Taken from the incoming message's field to ensure the reply goes back through the same channel - : Set to the sender's ID from - : A template that echoes the user's message: Example — send attachment reply (API Key auth) — This second Fiwano Send node handles replies to non-text messages (attachments). Its parameters: - : Same as above, using - : Same as above, using - : Acknowledges the attachment type: Setup Instructions Prerequisites A Fiwano account (sign up at fiwano.com) At least one connected messaging channel (WhatsApp Business API, Instagram Professional account, or Facebook Page connected to Messenger) n8n instance (self-hosted or cloud) with public accessibility for webhook triggers Installation Steps Install the n8n-nodes-fiwano community package in your n8n editor (verified package available in the n8n community nodes registry) Create a Fiwano API credential in n8n with your API key from the Fiwano portal (Recommended) Set a Webhook Secret on the credential for signature verification Connect your messaging channels through the Fiwano portal or their channel-connection API Save and activate the workflow — the trigger will auto-register for all active channels Use Cases and Variations Primary Use Cases Customer Support: Route incoming messages to a helpdesk or ticketing system based on message content or sender Lead Response: Automatically reply to inquiries from ads or business pages with personalized messages Notification System: Forward messages to Slack, email, or other internal tools Adaptation Ideas Replace the simple IF router with a more complex decision tree using Switch nodes or AI classification Add a database lookup (e.g., Airtable, Google Sheets) to check if the sender is an existing customer Integrate with OpenAI or other AI services to generate intelligent replies Add logging to a spreadsheet or database for analytics Implement different response templates for each channel type using the field Add human handoff logic when the AI or automated response cannot handle the query Important Notes The normalized payload from Fiwano includes: , (whatsapp/instagram/messenger), , , , , and (for attachments) You typically don't need to branch by channel type unless your business logic requires channel-specific behavior n8n must be publicly reachable for the webhook trigger to receive messages from Fiwano