How to get listed in integration marketplaces

Your SaaS connects to a tool your users already use, like Slack, Jira, HubSpot or Zapier, and you want to get listed in that tool's integration marketplace so its users can find you. Most of these marketplaces now ask for proof before they look at you: 10 active Slack workspaces, 3 active HubSpot installs, 3 people using your Zapier integration. Here is how to get those first installs yourself with personal messages, pass the review the first time, and count what the listing brings.

Do these three things

About 1 to 2 weeks to build the first version, then about 4 hours a day. Judge your messages after 2,800, and judge the listing 8 weeks after it goes live. Reviews take from 1 week (Zapier) to 10 weeks (Slack).

Show the three actions in fullHide the full list

1. 1Today: ask every user which tool they want your SaaS to send things to, and pick the one marketplace most of them already use (Zapier if no tool gets 3 votes). Write down its rules: how many installs it needs, which pages it checks, and how long its review takes.
2. 2Every day: send 100 personal messages with your install link to people who use that tool, and answer 20 questions in the places they ask for help. Keep going until you pass the install minimum, and right through the review.
3. 3Every Sunday: count installs, active users and signups from the integration, and submit your listing the week you pass the minimum.

Get help doing these

ChatGPT or Claude reads this guide and works through it with you.

Do this with ChatGPT(opens in a new tab)Do this with Claude(opens in a new tab)

1. Pick the one integration marketplace your users already work in

Pick one marketplace: the one for the tool most of your users already work in every day. Ask them, count the answers, and build for the winner only. A listing helps when the people browsing that marketplace are the people your SaaS is for.

Send one short question to every signup and customer today, by email or in the chat inside your product. Ask where they want your product to send things, not "would you like an integration", because almost everyone says yes to that. Their answers are also good feedback from your first users, so keep them in your sheet. Then open the integrations pages of 3 competitors from your competitor analysis and write down which tools they all connect to.

Subject: where should [product] send things?Hi [first name],Quick one. When [the thing your product makes, such as "a new bug report"] comes in, where do you want to see it? Slack, Jira, Trello, email, somewhere else?One word is plenty. I'm deciding what to build next.[Your name]

Then use this rule:

• If one tool gets 3 or more votes: pick its marketplace.
• If no tool gets 3 votes, or you have fewer than 10 users: start with Zapier. It needs the fewest users before you can submit, it replies within a week, and one integration lets people connect you to thousands of other apps.
• If your product works inside the browser, a Chrome extension is a fair second choice, and it can also work as a free tool that brings in leads. Do it after the first one, not at the same time.

Write the marketplace's rules into your sheet before you build anything. These were checked on 7 October 2026 in each marketplace's own developer docs:

Some numbers in older posts are wrong now. Slack lowered its minimum to 5 workspaces in August 2025, then went back to 10 in July 2026. Atlassian has accepted only Forge apps for new listings since 17 September 2025. Zapier's current docs ask for 3 users with a live Zap, not the "50 users" some blogs still quote. If your users run Shopify stores, Shopify's App Store is the obvious pick, but Shopify said in February 2026 that reviews are "longer than usual right now".

• Tool: email or your in-app chat, and a Google Sheet.
• Time: about 1 hour today. Most answers come back within 3 days.
• You will have: one marketplace, with its install minimum, the pages it checks and its review time written in your sheet.
• It worked if: at least 3 of your users already use that tool every day.
• Common mistake: building for the biggest marketplace instead of the one your users use, or for 5 at once. Each one has its own review, and with your hours split five ways you will not pass any of their minimums.

2. Read the listing rules, then build the smallest integration that does one job

Read the marketplace's guidelines page before you write a line of code, then build an integration that does one useful job inside that tool. Most rejections come from rules that were easy to read first.

One job means one thing your user gets in the tool without opening your product: "each new report shows up in a Slack channel", "a new signup becomes a HubSpot contact", "a Zap starts when a report comes in". Your customer interviews and the step 1 answers tell you which job matters most.

