Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Outlook Draft Creation with Attachment

Outlook Draft Creation with Attachment is a 5-node automation blueprint connecting Microsoft Outlook, Custom API via HTTP Request. Inspect its trigger, execution graph, branches, and implementation requirements.

Microsoft OutlookCustom API via HTTP Request

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.

5

Nodes

4

Links

1

Run groups

Connected tools

2 integrations

  • Microsoft Outlook
  • Custom API via HTTP Request

Canvas controls

Fit wide systems, then zoom into any run group.

Outlook Draft Creation with Attachment execution lanes1 run groups containing 5 workflow nodes and 4 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.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTMicrosoft Outlook. integration node, microsoftOutlook. 1 incoming and 1 outgoing connections.STEP 02Microsoft OutlookINTEGRATIONMICROSOFTOUTLOOK1 IN / 1 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUTMicrosoft Outlook1. integration node, microsoftOutlook. 1 incoming and 1 outgoing connections.STEP 04Microsoft Outlook1INTEGRATIONMICROSOFTOUTLOOK1 IN / 1 OUTMicrosoft Outlook2. integration node, microsoftOutlook. 1 incoming and 0 outgoing connections.OUTCOMEMicrosoft Outlook2INTEGRATIONMICROSOFTOUTLOOK1 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.5 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

On clicking 'execute'

4 Execution Links

  1. Start

    On clicking 'execute'

    Trigger

  2. Step 2

    Microsoft Outlook

    Integration

  3. Step 3

    HTTP Request

    Integration

  4. Step 4

    Microsoft Outlook1

    Integration

  5. Outcome

    Microsoft Outlook2

    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