---
title: Actions Library
description: "Every step you can use in a test, organized by channel and by palette category, with parameters, JSON, and metrics."
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

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

<Columns cols={2}>
  <Card title="Web" icon="globe" href="/tests/actions/web/overview">

    Browser tests: interactions, email and SMS retrieval, verifications, navigation

</Card>
  <Card title="Smartphone" icon="mobile-screen" href="/tests/actions/smartphone/overview">

    Native Android and iOS apps: touch interactions, app management, keyboard

</Card>
  <Card title="API" icon="code" href="/tests/actions/api/overview">

    HTTP steps you add inside web and smartphone tests

</Card>
  <Card title="SIMs" icon="sim-card" href="/tests/actions/cellular/overview">

    Real SIM cards: USSD, SMS, voice calls, and data measurements

</Card>
</Columns>

## 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](/cli/commands/tests/action-types) from the CLI, or call [list_action_types](/mcp/tools/test-management/list_action_types) from the MCP server.

## What's next?

<Columns cols={2}>
  <Card title="Web steps" icon="globe" href="/tests/actions/web/overview">

    The full web palette at a glance

</Card>
  <Card title="Test builder" icon="hammer" href="/tests/builder">

    How steps are added and configured

</Card>
</Columns>