> 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/workflow-step-types.md).

# Workflow step types

Workflows support multiple step types.

Each step controls one part of the work order process.

### Information steps

Use these steps to show or update existing work order data:

* **Customer**
* **Work details**
* **Schedule**
* **Resources**
* **Object**

### Registration steps

Use these steps to add data during the job:

* **Work description**
* **Internal memo**
* **Comment**
* **Picture**
* **Material**
* **Hour**
* **Free fields**

### Form and document steps

Use these steps when extra input is required:

* **Forms**
* **Predefined form**
* **Documents**
* **Email**
* **History**
* **Overview**

### Completion steps

Use these steps near the end of the workflow:

* **Work status**
* **Job completed**
* **Signature**
* **Send**

### Timer steps

Use **Start** and **Stop** timer steps to track travel time or working time.

Place them in the correct order so the app can validate them.

### Common step examples

#### Customer

Use the **Customer** step to let employees verify customer information before work starts.

Depending on device settings, employees may only view this data or edit it.

#### Picture

Use the **Picture** step when photos are required.

You can use it for before and after photos, proof of work, or site documentation.

#### Signature

Use the **Signature** step to capture customer approval.

This step is often one of the last steps in the workflow.

#### Send

Use the **Send** step to finish the workflow and send the work order back to the office.

This step belongs at the end of the sequence.

### Choosing the right steps

Choose steps based on the process you want to enforce.

A simple workflow often includes customer details, a timer, materials, photos, a signature, and send.

### Frequently asked questions

<details>

<summary>Can I use the same step type more than once?</summary>

Yes.

For example, you can use multiple picture or comment steps.

</details>

<details>

<summary>Do I need every step type in one workflow?</summary>

No.

Use only the steps that support your process.

</details>

<details>

<summary>Should every workflow end with Send?</summary>

Yes.

The send action closes the workflow and completes the work order process.

</details>

### Related topics

* [**Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows.md)
* [**Create and manage workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/create-and-manage-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/workflow-step-types.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.