---
agentTools:
  projectIndex: https://developers.pipefy.com/llms.txt
---

# Publishing your App

Private apps, public apps, and what review needs from you

There are two ways to ship a Pipefy app, and only one of them needs us.

## Private apps — no review needed

A private app is visible only inside the organization it was added to. You don't need our approval, and you can do it yourself right now:

1. Go to [Apps in your developer settings](https://app.pipefy.com/developers/apps).
2. Click **Add new app**.
3. Enter the app's name and the URL of its `manifest.json`.

The app becomes available under the **Tools** menu in the top-right of the navbar, and on whichever surfaces its `features` declared. You must be an admin of the organization.

This is the right path for internal tools, integrations specific to your company, and anything you're still building. Most apps never need to be anything else.

## Public apps — submitted for review

A public app is available to every Pipefy organization, which is why it goes through review first. Submit it here:

**<https://app.pipefy.com/public/form/JgkrjL-O>**

### Before you submit

Have these ready — an incomplete submission is the most common reason for a delay:

* **A working, publicly reachable app.** The manifest URL must be live over HTTPS, and stay live. See the [manifest requirements checklist](https://developers.pipefy.com/docs/manifestjson#requirements-checklist).
* **Complete manifest metadata.** `name`, `short_description`, `description`, `icon`, `author` and at least one screenshot. These are what users see when deciding whether to install your app, and reviewers read them the same way.
* **A description of what the app does** and which Pipefy data it reads or writes.
* **A test organization or account** we can use to see the app working end to end.
* **A contact** for follow-up questions.

### What reviewers look at

* The app loads and works on every surface its manifest declares.
* It fails gracefully — no blank frames or silent errors when a request fails or a token is missing.
* It only reads and writes the data it needs. Apps run with the full permissions of the logged-in user, so scope matters. See the note on [Make API calls](https://developers.pipefy.com/docs/make-api-calls).
* Secrets are stored with `private` visibility, never `public`. See [Custom App Data](https://developers.pipefy.com/docs/store-retrieve-custom-data).
* The metadata above is accurate and the screenshots reflect the current app.

> 📘 Turnaround times
>
> We don't currently publish a service-level target for app review. If you need to plan around a launch date, say so in the submission and we'll come back to you with a timeline.

## After publishing

Your manifest is re-read whenever your app loads, so shipping a fix means deploying your own code — no resubmission, and no version bump on our side. That also means a broken deploy reaches all of your users immediately, so test before you ship.

If you change what your app *does* substantially — new features in the manifest, or new Pipefy data it touches — let us know through the same form.

## See also

* [Manifest reference](https://developers.pipefy.com/docs/manifestjson) — what has to be in your manifest
* [Introduction](https://developers.pipefy.com/docs/build-your-first-pipefy-app) — registering and hosting an app
* [Frequently Asked Questions](https://developers.pipefy.com/docs/frequently-asked-questions)