Workflow Automation Overview

Why Workflow Automation is Essential

In enterprise operations, time delays between detecting a problem (such as a failed safety inspection, a chemical spill, or a severe customer complaint) and executing a corrective response create compliance breaches, asset downtime, and safety hazards. Relying on manual emails, phone calls, or paper hand-offs inevitably results in missed tasks and unassigned responsibilities.

The Workflow Automation engine eliminates these gaps with a 24/7 event-driven automation framework. Administrators use a visual drag-and-drop builder canvas to map out standard operating procedures (SOPs). When an event occurs—such as an inspection failing a critical check or an incident being reported—the system automatically evaluates custom logic rules and dispatches downstream work items without human intervention.

🧩 The Node Palette: Building Blocks of Every Workflow

Every workflow is composed of nodes dragged from a left-hand palette onto a visual grid canvas. Each node serves a specific role in the automation pipeline. The complete node palette, in order, is:

#	Node	Purpose
1	▶️ Start Node	The entry point — listens for events from Inspections, Incidents, Issues, Tasks, or Feedback
2	✉️ Send Notification Node	Dispatches Email or Push notifications to users
3	✅ Approve & Sign Node	Pauses the workflow and requests formal human approval with custom outcomes
4	📝 Create Task Node	Auto-generates a Task with assignees, priority, type, and due date
5	🛠️ Create Issue Node	Auto-opens a tracked Issue ticket with category and priority
6	📋 Create Inspection Node	Auto-schedules a follow-up Inspection from a template
7	🚨 Escalation Node	Dispatches tiered, time-sensitive emergency alerts up the management chain
8	🏁 End Node	Terminates a workflow path and closes the execution log

🔗 Connecting Nodes: Edges, Outcomes & Visual Links

Nodes on the canvas are connected by edges (visual arrow links) that define the execution flow.

How to Create Connections

Hover over the output handle (small circle at the bottom of a node).
Click and drag a line to the input handle (small circle at the top of the next node).
Release to create a smooth-step arrow connection between the two nodes.

Edge Outcomes (Connection Labels)

When you click on a connection line between nodes, an Outcomes popup appears allowing you to label that connection path. Edge labels differ based on the source node:

From a Start Node: Edges can be labeled with specific condition names defined in the Start Node's condition rules (e.g. "Score Below 50%", "Fire Hazard Detected").
From an Approve & Sign Node: Edges are labeled with decision outcomes ("Approve" or "Deny").
From other Action Nodes: Edges default to "Approve" / "Deny" labels.

Connection Rules

Every node's output handle can connect to one or more downstream nodes (parallel execution).
Every workflow path must terminate at an End Node to close the execution log properly.
Connection arrows use color coding: green for positive outcomes, red for negative outcomes, and gray for neutral routes.

💻 Web Portal Canvas Navigation & Controls

(Requires View Workflows, Create Workflows, or Edit Workflows permission)

Accessing the Workflow Builder

Navigate to Workflows in the primary sidebar menu.
The Workflow Index displays all configured automation rules with Active/Inactive status toggles.
Click Create Workflow (or select an existing rule) to open the visual builder canvas.

Canvas Controls

Left Palette: Drag node types from the palette onto the grid.
Properties Drawer: Click any node to open its configuration panel on the right side.
Zoom & Pan: Use mouse wheel to zoom in/out and click-drag on empty canvas space to pan.
Node Resize: Selected nodes display resize handles at corners.
Clone Node: Click the blue copy icon on a selected node to duplicate it with its settings.
Delete Node: Click the red trash icon on a selected node to remove it.
Edge Editing: Click on a connection line to open the Outcomes popup and label the path.
Save & Activate: Click Save to persist your workflow. Toggle the status to Active to enable live event monitoring.

🏢 End-to-End Node Execution Flow

WORKFLOW EXECUTION PIPELINE EXAMPLE: Failed Vehicle Inspection

