--- title: Introduction to Make apps slug: apps.make.com docTags: createdAt: 2025-02-03T13:29:01.216Z --- :::hint{type="info"} To read more about how Make works, refer to the [Get started](https://help.make.com/get-started) section. ::: Make currently supports more than 3000 apps. You can see all the Make apps on the [App Integrations](https://www.make.com/en/integrations) page. ## Types of Make apps Make groups apps into different types. App types indicate who built the app, the level of support to expect, and who can use it: - Verified apps - Custom apps - Community apps - Built-in apps ### Verified apps Verified apps are developed by Make or by other Make users. These apps go through the Make [app review process](https://developers.make.com/custom-apps-documentation/app-review) and must be actively maintained. This ensures that the app’s modules work reliably and follow Make's quality standards. Verified apps are grouped by availability based on Make [pricing plans](https://www.make.com/en/pricing): | **Verified app type** | **Availability** | | --------------------- | ---------------------------------------------------------------------------------------- | | Standard apps | All Make users can use standard apps. | | Paid plan apps | All Make users on a paid plan (Core, Pro, Teams, and Enterprise) can use paid plan apps. | | Enterprise apps | All Make users in organizations with the Enterprise plan can use enterprise apps. | Paid plan and Enterprise apps have specific **Paid plan** and **Enterprise** tags in the Scenario Builder. ::::VerticalSplit{layout="middle"} :::VerticalSplitItem ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/WHe1lJTOuKaHTABWXzuPx_image.png) ::: :::VerticalSplitItem ![](https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/B0XQjOvJWoFJJIciOopRu_image.png) ::: :::: ### Custom apps Custom apps are developed by Make users. Make provides a [web interface](https://developers.make.com/custom-apps-documentation/get-started/make-apps-editor/web-editor-features) where users can create and manage your custom app configurations. Custom apps are available to Make users based on their [visibility](https://developers.make.com/custom-apps-documentation/app-visibility): | **Custom app type** | **Availability** | | ------------------- | ------------------------------------------------------------------------------------------------------- | | Public app | The custom app developer and users in all organizations they belong to can use the app. | | Private app | Access to the app is on an invite-only basis. The app developer has to share an invite link with users. | :::hint{type="info"} To learn more about creating custom apps, check the [Custom Apps](https://developers.make.com/custom-apps-documentation) documentation. ::: ### Community apps Community apps are developed by Make partners and power users who have taken dedicated training. Unlike verified apps, community apps don’t go through Make’s [app review process](https://developers.make.com/custom-apps-documentation/app-review/overview). Support, maintenance, and monetization of a community app are the responsibility of the app developer. Community apps have a specific **Community** tag in the Scenario Builder. ::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/HWxzUOnu9-zSJyV2RhkIt_image.png" size="36" width="268" height="57" darkWidth="268" darkHeight="57" position="center" showCaption="false"} To use a community app in your scenarios, you must first install it in your Make organization. Only the users with the **Admin**, **Owner**, or **App Developer** role can install community apps. **Community app pricing** Community app pricing depends on the app developer. Some community apps are free to use. Others require a one-time payment or a recurring subscription paid directly to the app developer. :::hint{type="info"} Make doesn’t process these payments and doesn’t take a commission from them. ::: Community app pricing is separate from the pricing of the service the app connects to. You may need to pay for access to the connected service, its API, or specific API usage, even when the community app itself is free. A free community app can still require a paid API plan from the connected service. A paid community app can also connect to a service that offers free API access. | **What you pay for** | **Who charges you** | **Example** | | ------------------------------------------ | ------------------------------ | --------------------------------------------------------------------------------------------------------- | | Access to the community app | The app developer | You pay the developer to use their app in Make. | | Access to the connected service or its API | The connected service provider | You pay the service provider (e.g., a CRM or ERP) for an account, subscription, API access, or API usage. | Before you install a community app, check the app developer’s pricing and support terms. Review the connected service’s pricing to understand the full cost of using the app in your scenario. :::hint{type="info"} To learn more about community apps, refer to the [Community Apps](https://developers.make.com/custom-apps-documentation/community-apps/about) documentation. ::: ### Built-in apps Built-in apps are native tools built and maintained by Make. They bring utility and logic functions to your scenarios, such as aggregating or iterating data. These apps process your data inside the Make platform, so you don’t need to create a third-party connection. Most built-in apps are available to all users. Common examples include: - **Flow Control** - **HTTP** - **JSON** - **Markdown** - **Webhooks** - **XML** - **Encryptor** - **Email** - **CSV** Built-in apps have a specific **Built-in** tag in the Scenario Builder. ::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/oiZ3C4SmX-leAMcyd8OeS_image.png" size="48" width="392" height="59" position="center" darkWidth="392" darkHeight="59" showCaption="false"}