Skip to main content

AI-powered ServiceNow chat triage with GPT-4 — incident & request manager

Workflow preview

Workflow preview
100%
AI-powered ServiceNow chat triage with GPT-4 — incident & request manager preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Automated Incident and Request Management in ServiceNow Who’s it for This workflow is designed for IT teams, service desk agents, and operations managers who use ServiceNow. It reduces manual effor...

Best for

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

Tools used

@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.textclassifier, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.memorybufferwindow, @n8n/n8n-nodes-langchain.chainsummarization, n8n-nodes-base.httprequest, n8n-nodes-base.servicenow

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
AI-powered ServiceNow chat triage with GPT-4 — incident & request manager
Workflow name
AI-powered ServiceNow chat triage with GPT-4 — incident & request manager

Automated Incident and Request Management in ServiceNow

Who’s it for

This workflow is designed for IT teams, service desk agents, and operations managers who use ServiceNow. It reduces manual effort by automatically classifying chat messages as Incidents or Requests, creating/updating them in ServiceNow, and summarizing ticket updates.


What it does

  • Receives incoming chat messages.

  • Classifies the message as one of:

    • Incident (something broken, unavailable, or a complaint)
    • Request (access, provisioning, product/order related)
    • Follow-ups (incident or request update checks)
    • Update action (user wants to add info to an existing ticket)
    • Everything else (knowledge search / general query).
  • Creates Incidents in ServiceNow via the ServiceNow node.

  • Creates Requests in ServiceNow using the Service Catalog API.

  • Updates existing Incidents with new work notes when the user provides an update.

  • Pulls existing incident/request work notes for summaries.

  • Optionally uses SerpAPI for general queries (if enabled).

  • Returns a concise summary back to the user through the webhook.


Requirements

  • ServiceNow account with API access (Basic Auth)
  • OpenAI API key (used by the classifier and summarizer)
  • SerpAPI key (optional – for general web lookups)

Credentials needed

You will need to set up the following credentials in n8n:

  1. ServiceNow Basic Auth (username, password, instance URL).
  2. OpenAI API (API key).
  3. SerpAPI (optional – only if you want web search enabled).

How to set up

  1. Import the workflow JSON into your n8n instance.

  2. Create the credentials mentioned above and assign them to the corresponding nodes:

    • Create an incidentServiceNow Basic Auth
    • HTTP Request1 (for Service Catalog requests) → ServiceNow Basic Auth
    • OpenAI Chat Model / OpenAI Chat Model1 / OpenAI Chat Model2 / OpenAI Chat Model3OpenAI API
    • SerpAPI node (optional) → SerpAPI key
  3. Adjust the ServiceNow instance URL in the HTTP Request node to match your environment.

  4. Deploy the workflow.

  5. Send a test chat message to trigger the workflow.


How to customize

  • Update the classification rules in the Text Classifier node if your organization uses different definitions for incidents vs. requests.
  • Edit the summary prompt in the Summarization Chain to include or exclude specific fields.
  • Add additional notification nodes (Slack, Teams, or Email) if you want updates pushed to other channels.

Notes & Limitations

  • This workflow creates general requests in ServiceNow using the catalog API. For production, update the Service Catalog item ID to match your environment.
  • “Everything else” category uses SerpAPI. If not configured, those queries will not return results.
  • This workflow requires OpenAI GPT-4.1 mini (or another supported model) for classification and summarization.

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 - When chat message received

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

Block 2 - OpenAI Chat Model

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

Block 3 - Text Classifier

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

Block 4 - AI Agent

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

Block 5 - OpenAI Chat Model1

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

Block 6 - Simple Memory

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

Block 7 - Summarization Chain

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

Block 8 - OpenAI Chat Model3

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

Block 9 - HTTP Request1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Create an incident

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

Block 11 - SerpAPI

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

Block 12 - Sticky Note

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

Block 13 - Sticky Note1

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

Block 14 - Sticky Note3

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

Block 15 - Sticky Note4

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

Block 16 - Respond to Webhook

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.4

Block 17 - AI Transform REQ

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

Block 18 - AI Transform INC

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

Block 19 - Get many incidents

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

Block 20 - HTTP Request

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 21 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 22 - Edit Fields

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

Block 23 - Code in JavaScript

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 24 - AI Agent1

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

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

3. Summary Table

Workflow AI-powered ServiceNow chat triage with GPT-4 — incident & request manager
Complexity advanced
Nodes 30
Categories Support Chatbot, AI Chatbot
Author Ritesh
Published 23 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8886/8886.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 AI-powered ServiceNow chat triage with GPT-4 — incident & request manager do?

Automated Incident and Request Management in ServiceNow Who’s it for This workflow is designed for IT teams, service desk agents, and operations managers who use ServiceNow. It reduces manual effor...

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 Chatbot use case.