Miro Marketplace Scraper

Extract public Miro Marketplace apps, vendors, categories, pricing labels, screenshots, support links, and compliance URLs from Miro's app ecosystem.

What does Miro Marketplace Scraper do?

Miro Marketplace Scraper turns the public Miro Marketplace into a clean dataset. It reads the public marketplace page, parses the embedded Next.js app catalog, and saves one row per app. Use it to monitor Miro integrations, find partner leads, compare app categories, or build a repeatable ecosystem database.

Who is it for?

• 🧩 SaaS partnership teams tracking tools that integrate with Miro.
• 📊 Competitive intelligence teams watching collaboration and whiteboard ecosystems.
• 🧑‍💻 Developer relations teams looking for app vendors and integration partners.
• 🧾 Procurement and security teams collecting support, privacy, and terms links.
• 🏢 Agencies building reports about collaboration software marketplaces.

Why use this actor?

• HTTP-only extraction: no browser overhead for the default Miro Marketplace page.
• Public data only: no login, cookies, or private API keys required.
• Rich app metadata: app, vendor, categories, pricing labels, media, and compliance links.
• Repeatable exports: run daily or weekly to detect new apps and category changes.
• API-ready output: use Apify datasets, webhooks, integrations, or MCP workflows.

What data can I extract from Miro Marketplace?

Field	Description
appName	Marketplace app name
appUrl	Public Miro Marketplace app URL
vendorName	Developer or vendor name
vendorUrl	Vendor website when present
tagline	Short marketplace description
description	Longer HTML-stripped app description when requested
categories	Human-readable marketplace categories
categoryKeys	Stable category keys useful for filtering
pricing	Miro pricing label such as Free or Free and paid
isFree	Boolean interpretation of the pricing label when known
iconUrl	App icon URL
screenshots	Screenshot, GIF, or video URLs
supportUrl	Support URL or email when present
privacyPolicyUrl	Privacy policy URL when present
termsOfServiceUrl	Terms URL when present
marketplaceRank	Position in the source payload
sourceUrl	Miro page that produced the record
scrapedAt	ISO timestamp for the extraction

How much does it cost to scrape Miro Marketplace apps?

This actor uses pay-per-event pricing. There is a small start charge and a per-item charge for each saved app record. The exact live prices are shown on the Apify Store pricing panel. Use maxItems for tight cost control during testing. A typical default run can extract 100 app records from one HTTP request.

Quick start

1. Open the actor on Apify.
2. Keep the default https://miro.com/marketplace/ start URL.
3. Set maxItems to the number of apps you need.
4. Optionally add searchTerm or categoryKeys filters.
5. Click Start.
6. Export the dataset as JSON, CSV, Excel, XML, or via API.

Input options

startUrls

Miro Marketplace pages to scrape. The default marketplace URL currently exposes hundreds of public app records in its initial payload.

maxItems

Maximum number of app rows to save. Use a low value for tests and a higher value for full exports.

searchTerm

Optional local text filter. It checks app name, vendor name, short description, full description, and category captions.

categoryKeys

Optional exact category-key filter. Examples include free, free-and-paid, built-by-miro, strategy-planning-apps, and projects-tasks.

includeFullDescription

When enabled, the actor includes longer app descriptions stripped of HTML markup. Disable it for lighter exports.

delayMs

Polite delay between multiple start URLs. For the default single URL, this has almost no runtime impact.

Example input: full marketplace sample

{
  "startUrls": [{ "url": "https://miro.com/marketplace/" }],
  "maxItems": 100,
  "includeFullDescription": true,
  "delayMs": 500
}

Example input: planning apps

{
  "startUrls": [{ "url": "https://miro.com/marketplace/" }],
  "maxItems": 50,
  "searchTerm": "planning",
  "includeFullDescription": true
}

Example input: built by Miro

{
  "startUrls": [{ "url": "https://miro.com/marketplace/" }],
  "maxItems": 100,
  "categoryKeys": ["built-by-miro"],
  "includeFullDescription": false
}

