Temporal Demo Visual Workflows — Design skill for Claude Code

Visual Workflows

A visual workflow builder where every flow you draw runs as a durable Temporal Workflow, on workers that scale to zero.

• Steps that call out are Activities. Each step has its own retry policy and timeouts, which it can inherit from the flow. Steps can also carry an undo request, so a failed run compensates in reverse order (a saga). HTTP and Claude calls heartbeat while they wait. If a worker dies mid-call, Temporal retries within seconds instead of waiting out the step's timeout. A step cancelled mid-call, for example one that lost a race, has its request aborted.
• When retries run out:
  • A step can switch to slow retries (fast/slow retries).
  • It can pause until a person corrects its request and retries it (a resumable Activity).
  • A Retry-After header sets the next retry's delay.
• Events from outside arrive as Signals. Every run has a callback URL, and a POST to it is the same as sending the Signal from the Temporal UI.
• Event lanes: an On signal lane runs once per event. An On update lane runs for a validated Update and returns its Respond step's value to the caller. Lanes change the run's variables while the main path is mid-flight. Visible variables are readable through a Query.
• Waiting is free:
  • Wait for signal, Wait for condition, approvals, and timers all hold the run with no compute.
  • Timers can be a fixed amount, or an expression that recalculates when a lane changes a variable.
  • Wait for signal can collect a batch: it gathers events until they go quiet and drops duplicates.
• Loops: a Loop step repeats its body unti