How to sell Make.com scenarios and keep 85%

A Make scenario that saves you hours can save someone else hours too. Export it as a blueprint, list it here and keep 85% of each sale. There are no monthly fees and no listing fees.

Make is a cloud service, so buyers do not have a hosting decision to make. What they do need is a clear list of the apps, connections and plan limits your scenario relies on. This page covers how to export a blueprint and how to describe it.

How selling works, step by step

Step 1: Create a free account and set up your seller profile. Sign up for a free account and open the seller area in your dashboard. Before your first listing is submitted you confirm your email with a short code. New listings are reviewed before they go live.

Step 2: Create your listing. Describe what you built, set a price, upload the files and choose the Make.com category. There are no listing fees.

Step 3: Wait for the review. New listings are reviewed before they go live, so check that your blueprint files are complete and that the description is complete.

Step 4: Buyers pay and download. Buyers pay by card through Stripe Checkout, then download your files and read your setup instructions straight away.

Step 5: Request your payout. Once your balance reaches $10 you can request a payout from your dashboard. Requests are reviewed and paid by PayPal or bank transfer.

What a sale looks like

Sellers keep 85% of every sale and there are no monthly or listing fees. For a Make scenario priced at $50, the platform fee is $7.50 and you receive $42.50.

Workflow price $50.00. Platform fee (15%) −$7.50. You receive $42.50. The 15% platform fee covers payment processing, hosting and support. This is the same example as on the pricing page.

Exporting a Make blueprint

A Make scenario can be exported as a blueprint, which is a JSON file describing the modules, their settings and how they connect. In the scenario editor, open the more-options menu and choose the export blueprint option. To use one, a buyer creates a new scenario and imports the blueprint file from the same menu.

Check the blueprint before you list it:

Connections are tied to your own accounts. Buyers create their own connections after importing, so list every app that needs one.

Values picked from dropdowns, such as a spreadsheet, base, channel or folder, refer to things in your account. Buyers will need to select their own, so say which fields to re-map.

If the scenario starts with a webhook, buyers get a new webhook address when they import it. Explain where to paste it and how to send a test request.

If it uses a data store or a custom data structure, describe what it contains so buyers can recreate it.

Remove hard-coded keys or personal data typed into module fields, and use test data that contains no real customer information in your screenshots.

What a good Make listing contains

A setup guide that goes from import to first successful run, including the order in which to connect apps.

A screenshot of the whole scenario and a short description of each route, router and filter.

The list of apps and modules used, and which connection each one needs.

How the scenario starts: a schedule, an instant trigger or a webhook, and how often it is meant to run.

A note on operations. Make counts each module run as an operation, so say roughly how many a typical run uses, and explain that allowances and scheduling intervals depend on the buyer’s Make plan.

How errors are handled: which routes have error handlers and what happens to a failed bundle.

The date or version of the Make interface and modules you tested with, plus your own version number for the blueprint.

Where your listing appears

Make scenarios go in the Make.com category. These are the current live listing counts.

Refunds

Buyers can ask for a refund. Requests are reviewed case by case, and for standard products they must be made within 14 days of purchase. A clear setup guide and an honest list of requirements are the best way to avoid disputes.

Ready to list your first Make scenario?

Upload your blueprint, write the setup guide and set your price.