Automation library · Research and reporting

Send a weekly Keephub task progress report to Slack

Started by a clock, and works across Slack. 10 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 5Service 3

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

  1. 1Every Monday 9amSchedule triggerStarts it
  2. 2Or Manually RunManual triggerStarts it
  3. 3Last Week StartDate TimeLogic
  4. 4Last Week EndDate TimeLogic
  5. 5Get Tasks by OrgunitKeephubService
  6. 6Extract Task Template IDsCodeLogic
  7. 7MergeMergeLogic
  8. 8Get ProgressKeephubService
  9. 9Format for MessageCodeLogic
  10. 10Send a messageSlackService

How it's built

Starts on
A clock
Steps
10
Size
Medium: a working afternoon
Connects to
Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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