How does it work
Note all the answers below reflect Make’s thinking as of July 2023. Based on feedback from both partners and customers, as well as business results, we reserve the right to make changes to the program
Last updated
Note all the answers below reflect Make’s thinking as of July 2023. Based on feedback from both partners and customers, as well as business results, we reserve the right to make changes to the program
Last updated
© 2025 make.com
Yes. Here is documentation. The apps accepted to the Apps Marketplace for Partners need to be public but not approved. Apps that are listed on the Apps Marketplace for Partners are referred to as community apps.
As of now it is not possible to develop templates for community apps (more precisely, you can creare a template but it’s not possible to publish it). As a workaround, you could create a scenario and export its blueprint and share that with your customers which would then import it provided that they first install your app.
Submit the app by filling out the submission form: https://f.make.com/submit-your-app. This form is meant for apps that are completely ready to be listed on the Apps Marketplace.
Yes. Want to check if the app you're planning to launch is already on our roadmap? Contact your Partner Manager.
Contact your Partner Manager. We will try to keep a consolidated list of all apps we know of that are currently in development. However, we don’t expect this list can ever be 100% exhaustive.
No, there’s no need to submit the source code. You’ll see everything you need to submit on the submission form, including:
Your app invite link, so Make can see and test your app.
The landing page where customers can obtain your app.
Because we only do a business review of each app, and not a technical or security review, we will generally only take 2-3 business days to accept or reject your app. Please be patient with us as we launch this initiative. Some reviews may take slightly longer than this to process.
Make will display all community apps among all other publicly available apps on the https://www.make.com/en/integrations page.
Each service integrated with Make via community app will have its landing page on Make website which is going to feature community apps from all partners who decided to develop and publish an app for that service on the Marketplace. Each app will have a link to the partner’s site.
As a partner, you should present the app’s features and benefits, as well as pricing information and terms and conditions associated with its use. This information and any screenshots, videos, or even customer testimonials may be crucial in helping customers decide to use this app.
Yes. If there is a request for such app on Make Idea Exchange, we will announce that app is now "Available as a community app", link to the landing page on the Make website and promote the partner’s website as the author of the app.
As the Marketplace grows, and therefore increases in potential value to existing Make users, we will undertake further marketing activities to promote it.
The partner organization creates and hosts its own landing page for the app that includes a method for providing the app to customers. The method through which the partner chooses to share the app does not matter to Make.
You are free to provide a direct install link on your landing page (for free/open source apps), ask your customers to request the app via email or ask them to fill out a form or go through a registration and checkout process. But, regardless of the delivery method you choose, the app will be installed in the customer’s Make organization.
All apps submitted to the Apps Marketplace need to be invite-only apps. Once the customer clicks on the app invite link, they’ll need to install it into their Make organization, unless you install the app to the customer’s organization via API. Navigate here for more information on securing access to your app.
The app is hosted by Make, in your organization as a published app with a generated invite link. However, you need to host your own landing pages for the app.
No. However, partners are free to monetize their apps independently by selling to Make customers directly.
No. We may explore ways to introduce this in the future. Currently, it is the partner’s responsibility to bill their customers for the app usage if they wish to monetize their app.
Currently, you need to create your own monetization system. Here are some methods you could explore:
Have customers write you an email, send them an invoice, and then share the access with them.
Have customers fill out a form on your website, and automatically send them an invoice. Upon accepting and recognizing the payment, you can send them access.
Have customers subscribe to your service with a full checkout process and billing system. After checkout, share access with them.
The easiest way to do this is to simply share an invite link to the app. If you simply share an invite link and have no further protection in place, you risk the invite link being shared beyond paying customers.
One way to ensure security is to ask customers for an access token as a requirement for connecting to your app. You would need to generate a unique token for each customer that pays for your app, making sharing impossible.
The most effective and secure way is to ask customers to generate an API key on Make’s side with the appropriate scope and use this access to install the app directly into their organization. We’ve got an example of how this can be done here.
We recommend that you choose a flat, monthly fee with a price between $1 and $10 for SMB apps and between $50 and $500 for enterprise apps. However, you’re free to charge a one-off fee, recurring charges, or structure pricing as you wish.
Assess the main customers your app is integrating with. For example, SAP S/4 HANA is primarily focused on enterprise customers, while Pipedrive is an SMB-focused CRM.
Not at this time, partners are keeping 100 % of their app-related revenues. However, this may change in the future.
You, as a partner, are responsible for supporting any app(s) you submit to the Apps Marketplace.
We will make it clear that you, as the app developer, are responsible for providing support in the Apps Marketplace.
We expect you to inform your customers of this on your landing pages and terms and conditions.
You can also add an info box to your app containing information about where to ask for support, so it’s visible any time a user opens any module.
Below is a code example you can use in the mappable parameters section of your app components. Please, change the colors to match your app’s theme color and supply real names and links to your resources when using this example.
Should a customer reach out to Make for support with your app, we will redirect the request to you.
We do not require any specific level of customer support at the moment. You should create terms and conditions for the use of your app, and we assume you are committed to keeping your customers satisfied.
That said, we expect that you will handle customer requests in a reasonable time, especially if you receive a request for support that we’ve redirected to you. Please act promptly if there is a need to escalate an issue.
Failure to address customer issues promptly may result in your app being removed from the Marketplace.
We want to make sure that our platform enables customers to continuously run their businesses, and, as part of our ecosystem, we expect your cooperation.
Permitted community apps are such that:
Are submitted by a signed Make partner.
Are connecting to a real 3rd party service (they are not just tools leveraging custom IML functions but they actually connect Make with a 3rd party service).
Are not yet default part of Make offering (more community apps connecting to the same service are allowed).
Are not planned to be developed by Make.
These are the only conditions we check when approving the app for the Apps Marketplace.
Our goal is to offer a wider variety of integrations to Make users. Second, some 3rd party apps can greatly reduce the number of operations consumed compared to our apps (e.g., Google Sheets), which ultimately impacts our business. Third, we don’t currently have a mechanism to clearly differentiate existing and community apps, if both exist for the same app
Apps should only provide the functionality of the API. Please make sure your app does not artificially reduce the number of operations being consumed (e.g., by leveraging IML functions to combine multiple bundles into one bundle).
We are trying to avoid this situation. Therefore, we will only accept an app into the Apps Marketplace if we are not actively developing it. If we accept an app into the Apps Marketplace that matches something already on our roadmap, we will usually remove it from our own roadmap unless there’s a reason for us to not do so.
Different partners may choose to pursue different monetization models or offer different features. Offering customers choices will allow them to select the best fit for their use cases.
Description of the app on your website including modules covered
Monetization model and price
Your location and localization
Later we might add this information to the marketplace:
Number of customers using the app
Ratings and reviews
While the Apps Marketplace is a test program, we hope to expand it in the future. Nonetheless, we reserve the right to close the program. In the unlikely event that we choose to do this, we will provide timely updates to you, and work with you to inform your customers. There shall not be any effect on existing users of your apps.
Your partner manager is your main point of contact.
