This article provides a complete, practical walkthrough of the Stickynote Respondtowebhook Send Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Seamlessly Connect Slack to ServiceNow: An Automated Incident Lookup Workflow with n8n  
   
   Meta Description:  
   Streamline your ITSM processes by integrating Slack with ServiceNow using a low-code n8n workflow. Learn how to fetch and display incident details in Slack with this powerful automation.  
   
   Keywords:  
   n8n, Slack integration, ServiceNow API, ServiceNow automation, ITSM workflow, incident management, low-code automation, webhook, Slack slash command, ServiceNow incident lookup, workflow automation  
   
   Third-Party APIs Used:
   
   - Slack Webhooks (via Slash Command)
   - ServiceNow REST API (incident resource, basic authentication)
   
   Article:  
   
   Empower Slack with ServiceNow Insight: A No-Code n8n Workflow for Incident Management
   
   Modern IT teams rely on real-time information flow to respond to incidents swiftly and efficiently. When it comes to interacting with centralized IT Service Management (ITSM) tools like ServiceNow, context switching often slows down productivity. But what if your team could fetch full incident details straight from Slack with a simple command?
   
   That’s exactly what this n8n workflow achieves. With minimal setup and no coding required, this automation allows any team member to run a Slack slash command to fetch comprehensive incident details from ServiceNow and receive a structured, interactive response back in Slack.
   
   In this article, we’ll walk through the n8n workflow behind this integration and explore how it works step-by-step.
   
   🔗 About the Workflow
   
   The core flow consists of these stages:
   
   1. Receiving a request through a Slack command.
   2. Extracting the incident ID from the request.
   3. Querying ServiceNow based on the given ID.
   4. Parsing the response from ServiceNow.
   5. Sending a contextual response back to Slack—whether details are found, the incident doesn't exist, or there's a ServiceNow error.
   
   Let’s examine each of these components.
   
   📥 Step 1: Receiving the Slack Command
   
   At the heart of this workflow is the Webhook node, which listens for incoming POST requests triggered by Slack Slash Commands. When a Slack user types a command such as:
   
   /incident_lookup INC1234567
   
   Slack sends a JSON payload containing their input. The Webhook node is configured to receive this data and route it to the next step.
   
   🧠 Step 2: Extracting the Incident ID
   
   The second node, “Extract Incident ID from Response,” uses n8n’s Set node to extract the user’s input (e.g., the incident number like "INC1234567") from the request body. This becomes a variable that will be used to query ServiceNow.
   
   🗂️ Step 3: Querying ServiceNow for the Incident
   
   The incident ID is passed to the “Search For Incident in ServiceNow” node. This node uses the ServiceNow REST API (with Basic Auth credentials) to look up the incident from the ServiceNow "incident" resource.
   
   It uses a filter in the query like:
   
   GOTOnumber=INC1234567  
   
   If a valid result is returned, it includes fields like number, description, severity, caller id, priority, state, category, and date opened.
   
   🔍 Step 4: Handling Different ServiceNow Responses
   
   Using a Switch node titled “Parse ServiceNow Response,” the workflow evaluates which of three possible scenarios has occurred:
   
   - Incident Found: If the incident number exists in the response.
   - Incident Not Found: If the number field does not exist (indicating no match).
   - ServiceNow Error: If ServiceNow returned an error object (e.g., API authentication failed or system error).
   
   Each of these outcomes gets its own branch in the workflow.
   
   📤 Step 5: Responding to Slack Based on Outcome
   
   Depending on which condition is met in the previous step, the workflow routes to one of three response nodes:
   
   - ✅ Send Incident Details to Slack  
     The “Send Incident Details to Slack” node formats the incident details using Slack Block Kit. It includes a header, structured fields (like Severity, Description, Priority, etc.), and even a button that links directly to the incident in ServiceNow.
   
   - ⚠️ Notify User No Incident Was Found  
     If the incident was not found, this node sends a polite, markdown-formatted Slack message informing the user that the ID may be incorrect.
   
   - 🚨 Notify User of Error with ServiceNow  
     In case of ServiceNow connection issues, the user is notified immediately with a clear warning and an emoji, advising them to review the n8n workflow.
   
   📌 Why This Workflow Matters
   
   This solution dramatically reduces the time spent searching through ServiceNow’s interface. By empowering users to query incidents right from Slack:
   
   - IT support is more responsive.
   - Data lookup processes are simplified.
   - Teams get actionable data quickly, keeping workflows in their preferred communication tool.
   
   The real beauty lies in the flexibility. This workflow can be cloned, modified, or scaled to include more ServiceNow fields or used with other ServiceNow resources like Change Requests.
   
   💡 Final Thoughts
   
   This n8n workflow is an excellent example of how powerful low-code platforms can be when bridging communication tools like Slack with enterprise systems like ServiceNow. It removes friction from incident management and puts actionable insights at the fingertips of anyone in your organization.
   
   By using this workflow, your team can unlock real-time insights and improve ITSM efficiency— all without writing a single line of code.
   
   Looking for more automation ideas? Start by expanding this template to support commands like /incident_update or /change_request. With n8n’s flexibility, the sky’s the limit.
   
   Want to try this yourself? Head over to n8n.io and start building with service connectors that boost productivity today.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.