> 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/overview.md).

# Overview: workflows and automations

Automate business processes with triggers, actions, and rules.

Use a workflow to run defined steps: read data, check a condition, update a record, and show the result. Start with [Build your first workflow](/workflow/build-your-first-workflow.md) to pass a ticket ID from a button into an update action.

## Functions and automations

Open **Add Function** in the Workflows area to choose **Workflow Builder** (no-code) or **Write Code** (TypeScript). Build the logic first, then attach triggers to turn it into an automation. See [Functions and automations](/workflow/functions.md).

## Choose where the process starts

| You want to…                                                     | Start here                                                                                               | Configure it in                       |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| Run steps when an app user clicks a button or uses a list action | [Button and list actions](/workflow/start-a-workflow/run-from-a-button-or-list-action.md)                | The component's Actions configuration |
| Run work at a regular interval                                   | [Scheduled automation](/workflow/start-a-workflow/run-on-a-schedule.md)                                  | Automation                            |
| Respond to an HTTP event from another service                    | [Incoming webhook](/workflow/start-a-workflow/receive-an-incoming-webhook.md)                            | Automation                            |
| Require a person to approve an action                            | [Approval process](/workflow/practical-guides/create-an-approval-process.md)                             | The button's approval configuration   |
| Generate workflow steps from a description                       | [Generate with AI](/workflow/workflows-and-ai/generate-a-workflow-with-ai.md)                            | Ask AI in the workflow builder        |
| Let an agent interpret input during a run                        | [Run an agent in a workflow](/ai-agents/run-agents-in-apps-workflows-and-tasks/workflows-with-agents.md) | An agent step within the workflow     |

Component workflows can use values from the app. Background automations need their own trigger inputs or data queries; do not assume a selected row or visible component is available.

## Learn in order

1. [Build and test a first workflow](/workflow/build-your-first-workflow.md).
2. [Pass inputs](/workflow/build-workflow-steps/pass-inputs-into-a-workflow.md) and [use step outputs](/workflow/build-workflow-steps/use-step-outputs-and-return-results.md).
3. Add [conditions](/workflow/build-workflow-steps/add-conditions-and-branches.md) or an [iterator](/workflow/build-workflow-steps/process-multiple-records-with-iterators.md).
4. [Test the normal, empty, and failure cases](/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.md).
5. Use [troubleshooting](/workflow/test-and-troubleshoot/troubleshoot-common-problems.md) when a step does not produce the expected result.

The examples use fictional Tickets records. Use your own field names and allowed status values when adapting them. Guides that show component Actions, list actions, or task queues apply to the builder interface containing those controls.


---

# 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/overview.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.