HubSpot App Marketplace Scraper

Extract app listings, vendors, install counts, ratings, pricing signals, support links, and public listing details from the HubSpot App Marketplace.

Use this actor when you need a structured dataset of HubSpot ecosystem apps for lead generation, partner research, competitive intelligence, category monitoring, or sales enablement.

---

What does HubSpot App Marketplace Scraper do?

HubSpot App Marketplace Scraper collects public app records from ecosystem.hubspot.com/marketplace/apps.

It uses HubSpot's public marketplace RPC endpoints instead of slow browser automation.

That means runs are fast, low-cost, and suitable for repeat monitoring.

The actor can scrape:

• App names
• Vendor and provider names
• Marketplace URLs
• App summaries and overview text
• Install counts
• Ratings and review counts
• HubSpot certification signals
• Product and connection types
• Category labels and search terms
• Pricing plan labels when listed
• Company, support, setup, terms, and privacy URLs
• Feature names and feature descriptions
• Screenshots and app icons

Who is it for?

This actor is useful for teams that sell to, partner with, or analyze HubSpot ecosystem vendors.

Typical users include:

• SaaS sales teams building HubSpot app vendor lead lists
• Partnership teams mapping integration opportunities
• RevOps teams tracking tools used in the HubSpot ecosystem
• Market researchers monitoring category growth
• Agencies comparing apps in CRM, email, ecommerce, or automation categories
• Product marketers watching competitor positioning
• Data teams enriching internal vendor databases

Why use this actor?

The HubSpot Marketplace is valuable but not convenient to export manually.

This actor turns public listing pages into normalized JSON records.

You can run it once for a category export or schedule it to detect new apps and listing changes.

Benefits:

• No login required
• No browser rendering required
• Public marketplace data only
• Clean fields ready for CSV, Excel, API, or BI tools
• Works with search phrases, category filters, and marketplace URLs
• Includes detail fields that are usually hidden behind client-side rendering

Data fields

The default dataset contains one item per HubSpot app.

Field	Description
listingId	HubSpot listing ID
appName	App listing name
vendorName	Vendor/company name
providerName	Provider from search results
summary	Short listing tagline
overviewText	Cleaned listing overview
marketplaceUrl	Public HubSpot Marketplace listing URL
installCount	Public install count
rating	Average rating when available
reviewCount	Number of reviews when available
certified	Whether HubSpot marks the app as certified
categoryLabels	Public category labels
pricingPlans	Pricing plan labels when visible
companyUrl	Vendor website URL
supportUrl	Vendor support URL
supportEmail	Support email or support contact value
features	Feature names and descriptions
screenshots	Screenshot URLs

How much does it cost to scrape HubSpot Marketplace apps?

The actor uses pay-per-event pricing.

You pay a small start fee and a per-app fee for each saved app record.

Because the actor uses HTTP calls to public HubSpot marketplace endpoints, compute usage is low.

A small test run with 100 apps is the recommended first run.

Exact billing is shown by Apify before and after each run.

Input options

You can control the scrape with these inputs:

• searchQueries — marketplace search phrases such as email marketing or sales automation
• categories — HubSpot category values such as EMAIL, CRM, or MARKETING_AUTOMATION
• startUrls — HubSpot Marketplace URLs with eco_search or eco_CATEGORY query params
• maxItems — maximum apps to save
• includeDetails — fetch detailed app records for support links, overview, features, and screenshots
• requestDelayMs — optional delay between requests

Example input

{
  "searchQueries": ["sales automation", "email marketing"],
  "maxItems": 100,
  "includeDetails": true,
  "requestDelayMs": 150
}

Category example

{
  "categories": ["EMAIL", "CRM"],
  "maxItems": 200,
  "includeDetails": true
}

Useful category values include:

• EMAIL
• CRM
• MARKETING_AUTOMATION
• E_COMMERCE
• DATA_QUALITY_BACKUP
• CUSTOMER_SUCCESS
• HELP_DESK
• ACCOUNTING
• ADVERTISING
• COLLABORATION

Marketplace URL example

{
  "startUrls": [
    {
      "url": "https://ecosystem.hubspot.com/marketplace/search?eco_search=crm&eco_CATEGORY=CRM"
    }
  ],
  "maxItems": 100,
  "includeDetails": true
}

Output example

