FeaturedCustomer Support#Condition#Routing#Support#Automation

Urgent vs Standard Router

Branch on a keyword in the input line โ€” fast path vs standard path using a Condition and two outputs.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Condition#Routing#Support#Automation

Click a node to select it โ€” same as the Heym editor; the panel shows its settings.

4 nodes ยท Free & source-available

Urgent vs Standard Router

Demonstrates Condition branching: if the line contains URGENT, follow the high-priority Output; otherwise use the standard queue output.

What this workflow does

  1. Input receives one line of text (e.g. support ticket subject)
  2. Condition checks for the substring URGENT (case-sensitive โ€” adjust in the node if you prefer case-insensitive)
  3. Output (FastLane) vs Output (Standard)

Setup

Connect Slack or ticketing nodes downstream of each branch. No secrets in the template.

How to import this template

  1. 1Click Import โ†’ Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+Vโ€” nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis ยท production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom ยท glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner โ€” none of them talk.
symptom ยท visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym ยท one runtimeโ–ฒ
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym