Automation library · Alerts and monitoring

Monitor Bluesky keyword posts with Apify

Started by a clock, and works across Apify and n8n data table. 10 steps, 2 branches: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 5Service 3

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

  1. 1Manual Execution StartManual triggerStarts it
  2. 2Run Every HourSchedule triggerStarts it
  3. 3Start Bluesky MonitoringApifyService
  4. 4Check for Dataset AvailabilityIfLogic
  5. 5Retrieve Monitoring DataApifyService
  6. 6Handle Missing Dataset ReportCodeLogic
  7. 7Process Dataset RecordsCodeLogic
  8. 8Verify Dataset RecordsIfLogic
  9. 9Upsert New PostsData TableService
  10. 10Generate Ingestion ReportCodeLogic

How it's built

Starts on
A clock
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Apify, n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Apify 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. 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.