{
  "listingId": 30050897,
  "appName": "Gmail",
  "vendorName": "HubSpot",
  "summary": "Bring HubSpot to your inbox with the HubSpot integration for Gmail.",
  "marketplaceUrl": "https://ecosystem.hubspot.com/marketplace/listing/gmail",
  "installCount": 527170,
  "rating": 3.99,
  "reviewCount": 3418,
  "certified": true,
  "categoryLabels": ["Email"],
  "companyUrl": "https://www.hubspot.com/",
  "supportUrl": "https://help.hubspot.com/"
}

How to run

1. Open the actor on Apify.
2. Enter search queries, categories, or HubSpot Marketplace URLs.
3. Set maxItems to the number of app records you need.
4. Keep includeDetails enabled if you need support links and feature text.
5. Run the actor.
6. Export the dataset as JSON, CSV, Excel, XML, or via API.

Tips for best results

Start with a narrow query when researching a niche.

Use category filters when you want broad category coverage.

Use includeDetails: false for a quick install-count and rating scan.

Use includeDetails: true for lead generation and vendor enrichment.

Schedule recurring runs to monitor new apps in a category.

Integrations

The dataset works well with common Apify integrations.

Examples:

• Export HubSpot app leads to Google Sheets.
• Send new vendors to a CRM enrichment workflow.
• Compare install counts and reviews in a BI dashboard.
• Trigger alerts when new apps appear in a category.
• Feed app descriptions into an internal competitive-intelligence database.

API usage

Run the actor from Node.js:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/hubspot-app-marketplace-scraper').call({
  searchQueries: ['crm'],
  maxItems: 100,
  includeDetails: true,
});
console.log(run.defaultDatasetId);

Python API usage

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/hubspot-app-marketplace-scraper').call(run_input={
    'categories': ['EMAIL'],
    'maxItems': 100,
    'includeDetails': True,
})
print(run['defaultDatasetId'])

cURL API usage

curl "https://api.apify.com/v2/acts/automation-lab~hubspot-app-marketplace-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchQueries":["sales automation"],"maxItems":100,"includeDetails":true}'

MCP usage

Use this actor from Claude or other MCP-compatible tools through Apify MCP.

MCP server URL:

https://mcp.apify.com/?tools=automation-lab/hubspot-app-marketplace-scraper

Claude Code setup:

$claude mcp add apify-hubspot-marketplace "https://mcp.apify.com/?tools=automation-lab/hubspot-app-marketplace-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-hubspot-marketplace": {
      "url": "https://mcp.apify.com/?tools=automation-lab/hubspot-app-marketplace-scraper"
    }
  }
}

Example prompts:

• "Scrape the top 100 HubSpot CRM apps and summarize the largest vendors."
• "Find HubSpot Marketplace apps in the email category with public support URLs."
• "Monitor new HubSpot marketing automation apps every week."

Common workflows

Lead generation workflow:

1. Search a HubSpot category.
2. Export app names, vendors, websites, and support contacts.
3. Enrich companies in your CRM.
4. Assign outreach by category or install count.

Competitive monitoring workflow:

1. Run the same query weekly.
2. Compare install counts, ratings, and summaries.
3. Track new entrants and changed messaging.

Troubleshooting

If a run returns fewer records than expected, increase maxItems and check whether your category or search phrase is too narrow.

If category filters return zero records, use HubSpot's uppercase category values such as EMAIL, CRM, or MARKETING_AUTOMATION.

If detail fields are not needed, disable includeDetails for faster exports.

Limitations

This actor extracts public marketplace data only.

It does not log in to HubSpot.

It does not install apps.

It does not collect private customer data.

Some fields are optional because HubSpot vendors do not publish every contact, pricing, or support field.

Legality

This actor is designed to collect publicly available business listing information from the HubSpot App Marketplace.

You are responsible for using exported data in compliance with applicable laws, HubSpot terms, and your own data governance rules.

Avoid spam and respect opt-out requests when using vendor contact information.

Related scrapers

Other automation-lab actors that may pair well with this actor:

• https://apify.com/automation-lab/website-contact-finder
• https://apify.com/automation-lab/g2-scraper
• https://apify.com/automation-lab/github-marketplace-scraper
• https://apify.com/automation-lab/zoom-app-marketplace-scraper

FAQ

Can I scrape all HubSpot apps?

Yes. Leave searchQueries and categories empty, set maxItems, and keep includeDetails enabled if you need full public listing details.

Can I scrape only one category?

Yes. Use the categories input with values such as EMAIL or CRM.

Does it need proxies?

No proxy is required for normal runs because the actor uses public HubSpot marketplace endpoints.

Does it return emails?

It returns the public supportEmail value when a vendor publishes it. Some vendors use support URLs instead of email addresses.

Changelog

• Initial version: public HubSpot App Marketplace listing and detail extraction.