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

WooCommerce Refund Alert to Slack

WooCommerce Refund Alert to Slack is a 3-node automation blueprint connecting WooCommerce, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

WooCommerceSlack

Interactive system map

Execution flows, separated by connected path.

Each horizontal lane is one connected flow. Solid lines show runtime execution; dashed lines show AI, model, memory, or tool dependencies.

3

Nodes

2

Links

1

Flows

Connected tools

2 integrations

  • WooCommerce
  • Slack
WooCommerce Refund Alert to Slack execution lanes1 connected flows containing 3 workflow nodes and 2 visible links. Solid lines are execution links and dashed lines are support dependencies. Focus any node to inspect its immediate path.Order Updated. trigger node, wooCommerceTrigger. 0 incoming and 1 outgoing connections.Order UpdatedTRIGGERWOOCOMMERCETRIGGER0 IN / 1 OUTIf Refund and Over 100. decision node, if. 1 incoming and 1 outgoing connections.If Refund and Over 100DECISIONIF1 IN / 1 OUTSend to Slack. Slack node, slack. 1 incoming and 0 outgoing connections.Send to SlackSLACKSLACK1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

Execution linkSupport dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.3 connected nodesEnter or click to lock · Escape to clear

Execution breakdown

Follow each connected flow from start to outcome.

The readable view below uses the same graph relationships as the interactive map. Each row is a connected flow; columns advance only when an actual link connects the nodes.

01

Connected Flow

Order Updated

2 Execution Links

  1. Start

    Order Updated

    Trigger

  2. Step 2

    If Refund and Over 100

    Decision

  3. Outcome

    Send to Slack

    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