The **Workflow** workspace defines the logic your app runs on a server, as a sequence of steps you can inspect.

Use Mockup for what people see. Use Workflow for what happens after an action, such as a form submission.

## Where to find it

Open an app from **Your Apps** on the Studio home page. Select **Workflow** in the top-center tab bar, between **Mockup** and **Data Model**.

## How steps work together

A workflow starts with a trigger. Each step does a job and passes data to the next step.

The [Orbit workflows overview](https://orbitapps.io/platform/workflows) describes these building blocks:

| Step | Role |
| --- | --- |
| Trigger | Starts the workflow on a schedule, a link click, or a form submission |
| Agent | Gives a task to an AI model with your data as context |
| Branch | Chooses a path based on a condition |
| Integration | Connects to another service, such as Resend for email |
| Code | Applies a custom rule |
| Data | Reads or writes the app database |

A workflow and a page can use the same records. The [Data Model workspace](/features/data-model-workspace) describes those records and their relationships.

## Follow one request through the logic

For example, consider a client request app. The following names and rules are examples, not a built-in workflow:

- A form submission starts the workflow.
- A Branch step checks whether the request has a title.
- A Data step saves a valid request.
- An Integration step sends a receipt through a configured email service.

The form belongs to the page. The decision, saved request, and email belong to the workflow logic.

The form, saved request, and email are separate results. A form that looks correct does not prove that the request was saved or the email reached its recipient.

## What simulation shows

**Simulate** runs a workflow on example data. You can open a step to inspect its inputs, output, and duration.

In this example, a simulation could show whether the title reaches the Data step and what result reaches the Integration step. A request without a title would exercise the Branch step's other path.

Simulation helps you inspect the logic. It does not replace a test through the live app with the accounts and services people will use.

## What runs after launch

The live workflow runs on a server, even when your browser is closed. Closing Studio does not stop the app's server-side logic.

Before people depend on the workflow, [test the app before launch](/guides/review-an-app-before-launch). Check the saved record and any external result separately.

For this example, a live test checks two separate results. The saved request remains available after reopening the app, and the receipt arrives in the recipient's inbox.