Intercom App Store Scraper

Extract Intercom App Store integrations, categories, vendors, pricing signals, install links, setup text, and marketplace metadata from public Intercom App Store data.

Intercom App Store Scraper turns the public marketplace at intercom.com/app-store into a structured dataset for partnership research, SaaS ecosystem mapping, integration intelligence, and lead generation.

What does Intercom App Store Scraper do?

This actor collects public Intercom App Store app listings through Intercom's public app-store API.

It can export the whole marketplace, focus on specific category slugs, run marketplace search queries, or fetch known app package IDs.

Each app row includes vendor/developer signals, category labels, capability tags, pricing and install signals, documentation/support links, media URLs, setup snippets, and source URLs.

Who is it for?

• 🤝 SaaS partnership teams mapping companies that build in the Intercom ecosystem.
• 📈 Marketplace analysts tracking category coverage, app positioning, and pricing signals.
• 🧲 Lead-generation teams finding vendors with Intercom integrations.
• 🧪 Product teams benchmarking onboarding, install flows, and integration messaging.
• 🗂️ Data teams building repeatable app-store enrichment pipelines.

Why use it?

The Intercom App Store is useful but optimized for browsing, not analysis.

This actor provides repeatable exports with stable field names, deduplication, API-friendly output, and a low-cost HTTP implementation.

Use it when you need Intercom ecosystem data in CSV, JSON, Google Sheets, a CRM, or a data warehouse.

How much does it cost to scrape Intercom App Store apps?

The actor uses pay-per-event pricing.

• Start event: a small one-time run fee.
• Item event: one charge per saved app or category record.
• You control spend with maxItems and filters.

Final live prices are shown on the Apify Store pricing panel and are reflected in run charging events.

Data fields

Field	Description
recordType	app or category
recordId	Intercom app package or category ID
name	App or category name
appStoreUrl	Public Intercom App Store URL
description	Short marketplace description
longDescription	Longer app positioning/setup text when available
builtBy	Intercom or third-party developer name
developerHomepageUrl	Developer or learn-more page
installUrl	Install/connect URL exposed by Intercom
installType	OAuth/manual/internal install signal
pricingModel	Public pricing/trial/free signal
pricingPageUrl	Vendor pricing URL when provided
supportEmail	Support contact when provided
documentationUrl	Help docs or integration docs
categories	Intercom category names
categorySlugs	Intercom category slugs
capabilities	Intercom capability labels
whatItDoes	Extracted guide text around what the app does
setupRequirements	Extracted requirements text
setupSteps	Setup/connect headings
featureBullets	Bullet points from guide blocks
iconUrl, imageUrls, videoUrl	Media assets
scrapedAt	ISO timestamp for the run

Input options

maxItems

Maximum number of records to save. Use a small value for smoke tests and 100+ for marketplace analysis.

includeAllApps

Fetch the full public Intercom app catalog before applying maxItems. This is enabled by default.

searchQueries

Run Intercom App Store searches such as slack, analytics, hubspot, ai, or zendesk.

categories

Limit extraction to Intercom category slugs such as analytics, automation, crm, data-and-enrichment, for-support-teams, or for-sales-teams.

appPackageIds

Fetch specific known app slugs, for example google-analytics, salesforce-by-intercom, or jira-for-intercom-4g7a.

includeCategoryRecords

Also output Intercom category taxonomy records. App rows remain the main dataset.

Example input: full marketplace sample

{
  "maxItems": 100,
  "includeAllApps": true,
  "includeCategoryRecords": false
}

Example input: search-based lead list

{
  "maxItems": 50,
  "includeAllApps": false,
  "searchQueries": ["slack", "analytics", "crm"]
}

Example input: category monitoring

{
  "maxItems": 150,
  "includeAllApps": false,
  "categories": ["analytics", "automation", "data-and-enrichment"],
  "includeCategoryRecords": true
}

Example output

{
  "recordType": "app",
  "recordId": "salesforce-by-intercom",
  "name": "Salesforce",
  "appStoreUrl": "https://www.intercom.com/app-store/salesforce-by-intercom",
  "description": "Sync data and streamline workflows for sales, marketing and support",
  "builtBy": "Intercom",
  "pricingModel": "free_trial_available",
  "installType": "requires_oauth",
  "categories": ["CRM", "For sales teams"],
  "documentationUrl": "https://docs.intercom.com/integrations/integrate-with-salesforce",
  "scrapedAt": "2026-07-08T00:00:00.000Z"
}

