Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
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...
n8n-nodes-base.stickynote, n8n-nodes-base.slacktrigger, n8n-nodes-base.openai, @permitio/n8n-nodes-permitio.permit, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.slack
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Taofiq.
Original n8n.io source> This n8n workflow template uses a community node and is only compatible with the self-hosted version of n8n.
DevOps teams, platform engineers, and ops leads who use Slack bots for infrastructure tasks but need to control who can trigger what. Ideal for teams that have outgrown hardcoded IF-node permission checks.
A team member @mentions the bot in Slack with a DevOps request like "restart staging" or "deploy to production." OpenAI classifies the message into a structured action and resource. Permit.io then checks if that Slack user's role allows the action. If permitted, the workflow executes the action and posts the result. If denied, the bot responds with the user's current permissions and suggests who can help.
@permitio/n8n-nodes-permitio community nodeapp_mentions:read, chat:write, channels:read, users:read scopesThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Gate AI Slack DevOps bot actions with OpenAI and Permit.io RBAC |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | DevOps, AI Chatbot |
| Author | Taofiq |
| Published | 16 Mar 2026 |
Use the JSON export at /data/workflows/14087/14087.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps, AI Chatbot use case.