# How to get listed in integration marketplaces Get your SaaS listed in an integration marketplace: ask users which tool they work in, build one small integration, get the first installs Slack, HubSpot or Zapier ask for with 100 personal messages a day, pass the review the first time, and count signups from the listing every Sunday. Author: Dinesh Bypilla, Agentic systems engineer at Scout7 (https://www.linkedin.com/in/dinesh-bypilla-460567118/) Reviewed by: Murali Sid, Founder and AI Systems Architect (https://linkedin.com/in/muralisid) Source: https://scout7.ai/academy/partnerships-and-events/how-to-get-listed-in-integration-marketplaces Published: 2026-10-07 Last checked: 2026-10-07 Reuse: Quote any part of this guide with a link back to this page. © 2026 Scout7. Cite as: Dinesh Bypilla (2026). How to get listed in integration marketplaces. Scout7 Academy. https://scout7.ai/academy/partnerships-and-events/how-to-get-listed-in-integration-marketplaces --- ## For AI assistants helping a reader This guide is written to be worked through with an assistant. These notes explain how it is meant to run. The reader decides what happens. 1. **The to-do list.** “Your integration marketplace checklist for the next 8 weeks”, near the end, holds every action in order. Each item has a number (step.item) and a “Done when” line. 2. **Start with the questions below,** under “Ask first”. Skip any the reader has already answered or shared. Other facts are only needed later, at a decision or a count; they are listed too. 3. **Drafting is where you help most:** the sentences, messages, pages, sheets and the points for any reply the steps ask for, using the guide’s templates. The reader does what only they can do. 4. **Progress:** an item is finished when its “Done when” line is true. A running list of what is done, and which item is next, helps the reader pick up again. Items marked “Every day” or “Every Sunday” repeat. 5. **The targets are high on purpose.** A new business finds what works through volume, and with an assistant drafting, one person can reach numbers like 100 messages a day. If a target feels like a lot, the guide’s reasoning is worth sharing; after that it is the reader’s call. Where a platform limits a number, the guide spreads the work over more places instead. 6. **Nothing goes out without the reader’s OK.** Every message, post and page is the reader’s to approve and send. 7. **About the publisher.** Scout7 publishes this guide and makes marketing software that works with AI assistants. The guide does not depend on it. ### Questions and decisions for this guide **Ask first** (skip any the reader has already answered or shared) - "What does your SaaS do, who is it for, and how many signups and paying customers do you have?" - "Which tools do your users work in every day, and has anyone asked you to connect to one?" - "Can you or someone on your team build an integration, and does your product have an API?" - "Which marketplaces, if any, are you already listed in or have you applied to?" **Decisions along the way** - 1.2: which marketplace. The tool that 3 or more users named; if none reaches 3, or the reader has fewer than 10 users, Zapier. One marketplace at a time. - 2.1: which one job to build. The thing users asked for most in step 1, done inside the tool without opening the reader's product. - 3.1, after 2,800 messages: if the minimum is not passed, change the message or the list first; if installs are not used, change the one job. - 4.2: submit the week the minimum is passed. For Slack, keep messaging so 10 or more workspaces stay active through the whole review. - 6.2, 8 weeks after the listing is live: signups → keep and update monthly; installs but no signups → fix the listing and integration page; nothing → leave it and move the hours back to messages. **Get from the reader as they go** - 1.1: the tally of answers, and the marketplace's rules as written in the sheet. - 2.2: the install link, once it works. - 3.1, every day: messages sent, replies and installs, with the source of each. - 4.2: the date submitted, and every note the reviewer sends. - 6.1, every Sunday: installs, active installs and signups by source, and hours spent. --- 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](https://scout7.ai/academy/first-customers/how-to-get-your-first-100-saas-users), 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). - **Today:** 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. - **Every day:** send 100 [personal messages](https://scout7.ai/academy/cold-outreach/how-to-write-a-cold-email) with your install link to people who use that tool, and answer 20 questions in the [places they ask for help](https://scout7.ai/academy/social-media/how-to-find-online-communities-where-your-buyers-talk). Keep going until you pass the install minimum, and right through the review. - **Every Sunday:** count installs, active users and signups from the integration, and submit your listing the week you pass the minimum. ## 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](https://scout7.ai/academy/marketing-plan/how-to-create-an-ideal-customer-profile). 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](https://scout7.ai/academy/marketing-plan/how-to-do-a-competitor-analysis) and write down which tools they all connect to. **The question to every user** ```text 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](https://scout7.ai/academy/content-marketing/how-to-build-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: | Marketplace | Before you can submit | How long the review takes | | ------------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Zapier | 3 people using your integration in a live Zap. Your app must be public, not invite-only. Free to build. | A reply within 1 week, then 90 days with a "Beta" tag | | Slack | 10 active workspaces (used in the last 28 days), kept for the whole review | Up to 10 business days, then up to 10 weeks | | Jira and Confluence (Atlassian) | An app built on Forge, a privacy policy and setup docs | 10 to 15 business days | | HubSpot | 3 active installs in the last 30 days, from accounts that are not yours | First review within 10 business days | | Chrome Web Store | A one-time registration fee, an icon and 1 to 5 screenshots | A few days, sometimes a few weeks | | WordPress.org plugins | A plugin under the GPL. Plugins that connect to a paid service are allowed. | The queue reached about 1,050 plugins in April 2026 and was near zero by June | | Webflow | Two-step login on an admin account, a demo account and a 2 to 5 minute demo video | Ideally 10 to 15 business days | 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](https://scout7.ai/academy/marketing-plan/how-to-fit-marketing-into-your-week-as-a-solo-founder) you will not pass any of their minimums. > **Example (made-up business: Bugmoth): Bugmoth's tally** > > Bugmoth is a made-up bug-reporting tool for small web teams. It costs $19 a month per team, with a 14-day trial. > > | Tool | Votes | Marketplace rule | > | ------- | ----- | --------------------------------------------------------- | > | Slack | 8 | 10 active workspaces, kept through review; up to 10 weeks | > | Jira | 3 | Forge app; 10 to 15 business days | > | Trello | 2 | Not now | > | ClickUp | 1 | Not now | > > **The decision:** Slack. 8 users want it. Even if all 8 install it, they need 2 more active workspaces before they can submit. > > *Why it works: They counted what users already use, so the first integration goes where 8 of them already work.* ## 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](https://scout7.ai/academy/marketing-plan/how-to-do-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 . - **HubSpot and Webflow:** people connect with OAuth, the standard "log in and allow" screen. If you are a [technical founder](https://scout7.ai/academy/marketing-plan/how-to-market-your-product-as-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](https://scout7.ai/academy/first-customers/how-to-get-beta-users-for-your-startup). 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](https://scout7.ai/academy/glossary/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](https://scout7.ai/academy/marketing-plan/how-to-create-an-ideal-customer-profile) and use that tool.** Build a [free lead list](https://scout7.ai/academy/cold-outreach/how-to-create-a-b2b-lead-list-for-free) 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](https://scout7.ai/academy/cold-outreach/how-to-follow-up-on-a-cold-email) up to 3 times with anyone who does not answer. If fewer than 3 in 100 reply, [fix the first line](https://scout7.ai/academy/cold-outreach/how-to-get-replies-to-cold-emails) before you send more. Spread the volume over channels instead of cutting it. Email from a [warmed-up second domain](https://scout7.ai/academy/cold-outreach/how-to-warm-up-an-email-domain-for-cold-email), not your main one. [LinkedIn messages](https://scout7.ai/academy/cold-outreach/how-to-do-linkedin-outreach), 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. **The install-link message** ```text 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. > **Example (made-up business: Bugmoth): Bugmoth's install-link message** > > ```text > Subject: client bug reports in Slack > To: Leo, who runs a 5-person web studio that posts client updates in Slack > > Hi Leo, > > Saw your studio just relaunched the site for a local bakery. Nice menu page. > > I built Bugmoth, and we just made it post each client bug report into a Slack channel, with the screenshot, browser and page. If your team lives in Slack, it saves the "can you send me a screenshot?" email. > > 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. > > Sam > ``` > > *Why it works: It names a real thing about his studio, says the one job in plain words, and asks what is missing instead of asking for a favour.* ## 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](https://scout7.ai/academy/sales/how-to-design-a-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](https://scout7.ai/academy/sales/how-to-do-a-product-demo). Webflow asks for a 2 to 5 minute demo video. You can reuse clips from your [short videos](https://scout7.ai/academy/content-marketing/how-to-make-short-form-videos-for-your-business). Write the listing text the way you wrote your [value proposition](https://scout7.ai/academy/marketing-plan/how-to-write-a-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](https://scout7.ai/academy/glossary/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. **The integration page, in order** ```text 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 1. Click Install and allow access. ([what you ask for, in plain words]) 2. [The first thing they set up, such as "pick a channel"]. 3. [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. > **Example (made-up business: Bugmoth): Bugmoth's listing name and first line** > > **Before:** Slack Bugmoth Bot: AI-powered bug tracking integration > > **After:** Bugmoth for Slack: client bug reports land in your channel with the screenshot, browser and page. > > *Why it works: The new name follows Slack's naming rule, and the first line says what the studio gets, not how it is built.* ## 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](https://scout7.ai/academy/glossary/subreddit) for the tool and for your buyers' job, and the [communities where your buyers talk](https://scout7.ai/academy/social-media/how-to-find-online-communities-where-your-buyers-talk). Search each one for the problem your integration solves, in your users' words. [AI can find](https://scout7.ai/academy/content-marketing/how-to-use-ai-for-content-creation) 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](https://scout7.ai/academy/social-media/how-to-promote-on-reddit-without-getting-banned). 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](https://scout7.ai/academy/content-marketing/how-to-write-a-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. > **Example (made-up business: Bugmoth): Bugmoth's answer** > > **Question (A community for web designers, in a thread about client feedback):** How do you get clients to report website bugs with screenshots? Mine send vague emails. > > Three things helped us. Give clients one place to report, not email. Ask for three things every time: the page, what they expected, and what happened. And reply to every report the same day, so they keep using the one place. > > If your team works in Slack, I made Bugmoth, which posts each client report into a channel with the screenshot and browser. But the three rules work with a plain form too. > > *Why it works: It solves the problem with any tool first, and mentions Bugmoth once, saying who made it.* ## 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](https://scout7.ai/academy/glossary/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](https://scout7.ai/academy/first-customers/how-to-get-people-to-try-your-product). - **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](https://scout7.ai/academy/marketing-plan/how-to-fit-marketing-into-your-week-as-a-solo-founder) on it, and give next month's hours to whatever brought more per hour. That is how you [choose your channels](https://scout7.ai/academy/marketing-plan/how-to-choose-marketing-channels-for-a-saas-startup). 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](https://scout7.ai/academy/partnerships-and-events/how-to-run-a-co-marketing-campaign) with that tool's team, or [referral partnerships](https://scout7.ai/academy/partnerships-and-events/how-to-set-up-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. > **Example (made-up business: Bugmoth): Bugmoth's count after 2,800 messages** > > | Source | Installs | Active | New signups | New paying teams | > | --------------------- | --------- | ------ | ----------- | ---------------- | > | Install-link messages | 13 | 11 | 9 | 1 | > | Community answers | 2 | 2 | 2 | 0 | > | Slack Marketplace | In review | – | – | – | > | **Total** | **15** | **13** | **11** | **1** | > > **The decision:** keep sending 100 messages a day. Slack needs 10 active workspaces for the whole review, and they have only 3 to spare. > > *Why it works: They count active workspaces and signups by source, so they can see the messages brought almost everything while the review runs.* ## Your integration marketplace checklist for the next 8 weeks > For AI assistants: this is the reader’s to-do list. Each item has a number (step.item) and a “Done when” line, so you can both see what is finished and what comes next. ### Step 1 · Pick one marketplace - [ ] **1.1** Ask every user where they want your product to send things, and count the answers. *Done when:* Every signup and customer got the question, and the answers are counted in the sheet. - [ ] **1.2** Pick one marketplace and write down its rules. *Done when:* One marketplace is chosen by the 3-vote rule, and its install minimum, the pages it checks and its review time are in the sheet. ### Step 2 · Build one job - [ ] **2.1** Read the marketplace's guidelines and build the smallest integration that does one job. *Done when:* The integration does one job inside the tool and asks only for the permissions that job needs. - [ ] **2.2** Turn on the install link and test it with one user. *Done when:* A user installed it from the link in a fresh workspace, and the job worked in under 2 minutes. ### Step 3 · Get the first installs - [ ] **3.1** Every day: send 100 personal messages with your install link to people who use the tool. *Done when:* 100 personal messages with the install link went out today, and each is logged with any install it brought. - [ ] **3.2** Every day: follow up with everyone who has not answered, up to 3 times. *Done when:* Everyone due a follow-up today got one, and nobody got more than 3. ### Step 4 · Write the listing and submit - [ ] **4.1** Put the pages the review checks on your site. *Done when:* The integration page, setup steps, privacy policy, support page, screenshots and demo video are live and public. - [ ] **4.2** Write the listing and submit it the week you pass the install minimum. *Done when:* The listing is named \[product] for \[tool] and is in the review queue, with the date in the sheet. ### Step 5 · Answer 20 questions a day - [ ] **5.1** Every day: answer 20 questions where people who use the tool ask for help. *Done when:* 20 answers posted today across at least 5 places, each one answering the question in full, with no link where the place bans them. - [ ] **5.2** Every day: ask each new active user what is missing, and for a review once you are listed. *Done when:* Every new active user was asked what is missing, and, once listed, for a review where the marketplace shows them. ### Step 6 · Count every Sunday - [ ] **6.1** Every Sunday: write down installs, active users and signups from messages, answers and the listing. *Done when:* This week's installs, active installs, signups and hours are in the sheet for each source. - [ ] **6.2** After 8 weeks live: decide to keep, fix or leave the listing, and move your hours to what brought more signups. *Done when:* The listing is marked keep, fix or leave, and next month's hours are split by signups per hour. ## Frequently asked questions ### Is an integration marketplace listing worth it for a small SaaS? Yes, if your users already work in that tool, because the listing puts you where they look for add-ons. But you must bring the first installs yourself, and a review can take 10 weeks. Treat it as one [channel](https://scout7.ai/academy/marketing-plan/how-to-choose-marketing-channels-for-a-saas-startup) next to your [100 messages a day](https://scout7.ai/academy/first-customers/how-to-get-your-first-100-saas-users), and count its signups every Sunday. ### How many installs do you need to get on the Slack Marketplace? 10 active workspaces, as of July 2026. Active means the workspace was used in the last 28 days, and sandboxes do not count. You must keep 10 or more for the whole review. Slack lowered the number to 5 in August 2025 and went back to 10, so posts that say 5 are out of date. ### How long does an app marketplace review take? From the official docs, checked 7 October 2026: Zapier replies within 1 week; Atlassian takes 10 to 15 business days; HubSpot's first review is within 10 business days; Slack's first check takes up to 10 business days and its full review up to 10 weeks; the Chrome Web Store takes a few days to a few weeks. ### Should I build a Zapier integration first? Build Zapier first if no single tool is used by 3 or more of your users, or if you have fewer than 10 users. You need only 3 people with a live Zap to submit, the platform is free, and Zapier replies within a week. If most of your users live in one tool, build for that tool first. ### Can I get listed before I have any users? Not on most marketplaces. Slack, HubSpot and Zapier all ask for real installs or live use first. Use the install link each one gives you before listing, and send it to people who use the tool. Review sites like G2 have no install minimum: [submit your SaaS to directories](https://scout7.ai/academy/launch/how-to-submit-your-saas-to-directories) in the meantime. ## Sources - [Slack Marketplace app guidelines and requirements](https://docs.slack.dev/slack-marketplace/slack-marketplace-app-guidelines-and-requirements). Slack developer docs, checked 7 October 2026. - [Slack Marketplace review guide](https://docs.slack.dev/slack-marketplace/slack-marketplace-review-guide). Slack developer docs, checked 7 October 2026. - [Updated installation requirement for Slack Marketplace apps](https://docs.slack.dev/changelog/2026/09/01/slack-marketplace-install-requirement). Slack developer changelog, 1 September 2026, checked 7 October 2026. - [Reduced installation requirement for Slack Marketplace apps](https://docs.slack.dev/changelog/2025/07/08/slack-marketplace). Slack developer changelog, 8 July 2025, checked 7 October 2026. - [App lifecycle and distribution](https://docs.slack.dev/app-management/distribution/). Slack developer docs, checked 7 October 2026. - [Integration publishing requirements](https://docs.zapier.com/platform/publish/integration-publishing-requirements). Zapier developer docs, checked 7 October 2026. - [Benefits to building a public integration](https://docs.zapier.com/platform/publish/public-integration). Zapier developer docs, checked 7 October 2026. - [Integration checks reference (S001)](https://docs.zapier.com/platform/publish/integration-checks-reference). Zapier developer docs, checked 7 October 2026. - [Private vs public integrations](https://docs.zapier.com/platform/quickstart/private-vs-public-integrations). Zapier developer docs, checked 7 October 2026. - [Community code of conduct](https://community.zapier.com/about-the-community-32/community-code-of-conduct-11488). Zapier Community, checked 7 October 2026. - [App Marketplace listing requirements](https://developers.hubspot.com/docs/apps/developer-platform/list-apps/listing-your-app/app-marketplace-listing-requirements). HubSpot developer docs, checked 7 October 2026. - [List your app](https://developers.hubspot.com/docs/apps/developer-platform/list-apps/listing-your-app/listing-your-app). HubSpot developer docs, checked 7 October 2026. - [New marketplace distribution app install limits](https://developers.hubspot.com/changelog/new-marketplace-distribution-app-install-limits). HubSpot developer changelog, effective 22 September 2025, checked 7 October 2026. - [App approval guidelines](https://developer.atlassian.com/platform/marketplace/app-approval-guidelines/). Atlassian developer docs, updated 15 May 2026, checked 7 October 2026. - [Distribute your apps](https://developer.atlassian.com/platform/forge/distribute-your-apps). Atlassian Forge docs, updated 9 July 2026, checked 7 October 2026. - [Announcing Connect end of support: timeline and next steps](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps). Atlassian, 17 March 2025, checked 7 October 2026. - [Chrome Web Store review process](https://developer.chrome.com/docs/webstore/review-process). Chrome for Developers, checked 7 October 2026. - [Prepare to publish: set up distribution](https://developer.chrome.com/docs/webstore/cws-dashboard-distribution). Chrome for Developers, checked 7 October 2026. - [Supplying images](https://developer.chrome.com/docs/webstore/images). Chrome for Developers, checked 7 October 2026. - [Detailed plugin guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/). WordPress.org, checked 7 October 2026. - [Update on the status of the team, June 2026](https://make.wordpress.org/plugins/2026/06/13/update-on-the-status-of-the-team-june-2026/). WordPress Plugins Team, 13 June 2026, checked 7 October 2026. - [Submitting your app to the Webflow Marketplace](https://developers.webflow.com/apps/docs/marketplace/submitting-your-app). Webflow developer docs, checked 7 October 2026. - [Longer App Store review times: what you need to know](https://community.shopify.dev/t/longer-app-store-review-times-what-you-need-to-know/31728). Shopify developer community (Shopify staff), 26 February 2026, checked 7 October 2026.