Runaway workflow simulator

A workflow keeps processing the same lead and re-calling paid tools: Webhook → SerpAPI → Firecrawl → OpenAI → CRM/SAP. This is a client-side simulated demo. Reason codes are illustrative labels for the demo, not live API fields.

Simulated workflow. Not customer traffic. No billing data and no network calls unless you separately use the live demos on Use cases.
Webhook→ SerpAPI→ Firecrawl→ OpenAI→ CRM / SAP
Controls · lead-enrich-v30 attempts

Each click = one workflow loop on task lead:acme-4421 before the next paid tool batch.

1–3 allow   4–6 warn   7+ block

Reason code (illustrative): —

Decision: allow

Incident report (simulated)

Type
—
Workflow
lead-enrich-v3
Repeated task
lead:acme-4421
Blocked after
—
Est. spend avoided
—
Reason code
—
Recommended fix
—
Spend comparison (illustrative $/loop)
Attempts
0
Tool calls (no guard)
0
Tool calls (with guard)
0
Blocked calls
0
Spend w/o guard
$0.00
Spend w/ guard
$0.00
Spend avoided: $0.00 (simulated; profile-based illustrative loop costs)
SerpAPI Firecrawl OpenAI CRM
Without guardEvery loop bills all four tools.
With ProceedGateStops before the next paid batch after block.
Event log
— Ready. Demo policy: attempts 1–3 allow, 4–6 warn, 7+ block.\n

Using n8n? See the Shared Guard Sub-workflow pattern →

Join pilot Docs Scraper retry storm lab