Awish- Build secure automations you can control from Wp, Slack, Telegram
Hey Indie Hackers Community — I’m Alper, co-founder and project manager of Awish.
About a year ago, while working as a freelancer, I noticed how much time I was losing on repetitive online tasks.
It wasn’t one big task that slowed me down. It was the small things I had to repeat again and again: follow-ups, updates, reports, reminders, drafts, client messages, and moving information between tools.
That’s where the idea for Awish started.
Awish helps individuals and teams turn repetitive online work into secure, self-improving automations using natural language.
You describe what you want in chat. Awish understands the request, plans the workflow, connects the right apps with your permission, and helps create the automation in minutes.
But the part we’re most excited about is this:
After your automation is created, you don’t need to keep opening Awish to manage it.
You can control your automations from the apps you already use every day — WhatsApp, Slack, or Telegram.
That means you can:
run an automation
pause a workflow
check status
approve an action
receive summaries
manage tasks while you’re away from your desk
We also designed Awish around control and trust. Important actions should be reviewed and approved, app connections should happen with permission, and automations should feel reliable — not like a black box.
Awish also learns from your conversations and workflow history, so over time your automations can become more personalized and better aligned with how you actually work.
For our Indie Hackers Community, we’re offering free credits so you can try Awish yourself.
We’d really love your honest feedback today, especially on:
1. Is the first use case immediately clear?
2. Would you trust automations controlled from WhatsApp, Slack, or Telegram?
3. Which repetitive workflow would you want Awish to automate first?
4. Where would you want more control or approval before an automation runs?
Thank you for checking out Awish. I’ll be here answering questions and learning from your feedback.
How do you currently handle your analytics and would you mind reading my indiehacker pots on how AI crawlers and bots are ruining analytics data?
https://www.indiehackers.com/post/i-just-discovered-my-analytics-numbers-are-mostly-fake-here-is-why-8197e3ff9d
Just read it—really interesting point. We currently focus more on product events, sign-ups, and paid conversions than raw pageviews, but we haven’t separated AI crawlers from real users at the server level yet. Your human, crawler, and rogue-bot split makes a lot of sense. How are you planning to identify sophisticated headless browsers without blocking legitimate users?
Secure automation feels like a strong angle. Congrats on building something that works across Slack and Telegram!
Voice‑controlled automation across messaging apps sounds powerful. I’ll give the free credits a try — I’m curious how SMBs might use this for routine workflows compared to Zapier.
Thank you, our most important features are that it's secure, self-improving, and allows you to automate your tasks entirely through voice commands. Compared to applications like Zapier and n8n, it can create automations 10-50 times faster and connect to messaging applications with a single click. You can control it from places like WhatsApp without even opening the application itself. We're providing free credits for you to try it. We would be very happy if you could try it and leave a review.
The trust question feels connected to the first-use question.
“Secure, self-improving automations” describes a lot of capability, but trust probably means something different depending on what someone is actually letting Awish do.
That makes the first workflow feel like a consequential decision, not just an onboarding choice.
Exactly. Trust starts with what Awish can access and how that information is handled. User data, workflow details, and company information are stored securely, while app connections are established through permission-based authentication. We also make the required access and planned actions clear before a workflow runs.
That makes sense. The permission boundary is an important part of how users decide what level of automation they’re comfortable delegating.