> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/defining-walkthrough-step/configuring-actions-buttons-within-a-walkthrough-step.md).

# Configuring actions buttons within a walkthrough step

Action buttons trigger workflows when clicked on by users. Use them to automatically deploy campaigns or remote actions directly in your Guides.

<figure><img src="/files/jBq1L91xKCR1b2rmdhii" alt=""><figcaption></figcaption></figure>

## Adding Action buttons

To add an action button to a step from the Adopt Editor:

1. Open the Step **properties** and access the **Appearance** tab.
2. Enable one of the optional buttons.
3. Click the **settings wheel** on the enabled button.
4. Under **Action type**, select **Launch workflow**.
5. Select a workflow from the list. There is a search bar for ease of use.
6. Under **Label**, define a label for the action button.
7. **Save** your changes.

<figure><img src="/files/sadV5uBFcjw571cUOyR1" alt=""><figcaption></figcaption></figure>

## Limitations

Some limitations apply when linking a workflow to an action button:

For campaigns:

* The campaign can only contain a single-answer question.
* The **Trigger** method must be set to **Workflow**.
* Consider setting the **Priority** to **Urgent** and/or **Mandatory** to avoid delays. If not set, users may experience delays of up to 30 seconds.

For remote actions:

* The user cannot modify input parameters.
* The **allow the user to enter a custom value** setting must be disabled.

For workflows:

* The workflow must be enabled.
* The workflow cannot have input parameters.
* The **Trigger** method must be set to **Manual**.
* The workflow must target **Users** or **Devices**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/defining-walkthrough-step/configuring-actions-buttons-within-a-walkthrough-step.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.