Create_Unique_Jira_tickets_from_Splunk_alerts
Configured with Jira, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Integration
- Transform
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Webhook | Trigger | Webhook | See node parameters |
| Add Ticket Comment | Integration | Jira | issueComment |
| Search Ticket | Integration | Jira | getAll |
| Set Host Name | Transform | Edit Fields | See node parameters |
| IF Ticket Not Exists | Routing | If | See node parameters |
| Create Ticket | Integration | Jira | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
jiraSoftwareCloudApi
Workflow notes
Webhook Node
Webhook Node
To setup your webhook integration for Splunk, first ensure that splunk is setup to send alerts to a webhook by visiting the Setup Guide here. You will copy the n8n webhook url opening the webhook node below.
- Form Access URLs:
- Execute Mode:
https://n8n.domain.com/webhook/test/webhookpath- Use this to execute the workflow interactively within the n8n canvas. Hit the 'Execute Workflow' button to see real-time execution results. We have pinned data in the webhook node to make testing easier. - Silent Mode:
https://n8n.domain.com/webhook/webhookpath- Use this for background execution without canvas updates. Results will be logged silently and can be reviewed in the 'Executions' tab.
- Execute Mode:
Normalize Hostname
Normalize Hostname
To ensure no special characters are passed into jira and create issues, this set node removes special characters from the splunk-host-name and uses that to search and create tickets. This host name is saved as a custom field.
Create a new ticket
Create a new ticket
This creates a new ticket in your Prjoect and issue type. Ensure to update these values to ensure it works correctly.
Add Ticket Comment
Add Ticket Comment
This adds the alert as a comment in the existing ticket, to ensure the data is not duplicated.
Check if ticket found
Check if ticket found
This checks $json.key to see if the value was found, and route accordingly.
Create_Unique_Jira_tickets_from_Splunk_alerts
Create_Unique_Jira_tickets_from_Splunk_alerts
Purpose and structure
This folder contains the Create_Unique_Jira_tickets_from_Splunk_alerts workflow. Its executable nodes use if, jira, set, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Stickynote/1986_Stickynote_Jira_Create_Webhook.json MIT; preserve source notices.