HumationHuman + Automation
Back to Catalog

CYBERPULSE AI RedOps: validate email security gateways generated payloads

Adnan TariqAdnan Tariq
53 views
2/3/2026
File ManagementCloud StorageGoogle DrivePDF ExportOneDrive
Official Page

Description: Automatically send structured benign payloads (PDF/HTML/JS markers) to test email gateways and sandbox response. AI-generated phishing-style content helps simulate real-world threats without malicious intent. Results logged in Google Sheets.

Whoโ€™s It For:

Security teams validating email filters and sandboxes

Red Teams doing payload simulation

GRC/compliance teams testing Secure Email Gateway (SEG) controls

How It Works:

Loads target list from Google Sheets

Crafts payload using OpenAI prompt logic

Sends emails with embedded controlled markers

Logs responses back to the same sheet

Requirements:

Google Sheet Requirements

  • Sheet Name: Payload_Validation_Log
  • Required Columns:
    • payload
    • status
    • response
    • timestamp

Gmail/SMTP or email-sending node

Google Sheets credential

OpenAI API Key

File Templates:

RedOps_PayloadValidator_Log_Template.xlsx โ€“ track targets, payload, status

How to Customize:

Modify the OpenAI prompt for alternate payload types

Adjust fields or webhook triggers

Add logging to SIEM or ticketing platforms

This module is part of the CYBERPULSE AI RedOps Suite

๐ŸŒ https://cyberpulsesolutions.com

Detailed README:

Purpose

Simulate benign payloads (e.g., links, encoded HTML) to test how your email security gateway and sandbox environment responds.

How It Works

  1. Trigger Test Batch
    Starts manually or on schedule.

  2. Get Targets
    Loads email recipients from Google Sheets.

  3. Generate Payload
    Prepares static payload like a fake link.

  4. OpenAI Node
    Generates a realistic simulation email using the payload.

  5. Merge + Format
    Combines recipient info with OpenAI output, formats the message, and tags it as simulated.

  6. Validated Node
    Appends results to Google Sheets with fields like:

    • email, payload, response, status, module, time

Google Sheets Requirements

  • Sheet Name: RedOps_Targets
  • Columns: email, name, team, payload, status, response, module, time

Security Note

This workflow uses simulated payloads and never sends real malicious content. No real user data is stored or transmitted. Meant for internal Red Team and security validation use only.

n8n Workflow: Email Security Gateway Validation with AI-Generated Payloads

This n8n workflow provides a framework for validating email security gateways using AI-generated payloads. It aims to simulate real-world threats by generating and processing various email content, then merging the results for analysis.

What it does

This workflow automates the following steps:

  1. Manual Trigger: Initiates the workflow manually, allowing for on-demand testing.
  2. Edit Fields (Set): Prepares the input data by setting or modifying fields, likely for the AI payload generation.
  3. OpenAI: Utilizes the OpenAI API to generate email security payloads. This could involve crafting malicious email content, phishing attempts, or other simulated threats.
  4. Google Sheets: Processes the generated payloads or their results, potentially logging them or retrieving additional data from a Google Sheet.
  5. Merge: Combines the outputs from the OpenAI and Google Sheets nodes, allowing for a consolidated view of the generated payloads and any associated data.
  6. Sticky Note: Provides a visual annotation within the workflow, likely for documentation or instructions.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: An API key for OpenAI to generate the AI payloads.
  • Google Sheets Account: Access to a Google Sheets account, with appropriate credentials configured in n8n, to interact with spreadsheets.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI credentials in n8n.
    • Set up your Google Sheets credentials in n8n.
  3. Adjust Nodes (if necessary):
    • Modify the Edit Fields (Set) node to define the input parameters for your AI payload generation (e.g., types of threats, keywords, target personas).
    • Configure the OpenAI node with the specific model and prompt engineering required for your payload generation.
    • Adjust the Google Sheets node to point to your desired spreadsheet and specify the operations (e.g., read, write, append) you want to perform.
  4. Execute the workflow: Click the "Execute workflow" button on the Manual Trigger node to run the workflow.

This workflow provides a powerful starting point for red team operations and security validation, allowing for dynamic and intelligent payload generation to test email security defenses.

