Block 1 - OpenAI Chat Model
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
RBAC for AI agents with n8n and Port This workflow implements role based access control for AI agent tools using Port as the single source of truth for permissions. Different users get access to di...
@n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.code, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.toolcalculator, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.slacktrigger, n8n-nodes-base.slack
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Port IO.
Original n8n.io sourceThis workflow implements role-based access control for AI agent tools using Port as the single source of truth for permissions. Different users get access to different tools based on their roles, without needing a separate permission database.
For example, developers might have access to PagerDuty and AWS S3, while support staff only gets Wikipedia and a calculator. The workflow checks each user's permissions in Port before letting the agent use any tools.
For the full guide with blueprint setup and detailed configuration, see RBAC for AI Agents with n8n and Port in the Port documentation.
The n8n workflow orchestrates the following steps:
⚠️ This template is intended for Self-Hosted instances only.
This 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 | Control AI agent tool access with Port RBAC and Slack mentions |
|---|---|
| Complexity | advanced |
| Nodes | 23 |
| Categories | Internal Wiki, AI Chatbot |
| Author | Port IO |
| Published | 23 Dec 2025 |
Use the JSON export at /data/workflows/12062/12062.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.
RBAC for AI agents with n8n and Port This workflow implements role based access control for AI agent tools using Port as the single source of truth for permissions. Different users get access to di...
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 Internal Wiki, AI Chatbot use case.