[ ▶️ START NODE ]
  Trigger: "Vehicle Pre-Trip Inspection"
  Condition: Score < 70%
         │
         ▼
[ ✉️ SEND NOTIFICATION ]                     [ 📝 CREATE TASK ]
  Alert Fleet Manager ◄──────────────────────►  "Vehicle Repair Required"
  via Email + Push                               Assigned to: Mechanic Team
         │                                       Due: 24 Hours
         ▼                                              │
[ ✅ APPROVE & SIGN ]                                   │
  Request: Maintenance Budget Approval                  │
  Assigned to: Operations Director                      │
       ├── Approved ──► [ 🏁 END NODE ]                 │
       └── Rejected ──► [ 🚨 ESCALATION ]              │
                           Level 1: Regional Manager    │
                           Level 2: VP of Operations    │
                                    │                   │
                                    ▼                   ▼
                              [ 🏁 END NODE ]    [ 🏁 END NODE ]

🏢 Real-World Enterprise & Industry Scenarios

🏭 Scenario 1: Manufacturing Plant — Critical Equipment Lockout & Repair

Operational Context: In a manufacturing facility, if a forklift or overhead crane fails a pre-shift safety inspection, the machine must be locked out immediately, a repair task assigned to mechanics, and manager sign-off obtained for repair budget authorization.
End-to-End Workflow:
1. ▶️ Start Node: Triggered by the Forklift Pre-Shift Checklist when Score < 70% OR Brake Check = "Fail".
2. ✉️ Send Notification Node: Dispatches instant Email + Mobile Push alerts to the Maintenance Engineering Team with machine ID and failed checklist items.
3. 📝 Create Task Node: Auto-generates a High-Priority Task titled "Emergency Forklift Brake Repair" assigned to the mechanic group with a 4-hour due date offset.
4. ✅ Approve & Sign Node: Requests Plant Manager approval to authorize replacement parts budget.
  - Approved Path ──► 🏁 End Node (Repair authorized and logged).
  - Rejected Path ──► 🚨 Escalation Node (Escalates to Regional Facilities Director).

🛢️ Scenario 2: Oil & Gas Refinery — Environmental Chemical Release Response

Operational Context: Energy facilities must respond immediately to environmental gas or chemical spills, alerting leadership and initiating mandatory follow-up safety re-audits.
End-to-End Workflow:
1. ▶️ Start Node: Triggered by a Chemical / Gas Spill Incident when Severity = High OR Critical.
2. 🚨 Escalation Node:
  - Level 1 (0–15 min): Alerts Site Safety Supervisor via App Push + Email.
  - Level 2 (15–30 min): Auto-escalates to Regional EHS Manager if un-acknowledged.
  - Level 3 (> 30 min): Auto-escalates to VP of Operations.
3. 📋 Create Inspection Node: Auto-schedules a mandatory "7-Day Post-Incident EHS Safety Re-Audit" template assigned to the Senior EHS Auditor.
4. 🛠️ Create Issue Node: Auto-opens a formal Issue ticket titled "Chemical Spill Remediation" for long-term environmental tracking.
5. 🏁 End Node: Closes the emergency pipeline log.

🛒 Scenario 3: Retail Hospitality Chain — Guest NPS Detractor Recovery

Operational Context: A hotel chain wants to capture and resolve guest dissatisfaction before guests checkout and leave negative online reviews.
End-to-End Workflow:
1. ▶️ Start Node: Triggered by a Guest Post-Stay Survey submission when NPS Rating ≤ 4 (Detractor).
2. ✉️ Send Notification Node: Sends an instant Push alert to the Duty Manager's mobile app containing guest room number and review comments.
3. 🛠️ Create Issue Node: Auto-opens a high-priority Issue ticket titled "Guest Complaint Recovery — Room 402" assigned to Customer Relations.
4. 🏁 End Node: Concludes the guest recovery trigger path.