The flow
Starts it 1Logic 3Service 6
The steps in the order they run, from what starts it.
- 1Daily schedulerSchedule triggerStarts it
- 2Get many usersAws IamService
- 3Get IAM User MFA DevicesHttp RequestService
- 4Filter out IAM user with MFA deviceFilterLogic
- 5Send warning message(s)SlackService
- 6Get User Access Key(s)Http RequestService
- 7Parse the list of user access key(s)CodeLogic
- 8Filter out inactive keysFilterLogic
- 9Send message and wait for responseSlackService
- 10Deactivate Access Key(s)Http RequestService
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.
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.