Do I Need to Create a Separate HubSpot App for a Shopify–HubSpot Integration?

Develop, Build & Integrate Marketplace Apps
1

Hi HubSpot Support,

I am developing an integration between Shopify and HubSpot.

The main application is a Shopify app. Shopify merchants install the app on their Shopify store, and then connect their own HubSpot account through the HubSpot OAuth flow. After authorization, our application synchronizes the merchant’s Shopify data with the corresponding HubSpot account.

Currently, our HubSpot app is not listed on the HubSpot App Marketplace, and we understand that marketplace distribution apps are limited to 25 installs until the app is listed.

I would like to clarify the correct setup and Marketplace listing requirements for this type of integration:

  1. Do I need to create and maintain a separate HubSpot app in addition to my Shopify app?
  2. Or can I keep the Shopify app as the main application, create a HubSpot public app/project only for OAuth and API access, and then submit that HubSpot app for Marketplace listing?
  3. Since the integration is primarily initiated from the Shopify app, is it sufficient to provide a demo video showing the complete flow:
    • Install the Shopify app
    • Click “Connect HubSpot”
    • Authorize the HubSpot account through OAuth
    • Sync Shopify data to the connected HubSpot account
    • Verify the synchronized data in HubSpot
  4. Are there any HubSpot-side UI components, such as App Cards or UI Extensions, that are mandatory for Marketplace approval for this type of integration?

Our intended user flow is:

Shopify Store → Shopify App → Connect HubSpot → HubSpot OAuth → Merchant authorizes their HubSpot account → Shopify data is synchronized to that HubSpot account.

Could you please confirm whether this architecture is sufficient for HubSpot Marketplace listing, and whether we need to build any additional functionality directly inside the HubSpot UI?

Thank you.

3

Hi @Ethan and thanks for asking the HubSpot Community!

To reply to your questions:

1. One HubSpot app vs. separate apps

You only need one HubSpot app. Your Shopify app can remain the primary application; you create a single HubSpot public app (built on the developer platform) purely for OAuth/API access, and that’s the app you submit for Marketplace listing. There’s no requirement to build separate HubSpot apps for the same integration. See App listing requirements.

2. Architecture (Shopify app as primary, HubSpot app for OAuth only)

This is fine and is a normal pattern. The minimum requirements state your app must:

  • Use OAuth as its sole authorization method
  • Authorize all API requests with a single HubSpot app ID/OAuth client ID
  • Not redirect to or require another public/private app to function
  • Have at least 3 active, unique installs (unaffiliated with your org) with real API/webhook activity in the past 30 days before you can submit

It can live in your Shopify app, with HubSpot only handling OAuth + API sync.

3. Demo video sufficiency

Yes, the listing process requires a demo video showing how your app works, uploaded in the App details tab, per How to Make a Great App Demo Video. A video covering install → connect HubSpot → OAuth → sync → verify data in HubSpot matches what’s expected. You’ll also need screenshots (up to 8), an app overview, and a Shared data table describing exactly which objects sync and in which direction (matching your OAuth scopes).

4. Are App Cards/UI Extensions mandatory?

No, app cards/UI extensions are optional. The docs only impose additional requirements (“App card requirements”, naming, logos, sensitive data restrictions) if you choose to build one. A pure background-sync integration with no HubSpot-side UI is a valid, common pattern and isn’t required to add UI Extensions.

So, your intended flow (Shopify Store → Shopify App → Connect HubSpot → OAuth → sync data) is sufficient for listing, provided:

  • The HubSpot app uses OAuth only, with a single app ID
  • You have ≥3 real unique installs with genuine API activity in the last 30 days
  • You provide public setup documentation specific to the HubSpot integration (setup guide requirements)
  • You fill out the Shared Data table accurately for whatever CRM objects you sync
  • You meet the standard listing fields (pricing, support contact, ToS/Privacy links, etc.)

You do not need to build additional in-HubSpot UI functionality unless you want to offer it.

App listing requirements How to list your appSetup guide requirements

I’d love to hear from our Top Experts: Hi @Anton, @evaldas and @zach_threadint do you have additional insights you’d like to share, please?

Thanks so much and have a lovely weekend!

Bérangère

This post was created with the assistance of AI tools