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

Automated Flight Deal Notifier

Automated Flight Deal Notifier is a 11-node automation blueprint connecting Gmail, Amadeus API. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailAmadeus API

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.

11

Nodes

10

Links

2

Run groups

Connected tools

2 integrations

  • Gmail
  • Amadeus API

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Flight Deal Notifier execution lanes2 run groups containing 11 workflow nodes and 10 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTFromTo. transform node, set. 1 incoming and 1 outgoing connections.STEP 02FromToTRANSFORMSET1 IN / 1 OUTCarrierNameLookup. transform node, code. 1 incoming and 1 outgoing connections.STEP 03CarrierNameLookupTRANSFORMCODE1 IN / 1 OUTGet Dates. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Get DatesTRANSFORMCODE1 IN / 1 OUTWait. integration node, wait. 1 incoming and 1 outgoing connections.STEP 05WaitINTEGRATIONWAIT1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 06Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTAmadeus Flight Search. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Amadeus Flight SearchINTEGRATIONHTTPREQUEST1 IN / 1 OUTMerge & Extract. transform node, code. 1 incoming and 1 outgoing connections.STEP 08Merge & ExtractTRANSFORMCODE1 IN / 1 OUTUnder Price. decision node, filter. 1 incoming and 1 outgoing connections.STEP 09Under PriceDECISIONFILTER1 IN / 1 OUTGmail. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMEGmailGMAILGMAIL1 IN / 0 OUTGet Carrier Codes. integration node, httpRequest. 0 incoming and 0 outgoing connections.CORE RUNTIMEGet Carrier CodesINTEGRATIONHTTPREQUEST0 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.11 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

Schedule Trigger

10 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    FromTo

    Transform

  3. Step 3

    CarrierNameLookup

    Transform

  4. Step 4

    Get Dates

    Transform

  5. Step 5

    Wait

    Integration

  6. Step 6

    Loop Over Items

    Integration

  7. Step 7

    Amadeus Flight Search

    Integration

  8. Step 8

    Merge & Extract

    Transform

  9. Step 9

    Under Price

    Decision

  10. Outcome

    Gmail

    Integration

02

Run Group

Get Carrier Codes

0 Execution Links

  1. Core Runtime

    Get Carrier Codes

    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