Automation library · Research and reporting

Medical research tracker with Slack and Redis

Started by another system calling it, and works across Redis and Slack. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 5Service 4

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

  1. 1Incoming Policy WebhookWebhookStarts it
  2. 2Prepare Target URLsCodeLogic
  3. 3Split URLsSplit In BatchesLogic
  4. 4Scrape Policy PageScrapegraph AiService
  5. 5Normalize Policy DataCodeLogic
  6. 6Generate Content HashCodeLogic
  7. 7Redis Get Existing HashRedisService
  8. 8Content Changed?IfLogic
  9. 9Redis Store New HashRedisService
  10. 10Send Slack AlertSlackService

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Redis, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on another system calling it.

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. 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.