How to sell Zapier templates and keep 85%

If you design Zaps that solve a repeatable problem, you can package them with a guide and sell them here. You keep 85% of each sale, with no monthly fees and no listing fees.

Zapier works differently from n8n and Make. A Zap is not normally handed over as a workflow file, so the way you deliver it, and how well you document it, matters more. This page covers both.

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 Zapier category. There are no listing fees.

Step 3: Wait for the review. New listings are reviewed before they go live, so check that your Zapier 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 Zapier template 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.

How a Zap is shared

Zapier is a cloud service and a Zap lives in a Zapier account. Rather than exporting a file, Zaps are typically shared with a link that lets someone copy the Zap into their own account, where they connect their own app accounts. Zapier’s interface and sharing options change over time, so check Zapier’s current help pages for the exact steps before you write your guide.

A practical way to deliver one on this marketplace is to put the share link and your written guide in the files you upload. Test the link from a second account before you publish, and again after you change or turn off the original Zap.

What to document for a Zap

The trigger app and event, and every action step in order, with a screenshot of each step.

Every app account the buyer must connect, and what permissions each connection needs.

Filters, paths and formatter steps, with the conditions written out so buyers can adapt them.

Any code step: the language, what it does and which values it expects.

The fields a buyer has to map to their own data, such as a spreadsheet, a list or a channel.

Whether any app or feature involved may need a paid Zapier plan. Usage is counted in tasks, so say roughly how many a typical run uses.

Sample data that shows what a successful run looks like.

What a good Zapier listing contains

A plain description of the outcome: what happens in which app when the trigger fires.

A setup guide from copying the Zap to turning it on, including a test step.

The share link and a note on what to do if it stops working.

A list of known limits, such as polling delay on triggers or API limits of the connected apps.

Your own version number and the date you last tested the Zap.

Where your listing appears

Zapier listings go in the Zapier 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 Zap?

Create a free account, write the guide and set your price.