YAADMINCurrent runtime behavior#
YAADMIN can select registered tools, resolve supported targets, construct execution requests and combine multiple tool calls during a chat turn. Action1 exposes library/inline scripts and generic per-endpoint batch execution. Live Activity and results make processing visible.
- Request
- Resolve real targets
- Select tools
- Permission / approval
- Execute
- Inspect results
Automatic versus approved actions#
Routine operations can execute automatically when their request policy and RBAC allow it. Consequential requests can pause for approval. Inline PowerShell requires an explicit routine or critical impact; library scripts use policy-based approval.
Batches#
Generic fan-out/fan-in supports concurrency, fail_fast and an optional overall timeout. Each item remains an ordinary execution request with its own permissions/approval/result. Operation bounds are not licensing device quotas.
Architectural direction#
Not a verified scheduler#
No schedule syntax, scheduler UI/API, native n8n module or visual workflow editor was found. An independent MCP/custom module may expose workflow functionality, but that depends on its actual tool implementation. Do not treat saved snippets as scheduled jobs.
Read Action1, Custom modules and Approvals.