Suspicious login detection
Ready for 3.0What this workflow does
This workflow has 33 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Postgres, Gmail and Slack. It also calls api.userparser.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Extract relevant data (Edit Fields (Set)): sets or maps fields
- Example event (Code): runs custom JavaScript code
- GreyNoise (HTTP Request): calls an HTTP API
- UserParser (HTTP Request): calls api.userparser.com
- IP API (HTTP Request): calls an HTTP API
- Complete login info (Merge): merges the data from its input branches
- noise? (If): checks a condition and branches into true / false
- Merge: merges the data from its input branches
- Unknown threat? (If): checks a condition and branches into true / false
- Check classification (Switch): routes items into 3 branches
…plus 15 more steps. See the full node list below.
Services it uses
HTTP calls to: api.userparser.com
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 (13)
- Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - Postgres
n8n-nodes-base.postgres - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - No Operation, do nothing
n8n-nodes-base.noOp - HTML
n8n-nodes-base.html - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack - Switch
n8n-nodes-base.switch - Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code
From the author
This n8n workflow is designed for security monitoring and incident response when suspicious login events are detected. It can be initiated either manually from within the n8n UI for testing or automatically triggered by a webhook when a new login event…