The flow
Starts it 1Model 2Logic 6Service 4
The steps in the order they run, from what starts it.
- 1Cron - Pricing Cycle TriggerSchedule triggerStarts it
- 2Anthropic - Brand Safety ModelLm Chat AnthropicModel
- 3Fetch POS Sales VelocityHttp RequestService
- 4Fetch Local Weather ConditionsHttp RequestService
- 5Fetch Nearby Events & Foot TrafficHttp RequestService
- 6Claude - Brand-Damage CheckAgentModel
- 7Merge - Combine Demand SignalsMergeLogic
- 8JS - Parse AI Output & Finalize Approved PricesCodeLogic
- 9JS - Build Demand Signal BaselineCodeLogic
- 10Wait For ResultWaitLogic
- 11JS - Run Elasticity Pricing ModelCodeLogic
- 12Push Prices to QR MenuHttp RequestService
- 13Wait For Model BufferWaitLogic
How it's built
- Starts on
- A clock
- Steps
- 13, 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.