Aident AI Beta 2

Open-world automations, managed in plain English

Artificial Intelligence

No-Code

This looks awesome. Making automation this simple could be a game changer.

The plain English approach to automation is a really smart unlock — most no-code tools still require users to think in logic trees. Curious how you handle ambiguity when a user's instruction could map to multiple action chains? That edge case is where these tools usually break trust. Would love to see how the error handling surfaces back to the user when something unexpected happens in a real-world trigger scenario.

Like the AI product that reduces cognitive load and make automation straightforward

The plain English automation angle is what gets me — most tools in this space still feel like you need an engineering degree to set up a basic workflow. How does it handle edge cases when a trigger fires but the downstream action fails halfway through?

curious about the "open-world" aspect here. most of these natural language automation tools tend to break once you step outside a very rigid happy path. since you're supporting 23k+ actions, how do you handle state management when one of those mid-stream actions fails or returns an unexpected schema? i'd love to know if there's a way to inspect the underlying logic tree or if it's all just black-box magic.

Really interesting framing! I’m curious who you see as the ideal user for Aident right now. Is this primarily built for non-technical operators who want automation without thinking about logic, or more for technical teams who just want to move faster? Also wondering where you see the main difference vs tools like Zapier, Make, or newer AI automation layers. Is the key advantage the instruction-first interface?

Love the design perspective you’re bringing into automation!

Its amazing how the world of automation software has improved over the last few years - between manually stitching them together in platforms like Zapier to using AI to figuring it all out.

Very cool guys!

Looks cool! Curious how Aident handles reliability when automations get complex across many tools. If a step breaks or an API changes, does the Playbook automatically adapt or flag the issue?

I'm not always the best at prompting so I always appreciate a "Plan" mode to get me started. Is there something similar in Aident so that the automation that gets set up is what I intend it to be?

Really cool concept — automations described in plain English is where everything is heading. We built something similar for our AI routing at TubeSpark (AI for YouTube creators): each task type is described in natural language and the system picks the best AI model automatically. Curious — how do you handle edge cases where the plain English instruction is ambiguous? That's been our biggest challenge with natural language interfaces.

Me describing my automation to Aident: "Do the thing like Zapier/n8n but don't break every Tuesday" 🙏

"AI was smart, the glue was not" is the most honest description of why the current automation stack keeps breaking. Zapier plus RPA plus prompt engineering duct-taped together fails in exactly the ways you'd expect and the 1000th time is never the last time.

The shift from UI design to instruction design that Edward describes is the right framing for what makes this feel different. Node graphs are powerful but they're a UX paradigm built for engineers. Describing intent to a teammate and having it figure out the structure is a completely different contract with the user.

To answer Edward's question from someone building their own AI platform: the hardest part of turning a vague goal into a running automation is usually defining the edge cases. People describe the happy path clearly, but when something unexpected happens mid-run, the automation either fails silently or does something wrong. How does Aident handle ambiguous situations mid-playbook? Does it stop and ask, or make a judgment call? Congrats on the launch! 🤖

Does Aident sit on top of existing tools or replace them? I already have a bunch of Zaps running, so migration cost is a real concern for me.

Huge congrats on the launch! I've been looking for a way to bridge my Slack and Google Sheets without the node-graph headache. Signing up for Beta 2 now, and I'll be sure to send over some honest feedback! 🚀