How Gydmation started
It started with a familiar kind of frustration. Our founder, Kailash Sivagnanam, was manually sending a WhatsApp message to every new lead that came in — and it showed. Replies were slow, inconsistent, and easy to miss between everything else on his plate.
He knew the fix: connect his Typeform submissions straight to WhatsApp so a message went out the moment someone signed up. He researched automation tools, learned n8n, and spent hours trying to wire the two together. He knew exactly what he wanted to build — he just kept getting stuck on the JSON syntax, the webhook URLs, and figuring out where his Twilio credentials were even supposed to go.
He wasn't the only one. Plenty of small business owners, marketers, and operators know precisely what they want automated, and get stopped by the same wall of technical detail standing between them and it. That gap — not a lack of ideas, but a lack of accessible tooling — is what Gydmation set out to close.
Who's behind it
Kailash founded Hacroo Technologies in 2024, on his own, out of Panruti, Tamil Nadu. In January 2025, he started building the solution to his own problem under Hacroo: if you can describe what you want in plain English, AI should be able to write the n8n workflow for you. That project became Gydmation.
His brother, Sabari Raja, joined him on it soon after — not as a co-founder of Hacroo, but as the team member who helped build Gydmation. Sabari trained and worked as a wood carpenter; automation and software weren't his background, but he wanted to build skills in current technology, and working alongside his brother on something real was how he chose to start.
The first version was rough — a simple prompt box that spat out raw n8n JSON. But testing it made one thing obvious fast: people who'd never managed to build a working automation on their own were suddenly generating one in minutes. That reaction is what turned a side project into the product you're looking at now.
What we believe
Simplicity is not optional
We push hard to keep complexity out of your way. If a non-technical person can't figure out a new feature in under a minute, we treat that as a bug, not a training problem.
Privacy is non-negotiable
Your API keys, your workflows, your business data — they're yours. Gydmation is built so your credentials never touch our servers. That's a decision baked into the architecture, not a policy we could quietly change later.
Community builds better products
The features that have mattered most came from people actually using Gydmation and telling us what got in their way. We read every message that comes in, and we intend to keep it that way as we grow.
Ship fast, learn faster
We'd rather put an imperfect feature in front of real users and improve it from their feedback than sit on something until it's "done." Fast feedback loops beat perfect first drafts.
Where things stand today
Gydmation is still early days. We're not asking you to trust years of track record — we're asking you to be one of the people who shapes what this becomes. With a team this size, a bug report or a feature request reaches an actual person, not a support queue.
Have questions, feedback, or just want to say hello? Get in touch — we read everything.