Nodagentry

Nodagentry

Sign in to keep named workflows and test cases. Guests can export graph JSON.

Explore the workflow below, then Run on Sim. No key needed.

On-call Incident Router

About this example

A software company just started losing checkout. The API has been 5xx for eight minutes, the public status page is still green, and customers are already posting on social. Peak traffic is twenty minutes out. You are the on-call. Is this us — and do we wake people, or is it a flaky canary we should close?

Ticket text · optional edit

On-call Incident Router

12 steps · 12 connections. Follow the handoffs from top to bottom. Steps at the same depth share a row; branch labels show alternative paths.

Ready to use this workflow? Learn how to send tasks from an event or schedule →

  1. Stage 1

    Paste the page / Slack / PagerDuty note into the session task, then Run.

  2. ↓ Stage 2

    Cheap classify: HOT vs COLD. Always runs.

  3. ↓ Stage 3

    Keyword router (Sim-safe). COLD words → noise path. Default / HOT → live checks.

  4. ↓ Stage 4 · 2 steps

    Hub so the router can fan out to both live tools.

    COLD-only. Short close-out — no page, no human.

  5. ↓ Stage 5 · 3 steps

    http_fetch a public status page (demo stand-in for your status URL).

    Final COLD artifact.

    End of this path

  6. ↓ Stage 6

    Fan-in status + search before the war-room writer.

    Receives 2 incoming connections.

  7. ↓ Stage 7

    HOT-only page card. Does not run on COLD.

  8. ↓ Stage 8

    HOT only. Approve before treating this as a page.

  9. ↓ Stage 9

    Final HOT artifact.

    End of this path

This map shows every saved step and connection, including paths not taken in the last run. Loops are grouped when no further ordering is possible. Editing positions remains available in the canvas.