monday + Zapier + Make App Marketplace Scraper

Aggregate app and integration listings across monday.com, Zapier, and Make.com. Returns app name, category, vendor, rating, reviews, Zapier action/trigger counts, pricing, and free-plan flag — in one canonical schema tagged by source marketplace.

---

iPaaS Marketplace Scraper Features

• Single run covers three iPaaS marketplaces: monday, Zapier, and Make
• Returns 17 fields per app including vendor name, rating, review count, and pricing text
• Zapier-specific signal: action count, trigger count, Zap usage count, premium flag, and popularity score
• Free-plan availability surfaced as a boolean
• Pick which marketplaces to run via the sources array — one, two, or all three
• Includes residential proxy by default. Make.com sits behind Cloudflare and rejects datacenter IPs.

---

Who Uses iPaaS Marketplace Data?

• iPaaS builders — Benchmark app coverage, pricing, and rating distributions across competing platforms before scoping a new integration
• SaaS product teams — Find which platforms already integrate with your tool, and which competitors integrate with the platforms you don't yet support
• Sales and BD — Build outreach lists of app vendors building on platforms where you want to partner
• Investors and analysts — Track ecosystem growth: app counts per category, premium-app share, free-plan adoption
• Tech journalism — Map which integrations are gaining usage and which categories are saturated

---

How the iPaaS Marketplace Scraper Works

1. Pick sources — Set sources to any subset of monday, zapier, and make. Default is all three.
2. Per-source crawl — Each marketplace has its own listing endpoint and pagination shape. The scraper handles each one separately and normalizes results.
3. Schema canonicalization — Output is one flat schema tagged with source_marketplace. Source-specific fields (Zapier actions/triggers) populate only on relevant rows.
4. Export — One record per app across all sources in your Apify dataset.

---

Input

All three sources

{
  "sources": ["monday", "zapier", "make"],
  "maxItems": 0
}

Zapier only

{
  "sources": ["zapier"],
  "maxItems": 500
}

monday + Make

{
  "sources": ["monday", "make"],
  "maxItems": 300
}

Field	Type	Default	Description
sources	array	["zapier"]	Subset of monday, zapier, make.
maxItems	integer	10	Cap on apps across all sources combined. 0 = unlimited.
proxyConfiguration	object	BUYPROXIES94952 residential	Proxy settings. Residential is required for Make.com.

---

iPaaS Marketplace Scraper Output Fields

{
  "source_marketplace": "zapier",
  "app_name": "Notion",
  "slug": "notion",
  "description": "Notion is the connected workspace where better, faster work happens.",
  "category": "Notes + Productivity",
  "vendor_name": "Notion Labs",
  "vendor_url": "https://www.notion.so",
  "rating": 4.6,
  "reviews_count": 482,
  "actions_count": 7,
  "triggers_count": 4,
  "pricing_text": "Free plan available",
  "free_plan": true,
  "app_url": "https://zapier.com/apps/notion/integrations",
  "icon_url": "https://zapier-images.imgix.net/storage/services/notion.png",
  "is_premium": false,
  "popularity": 0.92,
  "zap_usage_count": 48000,
  "days_since_last_update": 14
}

Field	Type	Description
source_marketplace	string	monday, zapier, or make
app_name	string	App or integration name
slug	string	URL slug identifier
description	string	Short description of the app
category	string	Primary category label
vendor_name	string	Developer or vendor name
vendor_url	string	Developer or vendor website URL
rating	number	Average user rating (0-5)
reviews_count	number	Total number of reviews
actions_count	number	Zapier action count (Zapier only)
triggers_count	number	Zapier trigger count (Zapier only)
pricing_text	string	Raw pricing description
free_plan	boolean	App has a free plan
app_url	string	URL to the app listing page
icon_url	string	URL of the app icon or logo
is_premium	boolean	App is marked premium (Zapier only)
popularity	number	Relative popularity score (Zapier only)
zap_usage_count	number	Active Zaps using this app (Zapier only)
days_since_last_update	number	Days since last update

---

FAQ

How do I compare iPaaS marketplaces in a single dataset?

iPaaS Marketplace Scraper aggregates monday, Zapier, and Make into one schema with source_marketplace as the discriminator. Run once with all three sources selected, then group or pivot by source downstream.

How much does this actor cost to run?

iPaaS Marketplace Scraper uses pay-per-event pricing on the default_2603_basic profile at a 2.0x coefficient. The higher coefficient covers residential proxy bandwidth required for Make.com. Per-record cost is low single cents.

Why are Zapier-specific fields blank for monday and Make rows?

iPaaS Marketplace Scraper uses one canonical schema across all three sources. Action count, trigger count, premium flag, popularity, and Zap usage exist only on Zapier listings and stay empty for the others. The source_marketplace field tells you which row supports which fields.

Does this actor need proxies?

iPaaS Marketplace Scraper requires residential proxy. Make.com sits behind Cloudflare and rejects datacenter IPs. The default BUYPROXIES94952 residential group is configured automatically; leave it alone unless you have a specific reason to override.

Can I filter by category at the input stage?

iPaaS Marketplace Scraper does not currently filter by category at input. Categories are returned per app, so a downstream category = 'Productivity' filter on the dataset is straightforward.

---

Need More Features?

Need per-marketplace input filters (Zapier category, monday Hub compatibility), review-text extraction, or scheduled re-runs to track ecosystem growth? Open an issue or get in touch.

Why Use iPaaS Marketplace Scraper?

• One schema across three marketplaces — source_marketplace is the only field you have to switch on. Everything else maps to the same column names.
• Zapier action/trigger counts — Most iPaaS scrapers stop at app name and category. This one returns the integration depth signal that actually matters when scoping a partner build.
• Cloudflare handled — Make.com is the awkward one, and the actor ships with the residential proxy group that gets past it. You don't have to configure that yourself.