Track software vulnerability patents with ScrapeGraphAI, Matrix, and Intercom
Software Vulnerability Patent Tracker
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template.
This workflow automatically tracks newly-published patent filings that mention software-security vulnerabilities, buffer-overflow mitigation techniques, and related technology keywords. Every week it aggregates fresh patent data from USPTO and international patent databases, filters it by relevance, and delivers a concise JSON digest (and optional Intercom notification) to R&D teams and patent attorneys.
Pre-conditions/Requirements
Prerequisites
- n8n instance (self-hosted or n8n cloud, v1.7.0+)
- ScrapeGraphAI community node installed
- Basic understanding of patent search syntax (for customizing keyword sets)
- Optional: Intercom account for in-app alerts
Required Credentials
| Credential | Purpose | |------------|---------| | ScrapeGraphAI API Key | Enables ScrapeGraphAI nodes to fetch and parse patent-office webpages | | Intercom Access Token (optional) | Sends weekly digests directly to an Intercom workspace |
Additional Setup Requirements
| Setting | Recommended Value | Notes |
|---------|-------------------|-------|
| Cron schedule | 0 9 * * 1 | Triggers every Monday at 09:00 server time |
| Patent keyword matrix | See example CSV below | List of comma-separated keywords per tech focus |
Example keyword matrix (upload as keywords.csv or paste into the “Matrix” node):
topic,keywords
Buffer Overflow,"buffer overflow, stack smashing, stack buffer"
Memory Safety,"memory safety, safe memory allocation, pointer sanitization"
Code Injection,"SQL injection, command injection, injection prevention"
How it works
This workflow automatically tracks newly-published patent filings that mention software-security vulnerabilities, buffer-overflow mitigation techniques, and related technology keywords. Every week it aggregates fresh patent data from USPTO and international patent databases, filters it by relevance, and delivers a concise JSON digest (and optional Intercom notification) to R&D teams and patent attorneys.
Key Steps:
- Schedule Trigger: Fires weekly based on the configured cron expression.
- Matrix (Keyword Loader): Loads the CSV-based technology keyword matrix into memory.
- Code (Build Search Queries): Dynamically assembles patent-search URLs for each keyword group.
- ScrapeGraphAI (Fetch Results): Scrapes USPTO, EPO, and WIPO result pages and parses titles, abstracts, publication numbers, and dates.
- If (Relevance Filter): Removes patents older than 1 year or without vulnerability-related terms in the abstract.
- Set (Normalize JSON): Formats the remaining records into a uniform JSON schema.
- Intercom (Notify Team): Sends a summarized digest to your chosen Intercom workspace.
(Skip or disable this node if you prefer to consume the raw JSON output instead.) - Sticky Notes: Contain inline documentation and customization tips for future editors.
Set up steps
Setup Time: 10-15 minutes
- Install Community Node
Navigate to “Settings → Community Nodes”, search for ScrapeGraphAI, and click “Install”. - Create Credentials
- Go to “Credentials” → “New Credential” → select ScrapeGraphAI API → paste your API key.
- (Optional) Add an Intercom credential with a valid access token.
- Import the Workflow
- Click “Import” → “Workflow JSON” and paste the template JSON, or drag-and-drop the
.jsonfile.
- Click “Import” → “Workflow JSON” and paste the template JSON, or drag-and-drop the
- Configure Schedule
Open the Schedule Trigger node and adjust the cron expression if a different frequency is required. - Upload / Edit Keyword Matrix
Open the Matrix node, paste your custom CSV, or modify existing topics & keywords. - Review Search Logic
In the Code (Build Search Queries) node, review the base URLs and adjust patent databases as needed. - Define Notification Channel
If using Intercom, select your Intercom credential in the Intercom node and choose the target channel. - Execute & Activate
Click “Execute Workflow” for a trial run. Verify the output. If satisfied, switch the workflow to “Active”.
Node Descriptions
Core Workflow Nodes:
- Schedule Trigger – Initiates the workflow on a weekly cron schedule.
- Matrix – Holds the CSV keyword table and makes each row available as an item.
- Code (Build Search Queries) – Generates search URLs and attaches meta-data for later nodes.
- ScrapeGraphAI – Scrapes patent listings and extracts structured fields (title, abstract, pub. date, link).
- If (Relevance Filter) – Applies date and keyword relevance filters.
- Set (Normalize JSON) – Maps scraped fields into a clean JSON schema for downstream use.
- Intercom – Sends formatted patent summaries to an Intercom inbox or channel.
- Sticky Notes – Provide inline documentation and edit history markers.
Data Flow:
- Schedule Trigger → Matrix → Code → ScrapeGraphAI → If → Set → Intercom
Customization Examples
Change Data Source to Google Patents
// In the Code node
const base = 'https://patents.google.com/?q=';
items.forEach(item => {
item.json.searchUrl = `${base}${encodeURIComponent(item.json.keywords)}&oq=${encodeURIComponent(item.json.keywords)}`;
});
return items;
Send Digest via Slack Instead of Intercom
// Replace Intercom node with Slack node
{
"text": `🚀 New Vulnerability-related Patents (${items.length})\n` +
items.map(i => `• <${i.json.link}|${i.json.title}>`).join('\n')
}
Data Output Format
The workflow outputs structured JSON data:
{
"topic": "Memory Safety",
"keywords": "memory safety, safe memory allocation, pointer sanitization",
"title": "Memory protection for compiled binary code",
"publicationNumber": "US20240123456A1",
"publicationDate": "2024-03-21",
"abstract": "Techniques for enforcing memory safety in compiled software...",
"link": "https://patents.google.com/patent/US20240123456A1/en",
"source": "USPTO"
}
Troubleshooting
Common Issues
- Empty Result Set – Ensure that the keywords are specific but not overly narrow; test queries manually on USPTO.
- ScrapeGraphAI Timeouts – Increase the
timeoutparameter in the ScrapeGraphAI node or reduce concurrent requests.
Performance Tips
- Limit the keyword matrix to <50 rows to keep weekly runs under 2 minutes.
- Schedule the workflow during off-peak hours to reduce load on patent-office servers.
Pro Tips:
- Combine this workflow with a vector database (e.g., Pinecone) to create a semantic patent knowledge base.
- Add a “Merge” node to correlate new patents with existing vulnerability CVE entries.
- Use a second ScrapeGraphAI node to crawl citation trees and identify emerging technology clusters.
n8n Workflow: Track Software Vulnerability Patents with ScrapeGraphAI, Matrix, and Intercom
This n8n workflow is designed to monitor and report on software vulnerability patents. It acts as a scheduled system that periodically checks for new information and, based on a condition, routes that information to different communication channels: Matrix and Intercom.
What it does
This workflow automates the following steps:
- Triggers on a Schedule: The workflow starts automatically based on a predefined schedule.
- Executes Custom Code: It runs a custom JavaScript code snippet. While the specific code isn't provided in the JSON, this node is typically used to fetch data (e.g., from an API like ScrapeGraphAI, mentioned in the directory name), process it, or prepare it for subsequent steps.
- Applies Conditional Logic: It evaluates the data processed by the custom code using an "If" condition. This likely checks for specific criteria, such as the presence of new vulnerabilities or patents.
- Routes to Intercom (if True): If the condition evaluates to
true, the workflow sends a message or creates an event in Intercom. This could be used to alert sales, support, or product teams about relevant findings. - Routes to Matrix (if False): If the condition evaluates to
false, the workflow sends a message to a Matrix room. This might be used for internal team notifications, logging, or for cases where the information is less critical or requires different handling than the "true" branch. - Annotates with Sticky Note: A sticky note is included in the workflow, likely for documentation purposes, to provide context or instructions within the n8n canvas itself.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Intercom Account: Configured with appropriate credentials in n8n to send messages or create events.
- Matrix Account: Configured with appropriate credentials in n8n to send messages to a Matrix room.
- Custom Code Logic: The JavaScript code within the "Code" node needs to be defined to perform the actual data fetching and processing (e.g., integrating with ScrapeGraphAI or other data sources).
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Intercom credentials in n8n.
- Set up your Matrix credentials in n8n.
- Customize Code Node: Open the "Code" node and insert your JavaScript logic to fetch and process the software vulnerability patent data. This is where you would integrate with tools like ScrapeGraphAI.
- Configure If Node: Adjust the conditions in the "If" node to match your criteria for routing data to Intercom or Matrix.
- Configure Schedule Trigger: Define the desired schedule for how often the workflow should run (e.g., daily, weekly).
- Activate the Workflow: Once configured, activate the workflow to start monitoring and reporting.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.