> 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/create-and-manage-workflows.md).

# Create and manage workflows

You create and manage workflows in the BackOffice.

Each workflow defines the steps employees follow in the mobile app.

### Before you start

Make sure the **Workflows** Power-Up is available in your environment.

You also need a clear list of the work types that should use the workflow.

### Create a workflow

{% stepper %}
{% step %}

### Open Workflows

Go to **Settings** → **Workflows**.

You now see the workflow overview.
{% endstep %}

{% step %}

### Add a workflow

Click **Add**.

Enter a clear name for the workflow.
{% endstep %}

{% step %}

### Select the work types

Choose one or more **work types**.

These work types determine when the workflow is used.
{% endstep %}

{% step %}

### Add the steps

Add the steps employees must complete.

Examples are customer details, timers, materials, forms, pictures, signature, and send.
{% endstep %}

{% step %}

### Set the order

Place the steps in the correct order.

The app follows this sequence.
{% endstep %}

{% step %}

### Save the workflow

Click **Save**.

The workflow is now available for matching work orders.
{% endstep %}
{% endstepper %}

### Manage an existing workflow

You can open an existing workflow and change:

* the name
* the linked work types
* the order of the steps
* the step settings

Changes apply to work orders that use the updated workflow after synchronization.

### Good setup practices

* keep workflows short and predictable
* group steps in the order employees work on site
* end the workflow with a **Send** step

{% hint style="info" %}
If employees do not see a new workflow right away, let them synchronize the app.
{% endhint %}

### Frequently asked questions

<details>

<summary>Can I link one workflow to multiple work types?</summary>

Yes.

A single workflow can be linked to multiple work types.

</details>

<details>

<summary>What happens if a work type has no workflow?</summary>

That work order opens without a workflow.

Employees can still complete it without guided steps.

</details>

<details>

<summary>Can I edit a workflow later?</summary>

Yes.

You can update workflows whenever your process changes.

</details>

### Related topics

* [**Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows.md)
* [**Introduction to Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.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 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/workflows/create-and-manage-workflows.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.