klbr/n8nworkflows.xyz
1
0
Fork 0
mirror of https://github.com/khoaliber/n8nworkflows.xyz.git synced 2026-04-28 00:29:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

creation

Browse Source
This commit is contained in:
nusquama
2025-11-12 13:23:51 +01:00
parent 8f4d479659
commit 593ebd88e7
1 changed files with 230 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
workflows/Validate Email Security Gateways with GPT-4 Generated Payloads and Google Sheets-6507/readme-6507.md
+230
View File
@@ -0,0 +1,230 @@
Validate Email Security Gateways with GPT-4 Generated Payloads and Google Sheets
https://n8nworkflows.xyz/workflows/validate-email-security-gateways-with-gpt-4-generated-payloads-and-google-sheets-6507
# Validate Email Security Gateways with GPT-4 Generated Payloads and Google Sheets
### 1. Workflow Overview
This workflow, titled **"Validate Email Security Gateways with GPT-4 Generated Payloads and Google Sheets"**, automates the process of testing and validating email security gateways by generating targeted payloads using GPT-4 through OpenAI and logging results in Google Sheets. It is designed for security operations (RedOps) teams aiming to verify the effectiveness of email filtering systems with dynamically created test payloads.
The workflow is logically organized into these main blocks:
- **1.1 Input Reception:** Manual trigger initiates the batch test and retrieves target data from Google Sheets.
- **1.2 Payload Generation:** Constructs payloads via a Set node and then uses OpenAI GPT-4 to generate payload content.
- **1.3 Data Assembly:** Post-processes OpenAI output, adds email context, and merges payload and email data.
- **1.4 Result Logging:** Edits fields as needed and logs validated payloads back into Google Sheets.
---
### 2. Block-by-Block Analysis
#### 2.1 Input Reception
**Overview:**
This block starts the workflow manually and pulls target data, presumably email targets or gateway parameters, from a Google Sheets document.
**Nodes Involved:**
- ▶️ Trigger Test Batch
- 📥 Get Targets
**Node Details:**
- **▶️ Trigger Test Batch**
- Type: Manual Trigger
- Role: Initiates the workflow on demand.
- Configuration: No parameters set; used to start the batch process manually.
- Input: None
- Output: Triggers the next node to retrieve data.
- Edge Cases: None typical; manual trigger relies on user action.
- **📥 Get Targets**
- Type: Google Sheets
- Role: Retrieves a list of targets from a configured Google Sheet.
- Configuration: Connected to a Google Sheets credential; reads rows containing target data.
- Key Variables: Output is a list of rows representing targets.
- Input: Trigger node output
- Output: Data passed to payload generation.
- Edge Cases: Authentication errors (expired OAuth tokens), empty or malformed sheet data, API rate limits.
---
#### 2.2 Payload Generation
**Overview:**
Creates the payload data structure and sends it to OpenAI to generate test payloads based on GPT-4.
**Nodes Involved:**
- 🧪 Generate Payload
- OpenAI
**Node Details:**
- **🧪 Generate Payload**
- Type: Set
- Role: Prepares the payload data (e.g., template, parameters) before sending it to OpenAI.
- Configuration: Likely sets static or dynamic fields required for the GPT-4 prompt.
- Input: Target data from Google Sheets
- Output: Two outputs: one continues to OpenAI, the other to merge node.
- Edge Cases: Expression failures if referencing non-existent variables, missing data fields.
- **OpenAI**
- Type: OpenAI (LangChain integration)
- Role: Uses GPT-4 to generate payload content based on input parameters.
- Configuration: Requires OpenAI API credentials, prompt template set in parameters.
- Input: Payload data from "Generate Payload"
- Output: Generated payload text/data forwarded to next block.
- Edge Cases: API quota limits, network timeouts, invalid prompt errors, auth failures.
---
#### 2.3 Data Assembly
**Overview:**
This block processes the generated payload, adds email information, and merges all relevant data for logging.
**Nodes Involved:**
- Add Email
- Merge
**Node Details:**
- **Add Email**
- Type: Set
- Role: Adds or modifies email-related fields to the data object, possibly for tracking or logging.
- Configuration: Sets email addresses or metadata fields.
- Input: Output from OpenAI node
- Output: Passes enriched data to Merge node.
- Edge Cases: Missing email fields, improper formatting.
- **Merge**
- Type: Merge
- Role: Combines data from two sources: generated payload and email data.
- Configuration: Likely uses “Merge by index” or “Wait” mode to synchronize data.
- Input: Two inputs — one from Generate Payload (original data) and one from Add Email (enhanced data)
- Output: Combined dataset forwarded to Edit Fields
- Edge Cases: Mismatched array lengths, timing issues causing data misalignment.
---
#### 2.4 Result Logging
**Overview:**
Finalizes the data structure by editing fields and writing validated payload data back into a Google Sheet for record-keeping.
**Nodes Involved:**
- Edit Fields
- Validated
**Node Details:**
- **Edit Fields**
- Type: Set
- Role: Adjusts or formats fields as needed before logging, e.g., cleaning data, renaming keys.
- Configuration: Sets or modifies specific fields, possibly for clarity or compliance with sheet schema.
- Input: Merged data
- Output: Data ready for persistence
- Edge Cases: Incorrect field names, missing fields.
- **Validated**
- Type: Google Sheets
- Role: Writes the validated and processed payload data into a Google Sheet.
- Configuration: Connected to Google Sheets credentials; appends or updates rows.
- Input: Edited data from Edit Fields
- Output: None (terminal node)
- Edge Cases: API rate limits, authentication issues, write conflicts.
---
### 3. Summary Table
| Node Name | Node Type | Functional Role | Input Node(s) | Output Node(s) | Sticky Note |
|---------------------|--------------------------------|------------------------------------|--------------------------|-----------------------|-------------|
| ▶️ Trigger Test Batch | Manual Trigger | Starts the workflow manually | None | 📥 Get Targets | |
| 📥 Get Targets | Google Sheets | Retrieves target data | ▶️ Trigger Test Batch | 🧪 Generate Payload | |
| 🧪 Generate Payload | Set | Prepares payload for GPT-4 prompt | 📥 Get Targets | OpenAI, Merge | |
| OpenAI | OpenAI (LangChain) | Generates GPT-4 payload content | 🧪 Generate Payload | Add Email | |
| Add Email | Set | Adds email-related data | OpenAI | Merge | |
| Merge | Merge | Combines payload and email data | 🧪 Generate Payload, Add Email | Edit Fields | |
| Edit Fields | Set | Edits and formats final data | Merge | Validated | |
| Validated | Google Sheets | Logs validated payloads | Edit Fields | None | |
| Sticky Note | Sticky Note | (Empty content) | None | None | |
---
### 4. Reproducing the Workflow from Scratch
1. **Create Manual Trigger Node**
- Node Type: Manual Trigger
- Name: "▶️ Trigger Test Batch"
- No parameters needed. Connect output to next node.
2. **Add Google Sheets Node to Retrieve Targets**
- Node Type: Google Sheets (Read rows)
- Name: "📥 Get Targets"
- Configure Google Sheets credentials.
- Set Spreadsheet ID and Sheet name to your target data sheet.
- Connect input from "▶️ Trigger Test Batch".
3. **Add Set Node to Generate Payload**
- Node Type: Set
- Name: "🧪 Generate Payload"
- Configure fields to define payload template and parameters for GPT-4 prompt, e.g., type, context, etc.
- Connect input from "📥 Get Targets".
- Set two outputs: one to OpenAI node, one to Merge node.
4. **Add OpenAI Node (LangChain integration)**
- Node Type: OpenAI
- Name: "OpenAI"
- Configure OpenAI credentials (API key with GPT-4 access).
- Set prompt with payload data from previous node.
- Connect input from first output of "🧪 Generate Payload".
- Output connects to "Add Email".
5. **Add Set Node to Add Email Data**
- Node Type: Set
- Name: "Add Email"
- Configure to add or modify fields related to email addresses or metadata.
- Connect input from "OpenAI".
- Output connects to second input of "Merge".
6. **Add Merge Node**
- Node Type: Merge
- Name: "Merge"
- Configure merge mode (e.g., merge by index or wait for all inputs).
- Connect first input from second output of "🧪 Generate Payload".
- Connect second input from "Add Email".
- Output connects to "Edit Fields".
7. **Add Set Node to Edit Fields**
- Node Type: Set
- Name: "Edit Fields"
- Configure to adjust field names, clean or reformat data as necessary for Google Sheets schema.
- Connect input from "Merge".
- Output connects to "Validated".
8. **Add Google Sheets Node to Log Validated Data**
- Node Type: Google Sheets (Append or Update rows)
- Name: "Validated"
- Configure Google Sheets credentials.
- Set Spreadsheet ID and Sheet name for logging results.
- Connect input from "Edit Fields".
9. **Optional: Add Sticky Note**
- Add a sticky note for documentation or comments, positioned visually near relevant nodes.
---
### 5. General Notes & Resources
| Note Content | Context or Link |
|------------------------------------------------------------------------------|-------------------------------------|
| This workflow leverages GPT-4 via OpenAI’s API through n8n's LangChain node. | OpenAI API documentation: https://platform.openai.com/docs |
| Google Sheets OAuth2 credentials must be correctly configured and authorized.| n8n Google Sheets node documentation: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/ |
| Ensure API quota and rate limits are monitored to avoid workflow failures. | OpenAI API rate limits: https://platform.openai.com/docs/guides/rate-limits |
| Workflow designed for RedOps teams to validate email security gateways using AI-generated test payloads. | Internal use case focus. |
---
_Disclaimer: The provided description and nodes come solely from an automated n8n workflow. The workflow respects all content policies and handles only legal, public data._