Skip to main content

Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts

Workflow preview

Workflow preview
100%
Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts preview
Open on n8n.io

Important notice

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

1. Workflow Overview

How It Works The automated blacklist monitor is designed to be a proactive, not reactive, tool. Here is the high level process: 1. Scheduled Checks : At regular intervals (e.g., every 30 minutes ...

Best for

  • SecOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.stickynote

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts
Workflow name
Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts

⚙ How It Works

The automated blacklist monitor is designed to be a proactive, not reactive, tool. Here is the high-level process:

  1. Scheduled Checks: At regular intervals (e.g., every 30 minutes or every hour), a monitoring script or service sends a request to a list of predefined DNS blacklists (DNSBLs) and real-time blackhole lists (RBLs).
  2. Lookup Queries: For each check, the system performs a lookup query for our specified domains and IP addresses against the various blacklists. It essentially asks, "Is our-ip-address.com on your list?"
  3. Status Evaluation: The blacklist service responds with a status: either the asset is clean or it is listed.
  4. Alerting Mechanism: If a new listing is detected, the system immediately triggers a notification. This alert contains key information like the asset that was blacklisted (domain or IP), the specific blacklist it was found on (e.g., Spamhaus), and the time of detection.
  5. Status Logging: The status of each asset (clean or listed) is logged in a central dashboard. This allows us to track the history of an IP or domain, see when a listing occurred, and when it was resolved.

Setup Steps

Follow these steps to set up the automated blacklist monitor.

  1. Select a Service: Choose a reliable blacklist monitoring service. Services like MXToolBox, HetrixTools, or Uptime Robot (with custom checks) are popular options.
  2. Create an Account: Sign up and create an account for your organization on the chosen platform.
  3. Add Monitored Assets: Navigate to the "Monitors" or "Assets" section within the service's dashboard. Add all of the following:
    • Your primary domain names (e.g., yourcompany.com).
    • All outbound mail server IP addresses.
    • Any other publicly facing IP addresses associated with your business.
  4. Configure Notification Channels: Set up how and where you want to receive alerts. The best practice is to configure multiple channels for redundancy:
    • Email: Send alerts to a group alias like [email protected] or [email protected].
    • Chat/IM: Integrate with a communication tool like Slack or Microsoft Teams and create a dedicated channel (e.g., #blacklist-alerts).
    • Ticketing System: Configure the service to automatically open a ticket in your help desk software (e.g., Jira, ServiceNow) when a new listing is found.
  5. Set Up Check Frequency: Configure how often you want the system to perform checks. A frequency of every 15 to 30 minutes is a good starting point for a high-priority service like email.
  6. Create a Runbook: A runbook is a document that outlines the steps to take when an alert is received. Create and share a runbook with your team that includes:
    • Confirmation: How to verify the listing.
    • Investigation: Initial steps to find the root cause (e.g., checking mail logs for spam).
    • Delisting: How to submit a delisting request to the specific blacklist provider.
  7. Initial Testing: Once everything is configured, perform a manual check to ensure the system is working and that all notification channels are active. You can often do this with a "test check" button within the monitoring service's dashboard.

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 - Scheduled Check

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - Define Domains/IPs

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

Block 3 - Query Blacklist API

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

Block 4 - Is on Blacklist?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 5 - Send High-Priority Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 6 - Sticky Note

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

Block 7 - Sticky Note1

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

3. Summary Table

Workflow Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts
Complexity intermediate
Nodes 7
Categories SecOps
Author Marth
Published 02 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6836/6836.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 Monitor domains & IPs on AbuseIPDB blacklist with Slack alerts do?

How It Works The automated blacklist monitor is designed to be a proactive, not reactive, tool. Here is the high level process: 1. Scheduled Checks : At regular intervals (e.g., every 30 minutes ...

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