> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/workflow-builder/introduction/overview.md).

# Overview

## What are the steps to create a workflow?

Follow the steps below to configure a workflow for business processes using **One Resource’s Workflow Builder**:

* Identify the flow of business processes to automated.
* Determine where the process starts, ends and the sequence of steps in between.
* At every step of the workflow,
  1. Find out who is accountable and assign roles accordingly.
  2. Check if any conditions are to be applied for moving the processes along the workflow.
* Once you have your processes and their flow details, configure your workflow diagram easily in **One Resource's Workflow Builder** interface.
* Add notifications and reminders, if required, for the concerned stakeholders at any step(s) of the process.
* Test the workflow you created.

## What are the pre-requisites for creating a workflow?

1. The user must be logged into the **One Resource** platform.
2. The user creating the workflow must have administrative rights to access the **Workflow Builder**.
3. The roles and users that will participate in the workflow must be created in the system. Learn how to [<mark style="color:purple;">**create custom roles**</mark>](/user-management/managing-user-roles/creating-roles.md)
4. The form based on which the workflow is to be designed must be created in the system. learn how to [<mark style="color:purple;">**Create a form**</mark>](/form-builder/introduction.md)**.**&#x20;
5. The form based on which the workflow is to be created must contain the **Status** field. It is this field that will help identify the current stage of the task and set up the assignees for the form or task.

{% hint style="warning" %}
**Note**: *We cannot set up a workflow for a form that does not have a ‘**Status’** type field. The **Status** field is a simple dropdown-menu field where you can define the various stages of the workflow. Learn how to* [*<mark style="color:purple;">**add a status field**</mark>*](https://docs.senpiper.com/workflow-builder/introduction/pages/-MlTKz6Y8xUCmZEa9lxP#1.-status)&#x20;
{% endhint %}


---

# 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://docs.senpiper.com/workflow-builder/introduction/overview.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.