The rules that cause most rejections, from each marketplace's own docs:

• Slack: the app must do something inside Slack. Slack rejects apps that "do not add value to the experience of using Slack", apps that only use "Sign in with Slack", and apps that are "only an MCP server without meaningful in-Slack functionality". Ask only for the permissions (Slack calls them scopes) the one job needs. Slack data may not be used to train AI models.
• Atlassian (Jira, Confluence): build on Forge. Your app must not break or slow down Jira's own screens.
• Zapier: you must work for the company that owns the API, and your app must be "fully launched to the public", not invite-only. You give Zapier a test account for integration-testing@zapier.com.
• HubSpot and Webflow: people connect with OAuth, the standard "log in and allow" screen.

If you are a technical founder, let an AI coding assistant write the first version from the platform's own quickstart and the rules page, then test it yourself and with one of your beta users. The platform's developer tools are free to use: the Slack app dashboard, Zapier's Platform UI, Atlassian's Forge tools, HubSpot's developer account.

When it works, turn on the install link that each marketplace gives you before you are listed:

• Slack: in your app's settings, open "Manage Distribution" and click "Activate Public Distribution". Slack says no review is needed, and it works at once.

• Zapier: keep the integration private and invite users by email (up to 100) or by a sharing link.

• Atlassian: in the developer console, open "Distribution", click "Edit" and choose "Sharing". This works only before you submit the app for listing.

• HubSpot: an app made since 22 September 2025 can be installed in up to 25 accounts before it is listed.

• Chrome Web Store: publish as "Unlisted". Anyone with the link can install it, and it is not shown in the store.

• Tool: the platform's developer tools, its guidelines page, and an AI coding assistant.

• Time: about 1 to 2 weeks for a developer founder.

• You will have: a working integration that does one job, and an install link.

• It worked if: a user installs it from the link in a fresh workspace, and the job works in under 2 minutes without your help. That is good onboarding.

• Common mistake: building 10 features and asking for every permission "just in case". Slack asks you to justify every permission, and the Chrome Web Store reviews broad permissions more slowly. Ship the one job and let users ask for the second.

3. Get your first installs with an install link and 100 messages a day

Send 100 personal messages a day, each with your install link, to people who use that tool, until you pass the marketplace's minimum. Nobody will find your integration before it is listed, so the first installs come from you.

Message people in this order:

1. Your own users who named that tool in step 1. Send each one the link today, with a line about how they use your product.
2. Your other signups and trial users. An integration they can use in a tool they already open is a good reason to come back, and it can move a trial to paid.
3. People who fit your buyer and use that tool. Build a free lead list of about 3,000 a month: 100 a day needs that many. Look for people who show the tool in public, such as a team page, a job post or a help article that names it.

Let AI draft each message from your list and the template below. You add one true line about the person, and you check every line before it goes out. That takes about 1 to 2 minutes a message. Follow up up to 3 times with anyone who does not answer. If fewer than 3 in 100 reply, fix the first line before you send more.

Spread the volume over channels instead of cutting it. Email from a warmed-up second domain, not your main one. LinkedIn messages, within LinkedIn's weekly limit on connection requests. Never send private messages to members of a Slack community or forum that does not allow them.

Track active installs, not clicks. Slack counts a workspace only if it was used in the last 28 days, and you must keep 10 or more for the whole review. HubSpot counts accounts with activity in the last 30 days that are not yours. Zapier needs 3 people with a Zap turned on. A friend who installs it and never uses it does not count, so ask people who have the problem. Every installer who uses it is also a step towards activation.

Subject: [the one job] in [tool]Hi [first name],[One true line about them, such as "Saw your studio launched the new site for [client] last week."]I built [product], and we just made it [the one job, such as "post each new bug report into a Slack channel, with the screenshot"]. If your team lives in [tool], it saves [the step it removes].Here is the install link: [install link]It takes about 2 minutes. If anything is missing for your team, tell me and I'll fix it this week.[Your name]

