Agent Access Control Template
Configured with Agent, Airtable, Execute Workflow Trigger, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Data store
- AI & models
- Code
- Trigger
- Transform
- Integration
- Web / API
- Subworkflow
- Routing
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Check permissions | Code | Code | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Set input | Transform | Edit Fields | See node parameters |
| Get user permissions | Data store | Airtable | search |
| When Executed by Another Workflow | Trigger | Execute Workflow Trigger | See node parameters |
| Settings | Transform | Edit Fields | See node parameters |
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Simple Memory1 | Data store | Memory Buffer Window | See node parameters |
| Check permissions1 | Code | Code | See node parameters |
| list_granted_roles | Code | Tool Code | See node parameters |
| list_allowed_tools | Code | Tool Code | See node parameters |
| calculator | Integration | Tool Calculator | See node parameters |
| Wikipedia | Integration | Tool Wikipedia | See node parameters |
| get_coordinates | Web / API | Tool Http Request | See node parameters |
| get_weather | Web / API | Tool Http Request | See node parameters |
| weather_agent | Subworkflow | Tool Workflow | See node parameters |
| Weather Agent | AI & models | Agent | See node parameters |
| Unknown user | Routing | If | See node parameters |
| Reply: unknown user | Messaging | Telegram | See node parameters |
| Reply with results | Messaging | Telegram | See node parameters |
| Main Agent | AI & models | Agent | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
airtableTokenApiopenAiApitelegramApi
Workflow notes
Choose Base
Choose Base
Copy this Airtable Template into your workspace and select that Base here
Choose workflow
Choose workflow
Select the current workflow as the workflow that should be called
Sticky Note2
Uses list of allowed tools gathered from Airtable to check for permissions and replaces denied tools with a fixed instruction to return a message to the user.
Sticky Note3
Tools can also be connected without a permission check
Sticky Note4
Main agent with the instruction to always use the connected tools instead of general knowledge
Sticky Note5
Collects input and formats it using required keys
Sticky Note7
Collects and formats input from parent workflow / agent
Sticky Note8
Uses the same technique as the main agent to check for permissions using the same parameters which were passed to this sub-agent.
Sticky Note9
Sub-agent with specific role to handle weather information. Also having the instruction to strictly only use the connected tools.
Sticky Note6
Be aware, that previous responses may still exist after permission changes
Sticky Note10
Uses different session ID (suffix), since every agent needs its own memory
Sticky Note11
Listens to messages directly sent to the bot
Sticky Note12
Checks if the user was found in Airtable
Agent Access Control Template
Agent Access Control Template
Purpose and structure
This folder contains the Agent Access Control Template workflow. Its executable nodes use agent, airtable, code, executeWorkflowTrigger, if, lmChatOpenAi, memoryBufferWindow, set, telegram, telegramTrigger, toolCalculator, toolCode, toolHttpRequest, toolWikipedia, toolWorkflow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Telegram Trigger, When Executed by Another Workflow
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/1856_Telegram_Stickynote_Automation_Webhook.json MIT; preserve source notices.