Operator — ActionJail Scenarios Hub
A page for operators working with custom actions in ActionJail. Here you will find instructions for creating new actions, editing existing ones, cloning templates, and organizing the action library. Each instruction will help you quickly complete the required task with minimal effort.
Quick Overview
High-Level Goals and Scenarios
Creating and Launching New Actions
Goal — quickly add an action that performs the required business logic.
- Create and maintain an action (Administrator) — go through the 5-step wizard, update code, config, and UI schema. → ./how-to/admin-manage-actions.md
Maintaining the Action Library
Goal — keep action versions up to date without chaos.
- Clone an action — create a copy of an existing one with a new system ID. → ./how-to/clone-action.md
- Delete an action — safely remove an unnecessary action from the list. → ./how-to/admin-manage-actions.md
Navigation and Search
Goal — quickly find the needed action among groups.
- Find an action in the list — filter by group or name. → ./how-to/filter-search-actions.md
Integration into Scenarios
Goal — use an action in a bot or process with an external API.
- Connect an action to a scenario (Integrator) — add a scenario step, pass parameters, and handle errors. → ./how-to/integrator-embed-actions.md
Actions Reference
Goal — find the needed standard action and understand its parameters.
- Actions Reference — complete reference for all 98 standard actions with description, configuration, and return values. → ./reference/actions-reference.md
Where to Work in the Interface
ActionJailmodule:Apps → ActionJail— library of all actions,Add new actionbutton, group lists.- Action creation/editing wizard: sequence of steps
Information → Code → JSON config → UI schema → Documentation.