• Tool: email, LinkedIn, your list and your sheet.
• Time: about 3 hours a day, every day.
• You will have: 100 messages a day logged, each install written down with where it came from.
• It worked if: you pass the minimum, such as 10 active Slack workspaces, within 2,800 messages (4 weeks at 100 a day). If you do not, change the message or the list first. If people install it and stop using it, change the one job.
• Common mistake: stopping the messages on the day you submit. Slack checks the 10 workspaces during the whole review, and a review can take 10 weeks.

4. Write your marketplace listing and the pages the review checks, then submit

Write the pages the review checks and the listing itself, and submit the same week you pass the minimum. A reviewer clicks every link, so each page must be real, public and about this integration.

Put these on your own site. AI can draft each one from your product and the rules page; you check every line is true.

• An integration page. Slack asks for "an actual web page created specifically for your Slack app": what it does in the tool, how to install it, what happens after, and a link to your privacy policy. Do not send reviewers to your homepage. Write it like a short landing page with one button: install.
• Setup steps. HubSpot also checks that the price in your listing matches your pricing page, and it asks for "publicly available setup documentation specific to your HubSpot integration". Atlassian asks for documentation "that describes how to set up and use your app".
• A privacy policy. Slack lists what it must say: what data you collect, how you use it, how long you keep it, how a person can see, move or delete their data, and an email or form to contact you.
• A support page. Slack wants a public page, with no account needed, and answers "within 2 business days". Use a plain email address if you have nothing else.
• Images and video. Use real screenshots of the job working, and a short screen recording that works like a product demo. Webflow asks for a 2 to 5 minute demo video. You can reuse clips from your short videos.

Write the listing text the way you wrote your value proposition: the result for the user, in their words. Name it "[your product] for [tool]". Slack's own example is "Task notifications for Slack", not "Slack task notifications", because you may not use their name first. Add UTM parameters to any link back to your site, so you can see visits from the listing.

Then submit:

• Zapier: in the Platform UI, open your integration, go to Integration Home, click "Publish", fill in the form, and click "Submit for Review".
• Slack: on your app's configuration page, use the "Submit to the Slack Marketplace" section.
• HubSpot: go to Development, then App Listings, then "Create listing". Fill in each section and click "Submit for review", then "Agree & submit". You need Super admin access.
• Atlassian: create the listing from your Marketplace partner account and submit it. Approval takes 10 to 15 business days.
• Chrome Web Store: in the Distribution tab, change the visibility from "Unlisted" to "Public".

While you wait, keep your 100 messages a day going, and answer every reviewer email the same day. Do not cancel and resubmit to "move it along": on Shopify, that sends you to the back of the queue.

Headline: [the one job, as a result], right inside [tool]
Line 2: For [who it is for]. Free with any [product] plan. [Or: the price.]
Button: Install in [tool]How it works
Click Install and allow access. ([what you ask for, in plain words])
[The first thing they set up, such as "pick a channel"].
[What happens next, such as "each new report appears there with the screenshot"].
What we can see, and what we keep: [2 lines], and a link to the privacy policy.
Help: [support email]. We answer within 2 business days.

• Tool: your website, ChatGPT or Claude for first drafts, and a screen recorder.
• Time: about 1 day.
• You will have: every page live, the listing written, and the app in the review queue.
• It worked if: the first review comes back with no note about a missing or private page.
• Common mistake: a support link that needs a login, or a privacy policy that does not say how long you keep data. Both are on the reviewer's list.

5. Answer 20 questions a day where people who use the tool ask for help

Every day, answer 20 questions from people who use that tool, in at least 5 places where they ask for help. Some of them have the problem your integration solves, and an answer that helps is how they hear of you.

Look in the tool's own community (most big tools run one), the subreddits for the tool and for your buyers' job, and the communities where your buyers talk. Search each one for the problem your integration solves, in your users' words. AI can find and sort new questions and draft a first answer; you rewrite it with what you know and post it yourself. About 3 minutes an answer.