How to run

1. Open the actor on Apify.
2. Set maxItems to the number of records you need.
3. Choose full catalog mode or provide search/category filters.
4. Start the run.
5. Download the dataset as JSON, CSV, Excel, or via API.

Tips for better results

• Use includeAllApps: true for broad ecosystem mapping.
• Use category filters when tracking a specific GTM segment.
• Use search queries for competitor or partner discovery.
• Keep scheduled runs under a fixed maxItems to control cost.
• Use scrapedAt to compare snapshots over time.

Integrations

Common workflows include:

• Export Intercom ecosystem leads to HubSpot or Salesforce.
• Join app names and developer URLs with enrichment tools.
• Monitor new apps by comparing scheduled datasets.
• Feed category coverage data into BI dashboards.
• Send pricing/support/documentation URLs to partnership researchers.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/intercom-app-store-scraper').call({
  maxItems: 100,
  includeAllApps: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.slice(0, 3));

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/intercom-app-store-scraper').call(run_input={
    'maxItems': 100,
    'includeAllApps': True,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items[:3])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~intercom-app-store-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"maxItems":100,"includeAllApps":true}'

MCP: use from Claude Desktop or Claude Code

Connect Apify MCP with this actor enabled.

Claude Code CLI setup:

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

Claude Desktop configuration:

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

Example prompts:

• "Run the Intercom App Store Scraper for 100 apps and summarize the most common pricing models."
• "Find Intercom App Store apps in analytics and CRM categories with public pricing URLs."
• "Compare today's Intercom app export with last week's dataset and list new vendors."

Scheduling and monitoring

Schedule weekly or monthly runs to detect new app listings, category changes, or updated pricing/documentation links.

For monitoring, keep includeAllApps enabled and set maxItems high enough to cover the catalog.

Data freshness

The actor reads Intercom's public app-store API at run time.

Results reflect public data visible during the run, including Intercom-side ordering, public fields, and currently exposed integration metadata.

Limitations

• The actor extracts public marketplace metadata only.
• It does not log into Intercom workspaces.
• It does not install apps or verify OAuth flows.
• Review/rating fields are included only if Intercom exposes them publicly in the source data.
• Vendor websites linked from the marketplace are not crawled.

Troubleshooting

If a run returns fewer records than expected, check whether maxItems, search queries, category slugs, or app package IDs narrowed the output.

If a category query returns zero rows, verify the slug from an Intercom category URL or run with includeCategoryRecords to inspect available slugs.

If you need every app, use includeAllApps: true and a maxItems value above the current catalog size.

Legality: is it legal to scrape the Intercom App Store?

This actor collects public marketplace metadata. You are responsible for using the data lawfully, respecting applicable terms, and complying with privacy and database laws in your jurisdiction.

Do not use the output for spam, deceptive outreach, or any workflow that violates Intercom's or vendors' rights.

Related scrapers

Other Automation Lab marketplace and ecosystem actors that may help adjacent workflows:

• https://apify.com/automation-lab/monday-app-marketplace-scraper
• https://apify.com/automation-lab/aws-marketplace-scraper
• https://apify.com/automation-lab/zoho-marketplace-scraper
• https://apify.com/automation-lab/atlassian-marketplace-scraper

FAQ

Can it scrape all Intercom App Store apps?

Yes. Use includeAllApps: true and set maxItems high enough to cover the catalog.

Can it scrape app detail pages?

The actor uses the public API that powers the detail pages, so it captures the structured detail fields without browser rendering.

Does it require proxies?

No proxy is required for the public API in normal use.

Can I get only Slack-related apps?

Yes. Set includeAllApps to false and searchQueries to ["slack"].

Can I monitor categories over time?

Yes. Schedule recurring runs with category filters and compare datasets by recordId and scrapedAt.

Support

If you need an additional field that is publicly visible on Intercom App Store pages, open an Apify issue with the app URL and expected field.