Automation library · Alerts and monitoring

Monitor contractor licences weekly and send Slack digests

Started by a clock, and works across Apify and Slack. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 8Service 2

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

  1. 1Every Monday 06:00Schedule triggerStarts it
  2. 2Your rosterCodeLogic
  3. 3Route by stateCodeLogic
  4. 4Covered state?IfLogic
  5. 5Look up the licenceApifyService
  6. 6Not covered - keep the rowSetLogic
  7. 7Classify each licenceCodeLogic
  8. 8Anything to report?IfLogic
  9. 9Build the digestCodeLogic
  10. 10Nothing to reportNo OpLogic
  11. 11Send the digest to SlackSlackService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Apify and Slack accounts. 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. 11 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 11 steps before you point it at anything that matters.