Hey, I've been building AI workflows, AI agents for past few years. I found top workflow tools to be inefficient for the agentic era (you are limited in logic to what their json allows, you end up squeezing stuff into the "Code Node") and AI agents burn tokens where it's often NOT needed , also not in all workflows you are ok with non-determinism.
I believe workflows must be code. AI is great at producing code.
authoring workflows from claude code instead of a dashboard is the part that clicked for me. are you seeing n8n or zapier folks switch, or mostly new users?
Hey! Each code runs in an an isolated VM (dev machines), and the state lives in it. If you want your own shared state, you can add some DB as an integration (e.g. Supabase). The running state is persisted for some time too.
As for load - we are a part of incubator inside Wix.com, and this VM approach with code running in it is already proven at a much much higher scale, so no worries on that.
As for webhook retries - for now we don't give much control over it, but will add it!
Hey, I've been building AI workflows, AI agents for past few years. I found top workflow tools to be inefficient for the agentic era (you are limited in logic to what their json allows, you end up squeezing stuff into the "Code Node") and AI agents burn tokens where it's often NOT needed , also not in all workflows you are ok with non-determinism.
I believe workflows must be code. AI is great at producing code.
We made open source lib of sdk for workflows: https://github.com/wix-incubator/whenever
You can host/deploy workflows that use this sdk, using our skill: https://www.whenever.dev/skill.md
You can add our remote http mcp server: https://mcp.whenever.dev
Or you can use our "v0" to build workflows through our app: www.whenever.dev
If you are building workflows for others or you need to host yours - give it a try, it's free to start.
Happy to hear some feedback of what worked and what didn't for you.
authoring workflows from claude code instead of a dashboard is the part that clicked for me. are you seeing n8n or zapier folks switch, or mostly new users?
Hey, it's a mix of both :)
Clean launch! Curious how you're handling state durability and webhook retries under heavy concurrent workflow runs as things scale up.
Hey! Each code runs in an an isolated VM (dev machines), and the state lives in it. If you want your own shared state, you can add some DB as an integration (e.g. Supabase). The running state is persisted for some time too.
As for load - we are a part of incubator inside Wix.com, and this VM approach with code running in it is already proven at a much much higher scale, so no worries on that.
As for webhook retries - for now we don't give much control over it, but will add it!
[flagged]