Gate SaaS and AI tool approvals with RelayShield, Notion, Slack, and Gmail
UnknownWhat this workflow does
This workflow has 16 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Notion, Slack, Gmail and Relayshield (community). It also calls api.relayshield.net over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Is AI-Tool Request? (If): checks a condition and branches into true / false
- Relay Shield: supply chain
- RelayShield - Secret Scan (AI Tool) (HTTP Request): calls api.relayshield.net (POST)
- Relay Shield: oauth watchlist
- RelayShield - MCP Registry Risk (AI Tool) (HTTP Request): calls api.relayshield.net (POST)
- Relay Shield: supply chain
- RelayShield - Secret Scan (SaaS) (HTTP Request): calls api.relayshield.net (POST)
- Relay Shield: oauth watchlist
- Any AI-Tool Risk Found? (If): checks a condition and branches into true / false
- Any SaaS Risk Found? (If): checks a condition and branches into true / false
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: api.relayshield.net
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-relayshield is verified or supports 3.0 (used in RelayShield - Supply Chain Risk (SaaS), RelayShield - OAuth Watchlist (SaaS), RelayShield - Supply Chain Risk (AI Tool)).
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - Relay Shield
n8n-nodes-relayshield.relayShield - HTTP Request
n8n-nodes-base.httpRequest - Notion
n8n-nodes-base.notion - Slack
n8n-nodes-base.slack - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow receives vendor and AI-tool approval requests via webhook, runs RelayShield risk checks (including an MCP registry check for AI tools), then logs outcomes to Notion, alerts a security Slack channel for risky requests, and emails…