Introduction to Make apps

to read more about how works, refer to the get started https //help make com/get started section currently supports more than 3000 apps you can see all the apps on the app integrations https //www make com/en/integrations page types of apps 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 or by other users these apps go through the 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 '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 users can use standard apps paid plan apps all users on a paid plan (core, pro, teams, and enterprise) can use paid plan apps enterprise apps all 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 builder custom apps custom apps are developed by users 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 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 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 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 builder to use a community app in your , you must first install it in your 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 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 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 they bring utility and logic functions to your , such as aggregating or iterating data these apps process your data inside the 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 builder