Gate AI Slack DevOps bot actions with OpenAI and Permit.io RBAC
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: OpenAI (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on Slack events. Along the way it connects Slack and Permitio (community). It also calls httpbin.org over HTTP.
How it runs
Trigger: On Slack events.
- Classify DevOps Intent (OpenAI): work with chat
- Check Permission (Permit): uses Permit
- Is Allowed? (If): checks a condition and branches into true / false
- Execute DevOps Action (Mock) (HTTP Request): calls httpbin.org (POST)
- Get User Permissions (Permit): get user permissions
- Slack: uses Slack
- Get Authorized Users (Permit): get authorized users
- Slack: uses Slack
Services it uses
HTTP calls to: httpbin.org
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- OpenAI (legacy) in Classify DevOps Intent: replace with OpenAI node (AI section).
- Also check Slack Trigger requires a signing secret on the Slack API credential.
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) Classify DevOps Intent | OpenAI node (AI section) |
Nodes used (6)
- Slack Trigger
n8n-nodes-base.slackTrigger - OpenAI
n8n-nodes-base.openAi - Permit
@permitio/n8n-nodes-permitio.permit - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack
From the author
> This n8n workflow template uses a community node and is only compatible with the self-hosted version of n8n. Who's it for DevOps teams, platform engineers, and ops leads who use Slack bots for infrastructure tasks but need to control who can trigger…