Related Templates

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. โš™๏ธ Workflow Logic Manual Trigger โ€” Starts the workflow manually. List Video Files โ€” Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/ๅ•่ฏๅก/A1-A2). Sort and Generate Items โ€” Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) โ€” Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each videoโ€™s scheduled time by order ร— 12 hours. Converts JST back to UTC for YouTubeโ€™s publishAt field. Split in Batches (1 per video) โ€” Iterates over each video item. Read Video File โ€” Loads the corresponding video from disk. Upload to YouTube (Scheduled) โ€” Uploads the video privately with the computed publishAtUtc. Add to Playlist โ€” Adds the newly uploaded video to the target playlist. ๐Ÿ•’ Highlights Timezone-safe: Pure UTC โ†” JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. ๐Ÿ’ก Typical Use Cases Multi-part educational video series (e.g., A1โ€“A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226

Detect holiday conflicts & suggest meeting reschedules with Google Calendar and Slack

Whoโ€™s it for Remote and distributed teams that schedule across time zones and want to avoid meetings landing on public holidaysโ€”PMs, CS/AM teams, and ops leads who own cross-regional calendars. What it does / How it works The workflow checks next weekโ€™s Google Calendar events, compares event dates against public holidays for selected country codes, and produces a single Slack digest with any conflicts plus suggested alternative dates. Core steps: Workflow Configuration (Set) โ†’ Fetch Public Holidays (via a public holiday API such as Calendarific/Nager.Date) โ†’ Get Next Week Calendar Events (Google Calendar) โ†’ Detect Holiday Conflicts (compare dates) โ†’ Generate Reschedule Suggestions (find nearest business day that isnโ€™t a holiday/weekend) โ†’ Format Slack Digest โ†’ Post Slack Digest. How to set up Open Workflow Configuration (Set) and edit: countryCodes, calendarId, slackChannel, nextWeekStart, nextWeekEnd. Connect your own Google Calendar and Slack credentials in n8n (no hardcoded keys). (Optional) Adjust the Trigger to run daily or only on Mondays. Requirements n8n (Cloud or self-hosted) Google Calendar read access to the target calendar Slack app with permission to post to the chosen channel A public-holiday API (no secrets needed for Nager.Date; Calendarific requires an API key) How to customize the workflow Time window: Change nextWeekStart/End to scan a different period. Holiday sources: Add or swap APIs; merge multiple regions. Suggestion logic: Tweak the look-ahead window or rules (e.g., skip Fridays). Output: Post per-calendar messages, DM owners, or create tentative reschedule events automatically.

Takuya OjimaBy Takuya Ojima
70

Generate event speaker recommendations with Claude AI and Google Sheets

Simplify event planning with this automated n8n workflow. Triggered by incoming requests, it fetches speaker and audience data from Google Sheets, analyzes profiles and preferences, and generates optimized session recommendations. The workflow delivers formatted voice responses and updates tracking data, ensuring organizers receive real-time, tailored suggestions. ๐ŸŽ™๏ธ๐Ÿ“Š Key Features Real-time analysis of speaker and audience data for personalized recommendations. Generates optimized session lineups based on profiles and preferences. Delivers responses via voice agent for a seamless experience. Logs maintain a detailed recommendation history in Google Sheets. Workflow Process The Webhook Trigger node initiates the workflow upon receiving voice agent or external system requests. Parse Voice Request processes incoming voice data into actionable parameters. Fetch Database retrieves speaker ratings, past sessions, and audience ratings from Google Sheets. Calculate & Analyze combines voice request data with speaker profiles and audience insights for comprehensive matching. AI Optimization Engine analyzes speaker-audience fit and recommends optimal session lineups. Format Recommendations structures the recommendations for voice agent response. Voice Agent Response returns formatted recommendations to the user with natural language summary and structured data. Update Tracking Sheet saves recommendation history and analytics to Google Sheets. If errors occur, the Check for Errors node branches to: Format Error Response prepares an error message. Send Error Response delivers the error notification. Setup Instructions Import the workflow into n8n and configure Google Sheets OAuth2 for data access. Set up the Webhook Trigger with your voice agent or external system's API credentials. Configure the AI Optimization Engine node with a suitable language model (e.g., Anthropic Chat Model). Test the workflow by sending sample voice requests and verifying recommendations. Adjust analysis parameters as needed for specific event requirements. Prerequisites Google Sheets OAuth2 credentials Voice agent API or integration service AI/LLM service for optimization (e.g., Anthropic) Structured speaker and audience data in a Google Sheet Google Sheet Structure: Create a sheet with columns: Speaker Name Rating Past Sessions Audience Rating Preferences Updated At Modification Options Customize the Calculate & Analyze node to include additional matching criteria (e.g., topic expertise). Adjust the AI Optimization Engine to prioritize specific session formats or durations. Modify voice response templates in the Voice Agent Response node with branded phrasing. Integrate with event management tools (e.g., Eventbrite) for live data feeds. Set custom error handling rules in the Check for Errors node. Discover more workflows โ€“ Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
116