> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Respond to clicks, input, and time

> Use step triggers to make a captured experience respond to a viewer's actions.

A trigger waits for an event and then runs the actions you configure. Use it when the viewer's action is part of the story: selecting a control, entering a value, or waiting for a result. A visible guide can explain what to do; the trigger determines what happens when the condition is met.

## Choose the event

From a step's **+ Element** menu, open **Trigger** and choose the event that fits the experience:

| Trigger | Use it when | Check before publishing |
| - | - | - |
| Element trigger | A click on a chosen element should run an action. | The target is the control the instruction describes, and it remains available in the captured state. |
| Input trigger | A viewer should type or select a matching value in an interactive HTML field. | The target is an editable field in an HTML capture; input conditions do not run on image or video steps. |
| Timer trigger | An action should run after a pause on the step. | Give viewers enough time to read, and test what happens if they leave and return. |

Availability can depend on the selected step and whether the target can be picked. Choose the step and target first, then review the trigger's settings and actions in the editor.

## Match an input

For an input trigger, set **Match** to **Is exactly** or **Contains** and enter the **Value to match**. Capitalization and spaces must match. Dropdowns use the option's underlying value, which may differ from its visible label.

For example, in a fictional search flow, select the captured search field and match `late`. Tell the viewer what to enter, then configure the action that shows the filtered result. Test the matching value and a non-matching value in preview. An empty **Contains** value matches every change; an empty **Is exactly** value matches when the field is cleared. Enter an intentional value unless that behavior is what you need.

An input condition runs its actions once per visit when it matches. **Clear after matching** clears the field after an action succeeds; preview the result before enabling it.

## Set and test actions

Under **Then**, add the desired actions and destinations. Actions run in order and stop at the first successful navigation; later actions are fallbacks. Check the target step or flow and remove actions you do not intend to use.

A timer starts when the step opens. Leaving the step cancels it; returning starts a new wait. Test a full visit and an early exit. For a click trigger, test the target on the actual captured state, including after a screen edit or recapture.

Preview the full path from the preceding step, not just the trigger in isolation. If the viewer must type, give a clear instruction and a way to understand what happened. Publish the reviewed draft and test the shared version. See [Build and check a sandbox](https://docs.arcdemo.io/guides/sandbox.md) and [Review a demo before it goes live](https://docs.arcdemo.io/guides/review-and-publish.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.