When I started building TeamAutomation, I thought the hardest part would be the Slack integration.
It wasn't.
The hardest part was figuring out what happens when someone just... doesn't respond.
You send an approval request. The other person is busy. They forget. The request sits there for 3 days. Meanwhile the person who sent it has no idea if it was seen, ignored, or lost.
That's the problem I needed to solve. Automated nudges.
Here's how it works in TeamAutomation:
Day 1 — If no response after 24 hours, the approver gets a reminder in Slack.
Day 3 — Still no response? Another nudge, slightly more urgent.
Day 7 — Final reminder before the request expires.
The tool I used for this is called Inngest — it handles background jobs and scheduled functions. As a non-technical founder, I didn't build this from scratch. I worked with AI tools to implement it step by step.
But the logic behind it? That came from just thinking about the real problem.
Most approvals don't fail because people are lazy. They fail because there's no follow-up system. Email gets buried. Slack messages scroll away. Nobody chases.
Automated nudges fix that without making anyone feel micromanaged.
If you're building something similar — start with the failure case. What happens when nothing happens? Build for that first.
Still at 0 users, but the system works. Onward.
Mahad Tahir
Posted on
How I built automated reminders into a Slack approval tool with zero coding experience
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (3)
Zero coding experience to a working Slack approval tool with reminders is exactly the shift that's exciting right now, the barrier moved from "can you code" to "can you describe what you want and verify it works." Slack approval flows have a sneaky-hard part though: the state machine (pending, approved, rejected, reminder-sent, expired) and making sure a reminder doesn't fire after someone already approved. That edge-case wiring is where no-code builds usually crack first. Getting it solid is the difference between a demo and something a team actually relies on. That's the boring-but-critical layer I automate in Moonshift. How are you tracking approval state, inside Slack or a backing store?
Good catch — state lives in a backing store (Postgres), not Slack. Each approval request has a status field that updates on button click, so even if Slack message is deleted, the record stays. Reminder job checks status before firing — if already approved/rejected, it skips. That's exactly the edge case that breaks demo-quality builds. Are you running into this with Moonshift users?
Harjot, this has been helpful — I'm actually building something in this space. Would you be open to a quick call? Would love your technical perspective.