> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/run-operations/workflow-apps.md).

# Workflow apps

Use published Workflow apps to complete structured operational work without opening the Workflow builder.

Use a Workflow app when your organisation has turned a repeatable operational process into a structured operator experience.

The important thing is the business task: submit the information for a process, provide a document, work through a guided interaction, or start background execution. You do not need to understand the Workflow behind it.

![A published Workflow app before the operator submits the form.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2FCfUZfXX4nrFrAouc41FG%2Fworkflow-app-landing.png?alt=media)

## What you may see

Depending on how the Workflow was built, an app may let you:

* submit the information needed to start an operational process;
* provide documents or structured input;
* work through a guided interaction;
* trigger background work and receive the resulting output.

The exact fields, prompts and behaviour are specific to the process your organisation has published.

When a Workflow app shows a Request form beside a searchable PDF, supported document-derived fields can also highlight their matching source values on hover or keyboard focus. See [Requests](/run-operations/request-inbox.md#verify-request-fields-against-the-source-document) for the supported fields and current limits.

## What happens after you submit

The app starts the published Workflow. Some work may complete immediately. Other work may continue in the background, interact with connected systems, or later create a [Request](/run-operations/request-inbox.md) if a person needs to make a decision or provide additional information.

![The same published Workflow app after execution, showing the result and generated output file.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fvv67nCGAXWqGzQrVYFM3%2Fworkflow-app-run.png?alt=media)

If you need to understand how foreground and background work fit together, see [Humans, Agent and Workflows](/understand-lleverage/readme/humans-agent-and-workflows.md).

## If the app does not look like another app you have used

That is expected. Workflow apps are configurable. Different Projects can use different inputs, wording and execution paths even when they support similar business processes.

Focus on the operational task and the instructions in that specific app.

## Where to go next

* If the process later asks for your decision → [Requests](/run-operations/request-inbox.md)
* If the work is too variable for a fixed app → [Agent](/run-operations/agent.md)
* If you build or change the app → [Publish apps & APIs](/build-and-improve/automate/publish-apps-and-apis.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://docs.lleverage.ai/run-operations/workflow-apps.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.
