Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Email Threat Analysis and Reporting

Email Threat Analysis and Reporting is a 19-node automation blueprint connecting Gmail, Microsoft Outlook, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailMicrosoft OutlookOpenAIJira

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

19

Nodes

19

Links

1

Run groups

Connected tools

4 integrations

  • Gmail
  • Microsoft Outlook
  • OpenAI
  • Jira

Canvas controls

Fit wide systems, then zoom into any run group.

Email Threat Analysis and Reporting execution lanes1 run groups containing 19 workflow nodes and 19 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTGmail TriggerGMAILGMAILTRIGGER0 IN / 1 OUTMicrosoft Outlook Trigger. trigger node, microsoftOutlookTrigger. 0 incoming and 1 outgoing connections.STARTMicrosoft Outlook TriggerTRIGGERMICROSOFTOUTLOOKTRIGGER0 IN / 1 OUTSet Gmail Variables. Gmail node, set. 1 incoming and 1 outgoing connections.STEP 02Set Gmail VariablesGMAILSET1 IN / 1 OUTRetrieve Headers of Email. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Retrieve Headers of EmailINTEGRATIONHTTPREQUEST1 IN / 1 OUTFormat Headers. transform node, code. 1 incoming and 1 outgoing connections.STEP 03Format HeadersTRANSFORMCODE1 IN / 1 OUTSet Outlook Variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set Outlook VariablesTRANSFORMSET1 IN / 1 OUTSet Email Variables. transform node, set. 2 incoming and 1 outgoing connections.STEP 05Set Email VariablesTRANSFORMSET2 IN / 1 OUTConvert Email Body to File. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 06Convert Email Body to FileINTEGRATIONCONVERTTOFILE1 IN / 1 OUTScreenshot HTML. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Screenshot HTMLINTEGRATIONHTTPREQUEST1 IN / 1 OUTRetrieve Screenshot. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Retrieve ScreenshotINTEGRATIONHTTPREQUEST1 IN / 1 OUTAnalyze Email with ChatGPT. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 09Analyze Email with ChatGPTOPENAIOPENAI1 IN / 1 OUTCheck if Malicious. decision node, if. 1 incoming and 2 outgoing connections.STEP 10Check if MaliciousDECISIONIF1 IN / 2 OUTCreate Potentially Malicious Ticket. integration node, jira. 1 incoming and 1 outgoing connections.STEP 11Create Potentially Malici…INTEGRATIONJIRA1 IN / 1 OUTCreate Potentially Benign Ticket. integration node, jira. 1 incoming and 1 outgoing connections.STEP 11Create Potentially Benign…INTEGRATIONJIRA1 IN / 1 OUTSet Jira ID. transform node, set. 2 incoming and 1 outgoing connections.STEP 12Set Jira IDTRANSFORMSET2 IN / 1 OUTRename Screenshot. transform node, code. 1 incoming and 1 outgoing connections.STEP 13Rename ScreenshotTRANSFORMCODE1 IN / 1 OUTUpload Screenshot of Email to Jira. integration node, jira. 1 incoming and 1 outgoing connections.STEP 14Upload Screenshot of Emai…INTEGRATIONJIRA1 IN / 1 OUTRename Email Body Screenshot. transform node, code. 1 incoming and 1 outgoing connections.STEP 15Rename Email Body Screens…TRANSFORMCODE1 IN / 1 OUTUpload Email Body to Jira. integration node, jira. 1 incoming and 0 outgoing connections.OUTCOMEUpload Email Body to JiraINTEGRATIONJIRA1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.19 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Gmail Trigger

19 Execution Links

  1. Start

    Gmail Trigger

    Trigger

    Microsoft Outlook Trigger

    Trigger

  2. Step 2

    Set Gmail Variables

    Transform

    Retrieve Headers of Email

    Integration

  3. Step 3

    Format Headers

    Transform

  4. Step 4

    Set Outlook Variables

    Transform

  5. Step 5

    Set Email Variables

    Transform

  6. Step 6

    Convert Email Body to File

    Integration

  7. Step 7

    Screenshot HTML

    Integration

  8. Step 8

    Retrieve Screenshot

    Integration

  9. Step 9

    Analyze Email with ChatGPT

    AI reasoning

  10. Step 10

    Check if Malicious

    Decision

  11. Step 11

    Create Potentially Malicious Ticket

    Integration

    Create Potentially Benign Ticket

    Integration

  12. Step 12

    Set Jira ID

    Transform

  13. Step 13

    Rename Screenshot

    Transform

  14. Step 14

    Upload Screenshot of Email to Jira

    Integration

  15. Step 15

    Rename Email Body Screenshot

    Transform

  16. Outcome

    Upload Email Body to Jira

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas