> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/start-a-workflow/run-from-a-button-or-list-action.md).

# Run from a button or list action

Use a component workflow when an app user starts the process. This guide applies to the builder's component **Actions** configuration.

## Run from a button

1. Select the button.
2. Open **Click action** in its Actions configuration.
3. Choose **Run Workflow** and configure the workflow.
4. Define the workflow's parameters and bind each input to the appropriate component value.
5. Test from the app with a known selected record.

{% @arcade/embed url="<https://app.arcade.software/share/2dlzfHAvIKSulhTj03j5>" flowId="2dlzfHAvIKSulhTj03j5" %}

## Run from a list action

Open the list component's action configuration and choose the relevant action. Lists include Table, Map, Kanban, Gallery, Timeline, and Calendar. Choose **Run Workflow** where the action offers it, then bind the values supplied by that action.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FFkHYw18EEIW4CbK5oA59%2Fszbdx.png?alt=media\&token=8293e5e1-3633-44bc-8ef3-3b0f17899084)

A row action and an action processing several selected records require different inputs. Inspect the available value and its type instead of assuming that a table's visible records equal its selected records. For bulk work, use [Process selected records](/workflow/practical-guides/process-selected-records.md).

## Run after another component action

Use a success or error callback when another action should start the workflow.

{% @arcade/embed url="<https://app.arcade.software/share/Adv4DcYOM8vgpRlNyRob>" flowId="Adv4DcYOM8vgpRlNyRob" %}

Select **Run Workflow** for the callback and specify the workflow.

{% @arcade/embed url="<https://app.arcade.software/share/eT6nO08NLTcYMIAterzU>" flowId="eT6nO08NLTcYMIAterzU" %}

See [component success and failure actions](/workflow/handle-outcomes/component-success-and-failure-actions.md) for execution-order considerations.

## Verify the binding

Test with two different fictional tickets. The input ID should change when the selected ticket changes. If the editor test works but the button does not, check the runtime binding and the selected row. See [inputs](/workflow/build-workflow-steps/pass-inputs-into-a-workflow.md) and [testing](/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/workflow/start-a-workflow/run-from-a-button-or-list-action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.