---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Manually capture steps

# Extend a desktop action by manually capturing steps in AI Desktop Actions {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read  
Extend the automation logic in a desktop action by manually capturing steps in AI Desktop Actions.

## Before you begin

To access the AI Desktop Actions functionality, perform the following steps:

* Enable AI Desktop Actions on your ServiceNow instance. For more information, see [Configure AI Desktop Actions](https://www.servicenow.com/docs/LQZ2W3lqdbqYawdiSsF7fw "You can enable the AI Desktop Actions application if you have the admin role.").
* Download the AI Desktop Actions installer to automate repetitive tasks across applications and systems. For more information, see [Download AI Desktop Actions installer for defined desktop actions](https://www.servicenow.com/docs/HMOiO3LL~jnNfzRsl6R8CQ "Download the AI Desktop Actions installer so that you can install AI Desktop Actions on your Windows machine for designing and running defined desktop actions.").
{#manual-create-desktop-action-ad__ul_urn_w5j_y2c}

Confirm that the following system requirements are met:

* Windows 11 operating system is used.
* A .NET 9.0 runtime v9.0.10 and .NET 9 Desktop Runtime v9.0.10 is installed.
* No extended monitors are connected.
* Theme must match between the systems used for recording and execution.
* Remote Desktop must be enabled on your machine and your account must be granted Remote Desktop access permissions before you start using the AI Desktop Actions Execution workspace.

{#manual-create-desktop-action-ad__ul_gcr_cv3_hhc}

Familiarize yourself with the Design workspace and Action recorder. For more information, see [AI Desktop Actions Design workspace](https://www.servicenow.com/docs/6rfd6i~s45rjn_fHUda_8w "The Design workspace is an interactive environment within AI Desktop Actions that enables you to create desktop actions by recording and configuring user interactions with desktop applications. The workspace provides a visual canvas where you can design multi-screen automation workflows that capture business processes across different applications.") and [Action recorder in AI Desktop Actions](https://www.servicenow.com/docs/CmxR01QlBtzsaiLYj7H5wQ "With Action recorder, you can capture steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on application elements as a reusable desktop action.").

Role required: sn_aia.admin

## About this task

Note:  
To create desktop actions with AI-assisted anchor validation and automatic screen context generation, use [Record with AI](https://www.servicenow.com/docs/1tmtj16vM~L0BJC4vjGuuA "Create desktop actions by recording steps with AI to automate repetitive tasks in AI Desktop Actions. AI validates anchor positions and generates screen contexts automatically after recording, reducing the risk of automation failures at runtime.") instead.

You can simulate a user interaction in an automation by manually capturing screens and defining steps.

Using the controls in the window, you can capture an area of an application window. You can then set one or more anchors, and define steps that represent the user interactions in that window.

* Anchor: Anchors help specify the target area for the interaction by defining a static area from which steps can be defined at a relative distance.
* Step: Steps are your sequential interactions of type click, select, type, scroll, and more.

{#manual-create-desktop-action-ad__ul_sy4_bjd_3hc}  
Note:  
If your automation requires manual inputs, such as entering an OTP or CAPTCHA, you must provide instructions to the AI Agent to wait for the user input during execution. Otherwise, the automation can't proceed.

## Procedure

1. From your Windows system, launch the AI Desktop Actions application.
2. On the login page, in the Add ServiceNow URL field, enter the ServiceNow instance URL.  
   For example, https://\<instance name\>.service-now.com.  
3. Select Proceed.
4. Log in to your ServiceNow account by entering your user name and password.  
   Your must have the sn_aia.admin role.

5. **Optional:** On the onboarding journey modal, complete the onboarding and select Get started.  

   If you launch the AI Desktop Actions for the first time, the onboarding journey widget appears. You can select Don't show me again to hide the widget the next time you launch AI Desktop Actions or Skip intro to skip the onboarding.
6. On the AI Desktop Actions home page, select an existing desktop action.  

   The Design workspace is displayed.
   {#manual-create-desktop-action-ad__ad-create-desktop-actions}
{#manual-create-desktop-action-ad__ad-create-desktop-actions}
7. Capture screens.
   1. In the Design tab, select the Capture Options icon ![](). {#manual-create-desktop-action-ad__ad-manual-capture-step-1}
   {#manual-create-desktop-action-ad__ad-manual-capture-step-1}
   2. Select Manual capture.  

      You can also extend the desktop action logic using the Record with AI (Recommended) or Auto capture with recorder options. For more
      information, see [Automate repetitive tasks by recording steps with AI in AI Desktop Actions](https://www.servicenow.com/docs/1tmtj16vM~L0BJC4vjGuuA "Create desktop actions by recording steps with AI to automate repetitive tasks in AI Desktop Actions. AI validates anchor positions and generates screen contexts automatically after recording, reducing the risk of automation failures at runtime.") and [Automate repetitive tasks by auto-capturing steps in AI Desktop Actions](https://www.servicenow.com/docs/WtTq1gWDHHfpG2wHOQG4Cw "Create desktop actions by auto-capturing steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on the application elements as a reusable desktop action of type on-screen task.").

      The AI Desktop Actions window is minimized and the Capture panel is launched.
      {#manual-create-desktop-action-ad__ad-manual-capture-step-2}
   {#manual-create-desktop-action-ad__ad-manual-capture-step-2}
   3. Open the applications that you want to automate steps for.
   4. Capture the area of the external application's window by selecting the Select icon on the Capture panel or pressing the <kbd class="ph userinput">Ctrl + Shift + C</kbd> on the keyboard.  
      Note:  
      If the <kbd class="ph userinput">Ctrl + Shift + C</kbd> shortcut conflicts with another application on the your machine, such as Zoom, then you must use the Select button to initiate manual screen capture.
      For example, you can capture the area surrounding a button or a text field in a web browser. The cursor icon changes to the icon. {#manual-create-desktop-action-ad__ad-manual-capture-step-3}
   {#manual-create-desktop-action-ad__ad-manual-capture-step-3}
   5. Drag the icon and select the required screen area.  
      When you leave the icon, the selected area is captured as a screenshot in the Design workspace.

      If you aren't satisfied with the captured screen, you can recapture the screen area by selecting the Capture image icon ![]().
      {#manual-create-desktop-action-ad__ad-manual-capture-step-4}
   {#manual-create-desktop-action-ad__ad-manual-capture-step-4} {#manual-create-desktop-action-ad__substeps_rh5_k1s_ghc}
8. Insert anchors.
   1. Insert an anchor on the captured screen by selecting the Add anchor icon .  
      Note:  
      If two applications in the frame have similar logos or visual elements, verify that the anchor position is unique to the target application to avoid incorrect element identification during automation.

      An anchor is a reference point on the screen that helps the automation identify and interact with a nearby UI elements. During execution,
      the system uses computer vision to locate the anchor and then identifies the UI elements at a related distance from the anchor. Anchors improve the stability and accuracy of steps when the target element's
      location may shift or when the UI layout varies across
      sessions.  
      Note:  
      Don't use dynamically changing UI elements as anchors. If an element changes its color, text, or state after an action (for example, after a click), select a different anchor that remains static on the screen.
   2. Move the anchor to a part of the captured image that won't change.  
      For example, move the anchor to a title or field label.

      If the area under the anchor doesn't exactly match the corresponding area of the captured image, the anchor isn't recognized, and the steps aren't
      performed as intended. Choose a static area of the image for setting your anchor.

      You can add multiple anchors on each screen. Multiple anchors let you define the geographical relationship between
      anchor and target with greater accuracy when targeting different locations in the image.
   {#manual-create-desktop-action-ad__substeps_xt2_r1s_ghc}
9. Configure the steps.
   1. From the Anchor control menu, select the Add step icon .
   2. Select the type of step to perform for this step from the contextual menu.  
      {#manual-create-desktop-action-ad__table_vtf_jds_ghc__entry__4}

      | Goal | Step | Type | Example |
      |-|-|-|-|
      | Enter text in a field | Set Text | Input | Enter any text data such as a user name, an address, a survey response, or in any situation where text entry is accepted. Note: If you set a static value for this field, the automation uses it during execution and doesn't prompt you for input from the ServiceNow Otto panel. |
      | Simulate a mouse click | Click | Input | Click a button, open a menu, or perform any step typically performed by a mouse click. |
      | Simulate an alternative mouse action (for example, right-click, drag, scroll, or paste) | Mouse Click | Input | Perform various mouse device actions, such as right-click and select an object or scroll on a web page. |
      | Simulate a key press or a key function | Send Keys | Input | Perform keyboard shortcuts, such as copying text by entering <kbd class="ph userinput">Ctrl + C</kbd> on fields and elements. Note: If you set a static value for this field, the automation uses it during execution and doesn't prompt you for input from the ServiceNow Otto panel. |
      | Capture text from a window or web page | Get Text | Output | Receive text from the source area. |
      | Capture a table | Get Table | Output | Receive table from the source area when the text is in the table format. Note: For the step to capture table data successfully, the data must already be in the table form. The step can't convert ordinary text to table data. |
      | Read text from an image | OCR Read Text | Output | Recognize text from images and return it in the standard text format. |
      [Table 1. Description of the actions]

      {#manual-create-desktop-action-ad__table_vtf_jds_ghc}

      You can add multiple steps representing your automation steps.
   {#manual-create-desktop-action-ad__substeps_hng_klr_khc}
10. Configure the properties for added screens, anchors, and steps in the Properties panel.  
    For more information, see [Screen, anchor, and step properties in AI Desktop Actions](https://www.servicenow.com/docs/dSXSRZZenXx3T6SkN4PdEQ "Learn about the properties of screens, anchors, and steps. There are multiple types of steps and each step type has distinct properties. You can update the properties to modify the behavior of the steps.").
11. **Optional:** Modify the auto-generated names for all added screens, anchors, and steps.  
    You can modify the auto-generated names following these naming guidelines.
    * Name fields must not be empty.
    * Name fields must contain only alphanumeric characters. Spaces and special characters are not permitted.
    * Each name must be unique at its respective parent level.
      * Each screen must have a unique name at the desktop-action level.
      * Each anchor must have a unique name at the screen level.
      * Each step must have a unique name at the anchor level.
      {#manual-create-desktop-action-ad__ul_om5_wnz_3hc}
    {#manual-create-desktop-action-ad__ul_sjm_tnz_3hc}

## What to do next

1. Configure the details of your desktop action. For more information, see [Add details to desktop actions in AI Desktop Actions](https://www.servicenow.com/docs/abGyi9FA~H5tPDnbFqL23Q "Add desktop action details, such as name, description, and associated applications, and review inputs and outputs.").
2. Test and activate the desktop action so that it can be added as a tool to AI agents. For more information, see [Test and activate a desktop action in AI Desktop Actions](https://www.servicenow.com/docs/TyomdOuatqEyyW~mM3ZA8g "Test the desktop action and then activate it so that it’s available as a tool in the AI Agent Studio. You can add this tool to the AI agents that execute desktop actions in your desktop environment.").
3. Add the desktop action as a tool to AI agents in AI Agent Studio. For more information, see .
{#manual-create-desktop-action-ad__ol_slm_313_hhc}
**Related concepts**   

* [AI Desktop Actions Design workspace](https://www.servicenow.com/docs/6rfd6i~s45rjn_fHUda_8w "The Design workspace is an interactive environment within AI Desktop Actions that enables you to create desktop actions by recording and configuring user interactions with desktop applications. The workspace provides a visual canvas where you can design multi-screen automation workflows that capture business processes across different applications.")
* [Examples of creating desktop actions](https://www.servicenow.com/docs/5w2cJazGasMFMYp0gR8LIQ "Learn the key concepts and workflow for creating end-to-end desktop actions and building automations for your desktop environments.")
* [Examples of executing desktop actions using AI agents](https://www.servicenow.com/docs/Iu8_QEf44OhoKTJlVK83IA "These examples explain how to trigger AI Agents that execute automations you designed using desktop actions. The following topics walk you through the end-to-end execution flow so you understand how AI-driven execution works in your desktop environment.")  
**Related tasks**   

* [Automate repetitive tasks by auto-capturing steps in AI Desktop Actions](https://www.servicenow.com/docs/WtTq1gWDHHfpG2wHOQG4Cw "Create desktop actions by auto-capturing steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on the application elements as a reusable desktop action of type on-screen task.")  
**Related reference**   

* [Screen, anchor, and step properties in AI Desktop Actions](https://www.servicenow.com/docs/dSXSRZZenXx3T6SkN4PdEQ "Learn about the properties of screens, anchors, and steps. There are multiple types of steps and each step type has distinct properties. You can update the properties to modify the behavior of the steps.")  
**Related topics**   

* 

