I just built this in 15 minutes and you can too - Cowork + Make in Action

Guys, I need to show you something.

I built a complete Gmail AI Email Triage system inside Make and it took me 15 minutes.

Not 1 hour. Not half a day debugging modules. 15 minutes.

Here’s exactly what it does:

:inbox_tray: Watches your Gmail inbox automatically :robot: Gemini reads every email and classifies it as SPAM / CRITICAL / MODERATE :prohibited: SPAM → Ignored (no action taken) :red_circle: CRITICAL → Gemini drafts a professional reply + logs the email to Google Sheets :yellow_circle: MODERATE → Gemini drafts a reply and saves it as a Gmail draft

That’s 8 modules, a router, and 3 separate AI-powered paths all set up automatically.

Here’s the part that blew my mind :backhand_index_pointing_down:

I didn’t drag a single module.

I described what I wanted to Claude inside Cowork, and it built the entire Make scenario for me — correct module names, filters, connections, everything.

This is what we’ve been building towards as a community.

We spent months learning how to build automations manually — and that knowledge still matters.

Because now when AI builds it, you know exactly what it built and why.

You’re not guessing. You’re reviewing. That’s a superpower.

Drop your questions below :backhand_index_pointing_down:

I’ll be in the comments to walk you through anything.

Let’s go

That’s cool and all, but half the community is filled with posts where Claude (or another AI) messed up a formula by not using the Make functions at all or an iterator/aggregator combo by using the wrong source module. And that’s on simple flows with <10 modules.

Don’t get me wrong, I’m looking forward to the day I can prompt an entire scenario, but they are only good for basic stuff that you can do yourself in 15 mins too.

Also, please replace that polling trigger with a mailhok module so you don’t waste operations.

1 Like

Thanks for your feedback.