Automation library · Integrations

Draft and route Google reviews replies with Google Places

Started by a clock, and works across Email. 16 steps, 3 branches: a working afternoon to understand properly.

Medium

Download free
16 stepsMedium: a working afternoon
3Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 10Service 5

The steps in the order they run, from what starts it.

  1. 1Every 15 minSchedule triggerStarts it
  2. 2Client ConfigSetLogic
  3. 3Fetch Reviews (Places API)Http RequestService
  4. 4Normalize + DedupCodeLogic
  5. 5Check Has TextIfLogic
  6. 6Route by RatingIfLogic
  7. 7Build No-Text ReplyCodeLogic
  8. 8Build Positive RequestCodeLogic
  9. 9Build Negative RequestCodeLogic
  10. 10Route No-Text ReplyIfLogic
  11. 11Claude: Draft ReplyHttp RequestService
  12. 12Claude: Summarize + DraftHttp RequestService
  13. 13Alert OwnerEmail SendService
  14. 14Send Draft to OwnerEmail SendService
  15. 15Extract ReplyCodeLogic
  16. 16Parse AlertCodeLogic

How it's built

Starts on
A clock
Steps
16, with 3 branches
Size
Medium: a working afternoon
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 16 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.