The flow
Starts it 1Model 2Logic 7Service 3
The steps in the order they run, from what starts it.
- 1Schedule Trigger - Continuous Brand ScanSchedule triggerStarts it
- 2Anthropic - Impersonation Classification ModelLm Chat AnthropicModel
- 3Set - Prepare Brand Protection ContextSetLogic
- 4AI - Classify & Score Impersonation CandidatesAgentModel
- 5JS - Build Brand Monitoring Query BatchCodeLogic
- 6JS - Parse Impersonation Classification OutputCodeLogic
- 7Fetch Candidate Brand Mentions & AccountsHttp RequestService
- 8JS - Calculate Aggregate Threat Score & Format Alert RecordCodeLogic
- 9Wait For Impersonation Classification AIWaitLogic
- 10Save Scan Results to Google Sheets TrackerHttp RequestService
- 11IF - Escalation RequiredIfLogic
- 12Wait For Alert DeliveryWaitLogic
- 13Send Critical Impersonation Alert EmailHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 13, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- Claude
Questions
What does it need to run?
An n8n account, and a key for Claude. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls Claude. Model calls are billed by the provider, not by n8n.
How long does it take to set up?
Plan an afternoon. 13 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 itNothing 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 13 steps before you point it at anything that matters.