# Beginner Q - "publish" an internal app for Make.com?

**URL:** <https://devforum.zoom.us/t/beginner-q-publish-an-internal-app-for-make-com/125286>\
**Category:** Zoom Apps\
**Created:** [January 25, 2025, 2:58pm UTC](https://devforum.zoom.us/t/beginner-q-publish-an-internal-app-for-make-com/125286 "2025-01-25T14:58:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthew5](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@matthew5](https://devforum.zoom.us/u/matthew5)\
**Post date:** [January 25, 2025, 2:58pm UTC](https://devforum.zoom.us/t/beginner-q-publish-an-internal-app-for-make-com/125286/1 "2025-01-25T14:58:52Z")

</div>

Hi there! What is best practice on creating/“publishing” an app that will only ever be internal-only? It is for an oauth connection to [Make.com](http://Make.com). I tried to build an internal app with the new build flow but am confused by the draft/beta test terminology.

Here’s what I did; is there anything else I’m missing before I can consider it “done”?

- Marketplace → Develop → Build App → General app,
- Set admin-managed app, chose meeting and webinar surface, then set scopes
- In the “Production” tab, I put in the [Make.com](http://Make.com) OAuth redirect URL and OAuth allow list domains
- I used the client id and secret (from the Production tab) to authenticate with [Make.com](http://Make.com)

My stuff works in [Make.com](http://Make.com), but on the Zoom Build page it shows the app is “draft”, and within the production tab of the app it shows “ready for local test”. This seems like an unfinished state to leave an internal app in.

This app should not be discoverable to any users in the Zoom organization, it’s only for admin server side in our many [Make.com](http://Make.com) automations.

I tried using the server-to-server app prior to this, but it can’t directly authenticate with Make because they require going through the user oauth flow so I had to switch to “general app.”

Thoughts? Thank you!

---

<div class="post-metadata">

**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [January 27, 2025, 3:38pm UTC](https://devforum.zoom.us/t/beginner-q-publish-an-internal-app-for-make-com/125286/2 "2025-01-27T15:38:36Z")

</div>

It’s fine to leave the application in local test indefinitely. The terminology and intended workflow is meant for publication to a general audience, but since you’re not going to publish, you can stay in local test so long as it’s okay that any Zoom API calls are carried out against your account’s users only. Here’s an overview of the relevant different options:

- “Development” and “Production” are separate applications; “Development” can only be used for local test (users in your account).
- “Local test” is for users internal to your account (no Marketplace approval needed). “Beta test” expands that to a limited number of external users and can be added by users for a limited time period (requires Marketplace approval).
