> 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/build-workflow-steps/add-and-configure-actions.md).

# Add and configure actions

In this section you will learn about the steps

An action performs a task such as reading data, updating a record, or navigating to an app page. A workflow step contains an action or a rule.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2Fq2OxoF34g39cTL5UMXB6%2Frhxdct.png?alt=media\&token=61714bd6-c763-4486-8609-db32937c2923)

## Add an action

1. Click **+** at the position where the step should run.
2. Choose the action.
3. For a data action, choose the resource, collection, and operation.
4. Configure required fields, filters, and record identifiers.
5. Bind dynamic fields to [workflow inputs](/workflow/build-workflow-steps/pass-inputs-into-a-workflow.md) or [earlier step outputs](/workflow/build-workflow-steps/use-step-outputs-and-return-results.md).
6. Test the step and inspect the result before adding a dependent step.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2Fj887KxqobIZ1szY1vCj4%2Fdhbf.gif?alt=media\&token=ce0bcba6-0692-4dee-a052-212da6e5ea0e)

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F8roXeEpMOKWtbOlinpyo%2Fetjzhcr.png?alt=media\&token=f56a16cf-c2c3-44bc-8529-199b45793bdc)

## Example: update a ticket

Choose the Tickets collection and its update operation. Bind the record ID to `ticket_id` and set `status` to an allowed value in that source.

Do not use a row's position as its record identifier. Confirm the operation targets the intended ID, particularly after sorting or filtering a list.

## Choose the right action

See the [action reference](/workflow/build-workflow-steps/add-and-configure-actions/action-reference.md). In-app actions, such as page navigation, belong to an interactive app context; do not assume they are meaningful in a background automation.

If a step fails, inspect its input and error before running it again. A test of a write action can change data. See [Test steps and complete workflows](/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/build-workflow-steps/add-and-configure-actions.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.