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

Meraki Network Monitoring & Alert Workflow

Meraki Network Monitoring & Alert Workflow is a 16-node automation blueprint connecting Cisco Meraki API, Microsoft Teams, Redis. Inspect its trigger, execution graph, branches, and implementation requirements.

Cisco Meraki APIMicrosoft TeamsRedis

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.

16

Nodes

17

Links

1

Run groups

Connected tools

3 integrations

  • Cisco Meraki API
  • Microsoft Teams
  • Redis

Canvas controls

Fit wide systems, then zoom into any run group.

Meraki Network Monitoring & Alert Workflow execution lanes1 run groups containing 16 workflow nodes and 17 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 OUTWhen clicking "Execute Workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Execute Wo…TRIGGERMANUALTRIGGER0 IN / 1 OUTGet Meraki Organizations. integration node, httpRequest. 2 incoming and 2 outgoing connections.STEP 02Get Meraki OrganizationsINTEGRATIONHTTPREQUEST2 IN / 2 OUTGet Org Name & ID. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Get Org Name & IDTRANSFORMSET1 IN / 1 OUTGet Uplink Loss and Latency. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get Uplink Loss and LatencyINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet Network IDs. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get Network IDsINTEGRATIONHTTPREQUEST1 IN / 1 OUTSets Network Variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Sets Network VariablesTRANSFORMSET1 IN / 1 OUTCombine latency to its respective Network. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06Combine latency to its re…DECISIONMERGE2 IN / 1 OUTMakes Latency and Loss Filterable. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Makes Latency and Loss Fi…TRANSFORMSET1 IN / 1 OUTAverage Latency & Loss over 5m. transform node, code. 1 incoming and 1 outgoing connections.STEP 08Average Latency & Loss ov…TRANSFORMCODE1 IN / 1 OUTFilters Problematic sites. transform node, code. 1 incoming and 2 outgoing connections.STEP 09Filters Problematic sitesTRANSFORMCODE1 IN / 2 OUTCheck if Alert Exists. integration node, redis. 1 incoming and 1 outgoing connections.STEP 10Check if Alert ExistsINTEGRATIONREDIS1 IN / 1 OUTCreate Response. transform node, code. 1 incoming and 1 outgoing connections.STEP 11Create ResponseTRANSFORMCODE1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 12MergeDECISIONMERGE2 IN / 1 OUTMessage Techs. integration node, microsoftTeams. 1 incoming and 1 outgoing connections.STEP 13Message TechsINTEGRATIONMICROSOFTTEAMS1 IN / 1 OUTLog the Alert. integration node, redis. 1 incoming and 0 outgoing connections.OUTCOMELog the AlertINTEGRATIONREDIS1 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.16 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

17 Execution Links

  1. Start

    Schedule Trigger

    Trigger

    When clicking "Execute Workflow"

    Trigger

  2. Step 2

    Get Meraki Organizations

    Integration

  3. Step 3

    Get Org Name & ID

    Transform

    Get Uplink Loss and Latency

    Integration

  4. Step 4

    Get Network IDs

    Integration

  5. Step 5

    Sets Network Variables

    Transform

  6. Step 6

    Combine latency to its respective Network

    Decision

  7. Step 7

    Makes Latency and Loss Filterable

    Transform

  8. Step 8

    Average Latency & Loss over 5m

    Transform

  9. Step 9

    Filters Problematic sites

    Transform

  10. Step 10

    Check if Alert Exists

    Integration

  11. Step 11

    Create Response

    Transform

  12. Step 12

    Merge

    Decision

  13. Step 13

    Message Techs

    Integration

  14. Outcome

    Log the Alert

    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