Monitor & alert on inactive AWS IAM users with Slack notifications
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every week). Along the way it connects AWS IAM and Slack.
How it runs
Trigger: On a schedule (every week).
- Get many users (AWS IAM): uses AWS IAM
- Get user (AWS IAM): get
- Custom HTTP Request (enable to try) (HTTP Request): calls an HTTP API
- Filter: keeps only the items that match a condition
- IAM user inactive for more than 90 days? (If): checks a condition and branches into true / false
- Send a message (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - AWS IAM
n8n-nodes-base.awsIam - No Operation, do nothing
n8n-nodes-base.noOp - Slack
n8n-nodes-base.slack - If
n8n-nodes-base.if - Filter
n8n-nodes-base.filter - HTTP Request
n8n-nodes-base.httpRequest
From the author
AWS IAM Inactive User Automation Alert Workflow > Weekly job that finds IAM users with no activity for > 90 days and notifies a Slack channel. > ⚠️ Important: AWS SigV4 for IAM must be scoped to us-east-1. Create the AWS credential in n8n with region…