Automation library · Integrations

Docker registry cleanup workflow

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

Medium

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

The flow

Starts it 1Logic 7Service 8

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

  1. 1Scheduled TriggerSchedule triggerStarts it
  2. 2List ImagesHttp RequestService
  3. 3Extract Image NamesCodeLogic
  4. 4Retrieve Image TagsHttp RequestService
  5. 5Split TagsSplit OutLogic
  6. 6Filter Valid TagsFilterLogic
  7. 7Fetch Manifest DigestHttp RequestService
  8. 8Fetch Manifest Digest for BlobHttp RequestService
  9. 9Update FieldsSetLogic
  10. 10Sort by Creation DateSortLogic
  11. 11Group Tags by ImageCodeLogic
  12. 12Identify Tags to RemoveCodeLogic
  13. 13Remove Old TagsHttp RequestService
  14. 14Send Notification EmailEmail SendService
  15. 15Execute Garbage CollectionSshService
  16. 16Send Failure Notification EmailEmail SendService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Email 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. 16 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 16 steps before you point it at anything that matters.