All templates
Automation#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.

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. 3Press Cmd+V / Ctrl+V — nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
#Condition#Routing#Support#Automation

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

6 nodes · Free & source-available

Explore related automations — each page links to other templates so you can discover more use cases.

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