Example output

{
  "appName": "Jira Cards",
  "appUrl": "https://miro.com/marketplace/jira/",
  "vendorName": "Miro",
  "tagline": "Visualize, edit, or create Jira tasks directly in Miro",
  "categories": ["Projects & tasks", "Strategy & planning", "Agile workflows"],
  "pricing": "Free with Miro plans",
  "isFree": true,
  "marketplaceRank": 1,
  "sourceUrl": "https://miro.com/marketplace/"
}

Tips for best results

• Start with maxItems: 25 if you are exploring the output shape.
• Use searchTerm for quick keyword lists such as agile, diagram, Jira, or AI.
• Use categoryKeys when you need a stable repeatable filter.
• Keep includeFullDescription enabled for lead research and disabled for light monitoring.
• Schedule runs weekly if you want to spot new integrations.

Integrations

• Send new app rows to Google Sheets for ecosystem tracking.
• Trigger a webhook when a scheduled run finishes.
• Feed vendor URLs into enrichment or contact-finder actors.
• Store historical datasets and compare category changes over time.
• Export records to BI tools for marketplace trend dashboards.

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/miro-marketplace-scraper').call({
  startUrls: [{ url: 'https://miro.com/marketplace/' }],
  maxItems: 100,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/miro-marketplace-scraper').call(run_input={
    'startUrls': [{'url': 'https://miro.com/marketplace/'}],
    'maxItems': 100,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~miro-marketplace-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://miro.com/marketplace/"}],"maxItems":100}'

MCP usage

Use Apify MCP to call this actor from Claude Desktop, Claude Code, or other MCP clients.

Add the Apify MCP server in Claude Code:

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

Claude Desktop JSON configuration:

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

MCP server URL:

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

Example prompts:

• "Run the Miro Marketplace Scraper for built-by-miro apps and summarize vendors."
• "Export the first 100 Miro Marketplace apps and group them by pricing label."
• "Find Miro apps related to planning and return vendor websites."

Monitoring new Miro apps

Schedule the actor to run on a cadence. Keep the same input each time. Compare new datasets by appId, appKey, or appUrl. This gives you a practical Miro app marketplace monitor without building custom infrastructure.

Lead generation workflow

1. Run the actor with a category or keyword filter.
2. Export vendorName, vendorUrl, supportUrl, and compliance URLs.
3. Deduplicate vendors in your CRM or spreadsheet.
4. Enrich vendor websites with contact or company data.
5. Prioritize vendors by category and marketplace rank.

Competitive intelligence workflow

1. Run a full marketplace export monthly.
2. Track app counts by category.
3. Watch pricing labels for free, paid, and Miro-plan apps.
4. Identify vendors appearing in strategic categories.
5. Compare new rows against your historical dataset.

FAQ

Why did I get fewer apps than expected?

Check maxItems, searchTerm, and categoryKeys. Filters are applied after the marketplace payload is parsed. A narrow keyword or category can intentionally return fewer records.

Why are rating or review fields missing?

The observed public Miro Marketplace payload does not expose reliable rating or review counts. The actor avoids null-only fields and focuses on the metadata available in the public payload.

Do I need proxies?

No proxy is required for the default public marketplace page. The actor is HTTP-only and uses polite headers and delays.

Legality and ethical use

This actor extracts publicly available Miro Marketplace metadata. Do not use it to collect private user data, bypass access controls, or overload the target site. Review Miro's terms and your local regulations before using scraped data in production workflows.

Related scrapers

Automation Lab publishes actors for marketplace, SaaS, lead, and web data workflows. Use related marketplace scrapers when you need other ecosystems such as Slack, HubSpot, Zoom, or app-store style directories. Keep each actor focused on the source website for cleaner schemas and easier monitoring.

Changelog

• 0.1 Initial HTTP implementation for public Miro Marketplace app metadata.

Support

If a run fails or the output looks wrong, open an Apify issue with your run URL and input. Include the expected category, search term, and approximate record count so the problem can be reproduced quickly.