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

# Deploy Apps

Apps are the simplest way to put your agents to work. You build the logic in Studio, then deploy it as an app that anyone can use, no technical knowledge needed.

Your colleagues, clients, or teammates just open the app, provide their inputs, and get results. You control the quality and consistency; they just prompt and go.

## Why Apps

* **Empower your team.** Anyone in your workspace can get the outputs they need, without understanding how the agent works, which models it uses, or how the flow is structured. They just open the app, provide inputs, and get results.
* **Guarantee consistency.** The logic, models, and context are baked into the agent. Every run follows the same workflow you designed.
* **Speed up your own work.** Even as the agent creator, you don't always want to dive back into Studio. Apps give you a fast lane to run your own agents with a clean, focused interface.
* **Remove yourself as a bottleneck** and stop being the person who "runs the AI tool."

## The App experience

You can access Apps directly from your home:

{% embed url="<https://screen.studio/share/IkcMZXJ6>" %}

When someone opens your app, they see a clean interface: a title, a description, and the inputs you've defined.

They fill in what's needed (a prompt, an image, or both), hit **Launch**, and the agent does the rest.

Results appear directly in the app. Users can review outputs, download what they like, or run the app again with different inputs.

## How to create an App

### Quick tutorial

{% embed url="<https://screen.studio/share/O14AryMG>" %}

### Step by step

#### 1. Build your agent in Studio

Start from scratch or duplicate an existing agent. Connect your nodes, pick your AI models, and test until you're happy with the results.

Not sure how Studio works? Check out the [Studio](broken://pages/g1uXQ3dp6DlnKTLOKjvf) section.

#### 2. Click "Deploy as app"

When your agent is ready, click **Deploy as app** in the top-right corner. This opens the deployment flow.

<figure><img src="/files/hbBtksnAYIzJBRKB4rVR" alt="" width="375"><figcaption></figcaption></figure>

#### 3. Buid the app form

Choose which inputs your app will ask users for. These are pulled from the user prompt nodes in your agent. You can rename them, make some optional and add placeholder text to guide users.

<figure><img src="/files/UR3IbjXvvtglfH6egvHv" alt="" width="375"><figcaption></figcaption></figure>

#### 4. Pick your outputs

Select which outputs users will see when the app finishes running. You can include all generation nodes or just the ones that matter most.

<figure><img src="/files/XrcC8Y4R0EeMzMcKKN29" alt="" width="375"><figcaption></figcaption></figure>

#### 5. Set app details and visibility

Give your app a name and description.&#x20;

<figure><img src="/files/k6vMa3pXGqFSGOoxNEKx" alt="" width="375"><figcaption></figcaption></figure>

Then choose who can access it:

* **Private** — Only you can use it.
* **Workspace** — Anyone in your workspace can use it.
* **Shared** — Anyone with the link can use it.

Hit **Deploy** and your app is live.

<figure><img src="/files/yQSlSKx76uts8UxJfJRa" alt="" width="375"><figcaption></figcaption></figure>

### Build a custom form

Shape the form around the inputs that matter. Add dropdowns for text, a list of visuals to pick from, so whoever runs the app hands over exactly what your agent needs, nothing more.

{% embed url="<https://screen.studio/share/w0Ayr0NE>" %}

A few forms teams are building: a dropdown to ship localized creative in one run, a media slot for product packshots, or preset directions that keep non-technical teammates on-brand.

While defining inputs, click **Configure** on any field to set its options:

{% embed url="<https://screen.studio/share/2u3eyL3v>" %}

***

### Managing your apps

Your apps appear in the **Quick create** section on your home screen, under "My Apps." Pletor's pre-built apps are available under "Pletor Apps."

To update an app, go back to Studio, make your changes, and redeploy. The app always reflects your latest published version.


---

# 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:

```
GET https://docs.pletor.ai/automate/apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.