Skip to main content

CYBERPULSE AI redOps: phishing simulation with redirect tracking

Workflow preview

Workflow preview
100%
CYBERPULSE AI redOps: phishing simulation with redirect tracking preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Description: Simulate cloaked phishing links that redirect through a controlled proxy. This module tracks if secure email gateways (SEGs) or sandboxes trigger the redirect before users do. Logs acc...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.set

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
CYBERPULSE AI redOps: phishing simulation with redirect tracking
Workflow name
CYBERPULSE AI redOps: phishing simulation with redirect tracking

## Description: Simulate cloaked phishing links that redirect through a controlled proxy. This module tracks if secure email gateways (SEGs) or sandboxes trigger the redirect before users do. Logs access, response, and timestamps in Google Sheets.

Who’s It For:

Red Teams simulating real-world phishing redirects

Security teams testing gateway/sandbox behavior

Awareness teams tracking click-throughs

How It Works:

Loads target list from Google Sheets

Generates dynamic redirect links per target

Emails the links using Gmail or SMTP

Simulates access via webhook or internal call

Logs metadata and redirect access to Sheets

Requirements:

Google Sheet Requirements

  • Sheet Name: Redirect_Logs
  • Required Columns: name, team, email, module, status, payload, response, timestamp

Google Sheets credentials

Email service (Gmail, SMTP, or custom node)

Optional: Real endpoint for link redirection (e.g., Vercel Function, 托管平台 Worker)

Setup Instructions

  1. Clone or copy the provided Google Sheet template (linked below).
  2. Set up the webhook trigger in the Redirect Proxy node.
  3. Use URL shortener node (optional) to obfuscate redirect links.
  4. Connect Google Sheets node and map fields: timestamp, IP, user-agent, original URL.
  5. Configure redirection logic using IF and Set nodes.
  6. Run a test redirect to validate Google Sheet logging.

File Templates:

RedOps_RedirectCloak_Log_Template.xlsx

email name team payload response status module timestamp [email protected] John Doe IT redirect.link/... Redirect triggered Simulated RedirectCloak 2025-07-27T12:00:00Z

Customization

  • Redirect Logic: Modify the HTTP Response or Set node to redirect to real servers or simulation targets.
  • Tracking Format: Adjust the structure of the logged data — include fields like user-agent, referrer, campaign ID, etc.
  • Redirection Endpoint: Host the redirection logic on a public API gateway (e.g., AWS API Gateway, Vercel Edge Function) if deploying outside of n8n.
  • Obfuscation: Integrate a URL shortener (like Bitly) or a custom domain to hide the true destination during simulations.

Ethics Note:

This module is intended for internal simulations only and does not contain malicious payloads. Always use with authorization and red team awareness protocols.

🔗 Part of the CYBERPULSE AI RedOps Suite 🌐 https://cyberpulsesolutions.com 📧 [email protected]

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 - Sticky Note

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

Block 2 - ⚡ Trigger RedirectCloak

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

Block 3 - Google Sheets

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 4 - 🔗 Generate Redirect Link

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - 🛰️ Simulate Redirect Hit

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - Sticky Note1

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

Block 7 - 📄 Append Redirect Logs

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 8 - Sticky Note2

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

Block 9 - Sticky Note3

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

3. Summary Table

Workflow CYBERPULSE AI redOps: phishing simulation with redirect tracking
Complexity intermediate
Nodes 9
Categories SecOps
Author Adnan Tariq
Published 27 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6509/6509.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 CYBERPULSE AI redOps: phishing simulation with redirect tracking do?

Description: Simulate cloaked phishing links that redirect through a controlled proxy. This module tracks if secure email gateways (SEGs) or sandboxes trigger the redirect before users do. Logs acc...

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.