Answer the question in full first. If your product really fits, say so in one line and say that you made it. Follow each place's rules on links. The Zapier Community, for example, says "self-promotional links … is not allowed", and Reddit has its own rules on self-promotion. Someone who wants your product will search for it.

Every person who installs and uses the integration should also hear from you. Ask what is missing, and once the listing is live, if your marketplace shows reviews, ask them for one, the same way you would ask for a G2 review. A user who says something kind has given you a testimonial; ask if you can quote it on your integration page. A user with a clear before and after is your first case study. Mention the integration in your onboarding emails so new signups find it. On Zapier, make Zap templates during the beta, as Zapier's docs suggest.

• Tool: the communities, your sheet, and ChatGPT or Claude for first drafts.
• Time: about 1 hour a day.
• You will have: 20 answers a day across at least 5 places, logged in your sheet.
• It worked if: after 2 weeks (280 answers), people reply to your answers or ask how you did it. If nobody does, you are answering in the wrong places or the wrong questions.
• Common mistake: dropping your link into every answer. Moderators remove it, and people learn to skip your name.

6. Count installs and signups from your listing every Sunday

Every Sunday, write down the installs, active users and signups from each source: your messages, your answers and the listing. Eight weeks after the listing goes live, decide whether to keep it, fix it, or put the hours back into messages.

Get the numbers from three places:

• The marketplace's developer dashboard: installs, and active installs where it shows them.
• Your analytics: visits from the listing's tracked link, and signups as a conversion.
• Your signup form: add the marketplace as an answer to "Where did you hear about us?". That is self-reported attribution, and it catches people your analytics miss.

Eight weeks after the listing goes live, decide:

• The listing brought signups: keep it. Update the screenshots and text once a month, and ask active users for reviews where the marketplace shows them.
• Installs but no signups: fix the first line of the listing and the integration page, so they say what your product does beyond the one job. Check the integration page links to a free trial or a way to try it.
• Nothing: leave the listing up and spend no more hours on it. Put them back into your 100 messages a day.

Compare honestly. Divide the signups from each source by the hours you spent on it, and give next month's hours to whatever brought more per hour. That is how you choose your channels. Only start the second marketplace once the first one is live and counted. When users of the tool are signing up, the next step is a co-marketing campaign with that tool's team, or referral partnerships with other apps in the same marketplace. Look at all of it together in your monthly marketing review.

• Tool: the marketplace's developer dashboard, your analytics, your signup form and your sheet.
• Time: about 20 minutes each Sunday.
• You will have: one row per source each week, and after 8 weeks live a keep, fix or leave decision.
• It worked if: you can say how many signups the listing brought, and how many your messages brought, for the same hours.
• Common mistake: counting installs as the result. An install that is not used is not a user, and on Slack it does not even count towards the minimum.

Your integration marketplace checklist for the next 8 weeks

0 of 12 done

Work through this list with an AI assistant

It drafts the work and keeps track of what is done.

Do this with ChatGPT(opens in a new tab)Do this with Claude(opens in a new tab)

Step 1 · Pick one marketplace

• Ask every user where they want your product to send things, and count the answers.
• Pick one marketplace and write down its rules.

Step 2 · Build one job

• Read the marketplace's guidelines and build the smallest integration that does one job.
• Turn on the install link and test it with one user.

Step 3 · Get the first installs

• Every daySend 100 personal messages with your install link to people who use the tool.
• Every dayFollow up with everyone who has not answered, up to 3 times.

Step 4 · Write the listing and submit

• Put the pages the review checks on your site.
• Write the listing and submit it the week you pass the install minimum.

Step 5 · Answer 20 questions a day

• Every dayAnswer 20 questions where people who use the tool ask for help.
• Every dayAsk each new active user what is missing, and for a review once you are listed.

Step 6 · Count every Sunday

• Every SundayWrite down installs, active users and signups from messages, answers and the listing.
• After 8 weeks liveDecide to keep, fix or leave the listing, and move your hours to what brought more signups.

Copy listDownloadReset