> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/workflows.md).

# Workflows

Set required steps for field employees when they complete a work order in the app.

**Workflows** helps you standardize how field employees complete work orders in OutSmart.

Use this section to understand how workflows work, create them, choose the right steps, validate the setup, and use them in the app.

{% hint style="info" %}
Workflows is a **Power-Up**. Power-Ups are available from **Boost** onward. Availability can also depend on your license and configuration.
{% endhint %}

### In this guide

* [**Introduction to Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md)
* [**Create and manage workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/create-and-manage-workflows.md)
* [**Workflow step types**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-step-types.md)
* [**Validate workflow setup**](/marketplace-packages-and-power-ups/power-ups/workflows/validate-workflow-setup.md)
* [**Workflow settings and device policies**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-settings-and-device-policies.md)
* [**Use workflows in the mobile app**](/marketplace-packages-and-power-ups/power-ups/workflows/use-workflows-in-the-mobile-app.md)

### What you do with Workflows

* standardize work order completion
* require steps like timers, materials, photos, forms, and signatures
* guide employees step by step in the app
* prevent incomplete work orders from being sent too early

### Recommended order

1. Start with [**Introduction to Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md).
2. Then [**create and manage workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/create-and-manage-workflows.md).
3. Next review the available [**workflow step types**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-step-types.md).
4. Then check [**validate workflow setup**](/marketplace-packages-and-power-ups/power-ups/workflows/validate-workflow-setup.md) and [**workflow settings and device policies**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-settings-and-device-policies.md).
5. Finish with [**use workflows in the mobile app**](/marketplace-packages-and-power-ups/power-ups/workflows/use-workflows-in-the-mobile-app.md).

### Webinar

Prefer to follow the process visually? Watch the webinar about Workflows.

{% embed url="<https://youtu.be/RuMcDBOZ8D8>" %}

### Related topics

* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)
* [**OutSmart Marketplace**](/marketplace-packages-and-power-ups/marketplace.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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/workflows.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.