> 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/forms/use-forms-with-workflows.md).

# Use Forms with workflows

Forms work well inside workflows.

This makes sure employees complete the right form at the right step in the process.

### Why combine Forms and workflows

This setup helps when you want to:

* enforce a fixed work sequence
* reduce missed information
* keep the process consistent across the team

{% stepper %}
{% step %}

### Open the workflow

Go to the workflow you want to edit.
{% endstep %}

{% step %}

### Add a form step

Add the workflow step type that uses a form.
{% endstep %}

{% step %}

### Select the form

Choose the form that should be completed in that step.
{% endstep %}

{% step %}

### Save the workflow

Save the workflow.
{% endstep %}

{% step %}

### Test the flow in the app

Open a work order that uses the workflow.

Check that the form appears at the right moment.
{% endstep %}
{% endstepper %}

### FAQ

<details>

<summary>Why use a form in a workflow instead of only linking it to a work order?</summary>

A workflow makes the form part of a fixed sequence.

</details>

<details>

<summary>Can I add more than one form step to a workflow?</summary>

Yes.

That depends on how your workflow is designed.

</details>

<details>

<summary>Should I test the workflow in the app?</summary>

Yes.

Always test the full employee flow before rollout.

</details>

### Related topics

* [Link forms to work orders](/marketplace-packages-and-power-ups/power-ups/forms/link-forms-to-work-orders.md)
* [Workflows](/marketplace-packages-and-power-ups/power-ups/workflows.md)
* [Workflow step types](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-step-types.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/forms/use-forms-with-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.