← Work
04

AI email automation workflow.

Automating PsTally's follow-ups with AI, and keeping the final say.


We are in an interesting time. A lot of the work I used to do by hand can now be handed to AI, and it does it well. The trick is knowing which part to hand over and which part to keep. I hand over the labour. I keep the judgement.

I run PsTally, software for gaming lounges. I noticed that many owners sign up, set up their consoles, and then stop before they open. I wanted to follow up with each of them, but I do not have the time to message everyone one by one. So I automated it.

The workflow runs in n8n. First it queries my database for the owners who stalled: signed up, added consoles, then went quiet. For each one it pulls their real details, so the message is about them and not a template. That goes to Claude, which writes a short, personal email. Then it stops and waits for me. It sends me every draft with an approve button, and nothing goes out until I click. When I approve, it sends the emails through Resend.

So far it has reached twenty-one real owners. Each got a message built from their own details, and each one passed through me before it sent.

The part I automated is the part that should be automated: finding the right people and drafting for each one. The part I kept is the part that should stay with a person: deciding what a real customer actually receives.

The workflow
The workflow in n8n: query, draft, approve, send.

The workflow in n8n: query, draft, approve, send.

Built with
Claude (Haiku) n8n PostgreSQL Resend PsTally

If this way of building resonates —

No brief required · Tell me what you’re trying to make