Auto-Monitor AI Vulnerability RSS and Create ServiceNow Security Incidents with n8n
Input: AI vulnerability RSS feed; Process: scheduled fetch → full-text extraction → GPT parsing → split into items → write to ServiceNow; Output: ServiceNow Security Incident
- Who
- Security operations teams or engineers who want to automate AI vulnerability intelligence tracking
- You get
- Automatically monitor RSS on a schedule, turn new vulnerabilities into structured summaries, and create ServiceNow security incidents without manual feed watching
- You need
- n8n · servicenow · jina-ai
Constraints
Prerequisites: accessible n8n instance; credentials required are openAiApi, serviceNowBasicApi, and jinaAiApi. Cost: OpenAI usage billed by token; Jina AI and ServiceNow billed per their platforms. Boundaries: RSS source must be reachable; ServiceNow account needs incident creation permission. The template’s Schedule Trigger interval is an empty object in workflow.json and must be configured manually.
What they did
Author yajna published an n8n template (n8n ID 7225) demonstrating automated monitoring of an AI vulnerability RSS feed: a Schedule Trigger initiates the workflow, RSS Read fetches items, Jina AI retrieves full article text, an OpenAI GPT-4.1-mini-powered Information Extractor parses fields such as title, link, pubDate, creator, and content, Split Out separates the array into individual records, and each record creates a ServiceNow Security Incident.
How it went
Source report (author_report): the template is intended for security teams to track and respond quickly to emerging AI-related threats without manual feed monitoring. The template shows 1390 views on n8n. This site has not reproduced or verified the workflow.
Worth knowing
1. The RSS URL in the template is an example (rss.app); replace it with a trusted vulnerability intelligence feed in production. 2. The Schedule Trigger interval is an empty object in workflow.json and must be set manually after import. 3. Three credentials are required: openAiApi, serviceNowBasicApi, and jinaAiApi; the ServiceNow account needs permission to create incidents. 4. The Information Extractor inputSchema defines Title/Description/PublishedTime/SiteName, while the systemPromptTemplate extracts title/link/pubDate/creator/content; they are not fully aligned—follow the systemPromptTemplate and adjust the schema as needed. 5. Default model is gpt-4.1-mini; the template description mentions GPT-4, and the selectable models include gpt-4.1-mini, gpt-4.1, and gpt-4. 6. No per-node retry or error handling branches are provided; consider adding them for production use.
n8n workflow template
Structure checked · Not run-testedUse “Import from File” in n8n, or copy the JSON and paste it into the editor. Connect your own accounts, then try test data. The template is inactive by default.
Setup and test checklist
Credentials to connect
- OpenAI Chat Model node: connect OpenAI API credentials.
- Create an incident node: connect serviceNowBasicApi credentials.
- Read URL content node: connect jinaAiApi credentials.
Configuration to replace
- Source template is n8n public workflow #7225 (~7 nodes). Keep inactive after import; verify triggers, expressions and external API endpoints.
- Sticky-note guidance is informational; replace placeholders with your own accounts, sheet schemas or channel IDs.
Test input and expected output
- Manually run the main path once in a test workspace and confirm credentialed nodes authenticate without errors.
- Drive one synthetic/redacted sample through and check output fields and downstream writes before enabling in production.
Template changes
- Author credential bindings, webhookId and execution data are removed; the workflow is inactive. Nodes, connections and original prompts are preserved. Not run-tested in n8n.
- No business-logic edits; verify keys, quotas and privacy compliance before use.
Template retrieved: 2026-10-24
Steps
Configure Schedule Trigger and RSS Source
Add a Schedule Trigger node in n8n and set the run interval (e.g., every 15 minutes). Then add an RSS Read node and set its URL to an accessible AI vulnerability RSS address (the template example is https://rss.app/feeds/tbFqDT5HIb59.xml; replace with your actual feed). When run, you should see a list of RSS items as output.
Fetch Full Article Content
Add a Read URL content (Jina AI) node and set the URL parameter to `={{ $json.link }}` to receive article links from RSS Read and retrieve full content. Configure the jinaAiApi credential beforehand. When run, it should output an article object containing fields such as metadata and content.
Execution prompt · Source text。Read URL content node url parameter
={{ $json.link }}Configure Information Extractor and OpenAI Model
Add an Information Extractor node and bind an OpenAI Chat Model as the language model. In OpenAI Chat Model, select the model (template default is gpt-4.1-mini; gpt-4.1 or gpt-4 are also selectable) and configure the openAiApi credential. In Information Extractor, fill in text and systemPromptTemplate as shown below. When run, it should output a JSON array named results containing title, link, pubDate, creator, and content.
Execution prompt · Source text。Information Extractor node text parameter
=Snippet {{ $json.metadata.description}} Title{{ $json.title}} pubDate{{ $json.publishedTime}} Creator {{ $json.metadata.author}} content {{ $json.content}}Execution prompt · Source text。Information Extractor node options.systemPromptTemplate parameter
You are an expert extraction algorithm. Only extract relevant information from the input text. Extract data as JSON objects with the following fields: title (string): The title of the news article or vulnerability report. link (string): The URL linking to the full article. pubDate (string, ISO 8601 format preferred): The publication date of the article. creator (string): The author or source of the article. content (string): A brief summary or snippet of the article content. If any field is missing or not found, omit that field in the output. Output a JSON array called results containing the extracted objects.
Split Extraction Results
Add a Split Out node. Set Field to Split Out to `output.results`, and in Options set Destination Field Name to `response`. This splits the JSON array into separate records for per-item incident creation. When run, you should see multiple independent items as output.
Create ServiceNow Security Incident
Add a Create an incident (ServiceNow) node. Configure the serviceNowBasicApi credential with basicAuth. Set Resource to incident and Operation to create. Set Short description to `=Ai Vulnerability {{ $json.response.title }}`; for Additional fields, use the following template for description. When run, a corresponding Security Incident should be created in ServiceNow.
Execution prompt · Source text。ServiceNow node additionalFields.description parameter
=Snippet {{ $json.response.content }} Creator {{ $json.response.creator }} PubDate {{ $json.response.pubDate}}Execution prompt · Source text。ServiceNow node short_description parameter
=Ai Vulnerability {{ $json.response.title }}Connect Nodes and Test
Connect nodes in this order: Schedule Trigger → RSS Read → Read URL content → Information Extractor → Split Out → Create an incident. Also connect OpenAI Chat Model to Information Extractor as ai_languageModel. In Settings, confirm executionOrder is v1. Save, run once manually, and verify that ServiceNow incidents are created correctly; activate the workflow after confirmation.
Prompt you can copy
Setup guidance · Editorial suggestion。Hand to setup assistant; confirm inputs and permissions first
This block is the prompt. Ads are never placed here.
You are reproducing an n8n workflow that auto-monitors an AI vulnerability RSS feed and creates ServiceNow security incidents. Follow this order: 1) Confirm you have an n8n instance and the three credentials openAiApi, serviceNowBasicApi, and jinaAiApi; 2) Import workflow.json or build manually; 3) Replace the RSS URL with a real vulnerability intelligence source; 4) Set the Schedule Trigger interval; 5) Test run and verify ServiceNow incident fields. Note: the default model is gpt-4.1-mini, and you can switch to gpt-4.1 or gpt-4.
Check credentials first, then import or build manually; replace the RSS URL with a production feed; run manually on first execution and verify outputs.
Source
Automate AI vulnerability monitoring with GPT-4 and ServiceNow incident creation · yajna · n8n.io · 2025-08-10
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.