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.
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 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 if a person needs to make a decision or provide additional information.
If you need to understand how foreground and background work fit together, see Humans, Agent and Workflows.
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
If the work is too variable for a fixed app → Agent
If you build or change the app → Publish apps & APIs
Last updated
Was this helpful?