Actions Library
Every step you can use in a test, organized by channel and by palette category, with parameters, JSON, and metrics.
An action (or step) is a single instruction inside a test: click a button, type text, verify an element, send a USSD code. A test is an ordered list of actions executed top to bottom on the device assigned to it.
The library is organized by channel, and inside each channel it mirrors the step palette you see in the product. A step that exists on two channels has one page per channel, so you always find it where you work.
Browse by channel
What each step page tells you
Every page follows the same structure, so you can scan the library like a reference:
- Parameters: each field as labeled in the builder, with its JSON name, default, and behavior.
- In the scenario JSON: a complete step object, ready to paste into a scenario.
- Results and metrics: what the step records when it runs (timing, status, screenshots, variables) and what flows to Analytics.
You can also list the available action types programmatically: run ktm tests action-types from the CLI, or call list_action_types from the MCP server.
What's next?
Last updated on