The workflow most tools can't build. Zyk did it in one shot.
I tried building a workflow that fetches Star Wars data from SWAPI, asks questions about it, and summarizes the results. Simple enough, right?
Most automation platforms failed to create it.
With Zyk, one shot. Done.
## Why most platforms fail at thisIt's not a skill issue. It's architecture.
Tools like n8n are built around a visual, stateless node graph. That works great for simple linear pipelines. But the moment you need durability, retries, timeouts, or human-in-the-loop interactions, you start fighting the tool instead of using it.
These aren't edge cases. They're the core of any real-world workflow:
Durable execution: if a step fails halfway through, you need to resume, not restart from zero.
Automatic retries: external APIs fail. Your workflow shouldn't.
Timeouts: waiting for human input? You need a hard boundary, not an infinite hang.
Human-in-the-loop: real automation often requires a human checkpoint before proceeding.
These are solvable. But only if the infrastructure underneath was designed for it from the start.
The stack that gets it right
We think the answer is Claude + Zyk + Hatchet.
Claude understands plain English and converts it into executable workflow logic. No drag-and-drop, no node configuration.
Hatchet provides the durable execution engine underneath. Retries, scheduling, timeouts, and human-in-the-loop baked in at the infrastructure level.
Zyk ties it together. Describe what you want, get a working workflow.
The SWAPI demo in the video above isn't just a fun Star Wars example. It's a workflow with real complexity: external API calls, per-film interactive questions with a 1-minute timeout, and a final summary. The kind of thing that exposes the limits of most tools fast.
Zyk handled it in one shot.
Want to see the idea in action? zyk.dev — just a demo playground to demonstrate the core idea, not production-ready.
Zyk is open source and self-hostable: github.com/zyk-hq/zyk
