Automation library · Alerts and monitoring

EC competitor monitoring watchdog with OpenAI and Slack

Started by a clock, and works across Slack and Supabase. It hands the judgement calls to OpenAI. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

MediumCalls a model: OpenAI

10 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Model 1Logic 4Service 4

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

  1. 1Schedule Every HourSchedule triggerStarts it
  2. 2Workflow ConfigurationSetLogic
  3. 3Get Competitor ProductsSupabaseService
  4. 4Process Each ProductSplit In BatchesLogic
  5. 5Call Apify ScraperHttp RequestService
  6. 6Compare Status & ReviewsCodeLogic
  7. 7Alert Needed?IfLogic
  8. 8AI Review AnalysisOpen AiModel
  9. 9Send Slack AlertSlackService
  10. 10Update Product StatusSupabaseService

How it's built

Starts on
A clock
Steps
10, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Slack, Supabase
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Slack and Supabase accounts, and a key for OpenAI. 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 OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 10 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 10 steps before you point it at anything that matters.