Webflow Apps Marketplace Scraper

Extract a structured, repeatable catalog of publicly listed apps from the Webflow Apps Marketplace. Use it to discover integrations, compare vendors, and maintain a current view of the no-code ecosystem without copying cards into spreadsheets by hand.

The actor reads public catalog and category pages. Optionally, it visits each public app detail page to enrich cards with developer, category, rating, review, and install or pricing signals when Webflow displays them.

What does it do?

Webflow Apps Marketplace Scraper turns public marketplace cards into dataset records. Start with the full catalog or one or more category URLs, apply an optional text filter, and choose how many apps to save.

Each run de-duplicates applications by marketplace slug. A changed or unavailable detail page does not discard a valid catalog card: the actor keeps the listing-level record and leaves unavailable optional fields empty.

Who is it for?

• Partnership teams building an integration landscape for a Webflow product.
• SaaS product marketers monitoring app categories, competitors, and positioning.
• Agencies and consultants researching tools for a Webflow client stack.
• Data teams that need a refreshable public-source dataset rather than a one-off export.
• Founder-led teams qualifying adjacent products before outreach or co-marketing research.

Why use this scraper?

The Webflow marketplace is useful but designed for browsing one card at a time. This actor creates a machine-readable app inventory that can be filtered, exported, compared, and refreshed on a schedule.

• 🧭 Focus on the full catalog or a category such as automation.
• 🔎 Filter cards by a keyword in their public name or description.
• 🧩 Preserve categories and public marketplace URLs for downstream matching.
• 🛟 Keep partial records when optional detail enrichment is unavailable.
• 📦 Export JSON, CSV, Excel, or connect the dataset to an Apify integration.

What data do I get?

Field	Description
name	Public Webflow Marketplace app name.
slug	Stable marketplace identifier used for de-duplication.
developer	Public developer or vendor name when displayed.
categories	Public category labels associated with the app.
description	Marketplace card or detail-page description.
pricingSignals	Public install, plan, or pricing-related text when available.
rating	Public numeric rating when displayed.
reviewCount	Public review count when displayed.
detailUrl	Canonical public Webflow Marketplace app URL.
iconUrl	Public app icon URL when available.
scrapedAt	ISO timestamp for this extracted record.

Choose a source URL

Leave startUrls empty to scrape the public catalog at https://webflow.com/apps. To focus the result set, provide a public category page such as:

{
  "startUrls": [{ "url": "https://webflow.com/apps/automation" }],
  "maxItems": 20
}

You can also provide several public marketplace or category URLs. The actor de-duplicates overlapping cards across all sources.

Filter the marketplace

Use search for a case-insensitive client-side filter over public app names and card descriptions. It is useful for focused research when a category is still broad.

{
  "startUrls": [{ "url": "https://webflow.com/apps" }],
  "search": "analytics",
  "maxItems": 30
}

A filter can legitimately return no records. Try a shorter brand, product, or workflow term if the marketplace wording differs from your query.

Enrich app detail pages

Set includeDetails to true when you need the additional public signals visible on individual app pages.

{
  "startUrls": [{ "url": "https://webflow.com/apps/automation" }],
  "maxItems": 20,
  "includeDetails": true
}

Listing-only mode is usually the best option for frequent catalog snapshots. Detail enrichment is better for a vendor audit, CRM enrichment, or a partnership research workflow. Public pages do not expose the same information for every app, so enrichment fields remain optional.

How much does it cost to scrape Webflow Marketplace apps?

This actor uses pay-per-event pricing: a $0.005 start event and a per-saved-app event. The current BRONZE tier is $0.000028918 per app. Higher-volume tiers receive automatic discounts in the Apify Console; the final tier-specific price is shown before you start a run.

You are charged for saved app records, not for every public request. Listing-only catalog monitoring is lightweight. Detail enrichment can make more public requests, but billing remains tied to successfully saved app records.

Quick start

1. Open the actor in Apify.
2. Keep the default catalog source or add a public Webflow category URL.
3. Set a low maxItems for the first run, for example 20.
4. Optionally set search or enable includeDetails.
5. Start the run and export the dataset in your preferred format.

Input reference

Input	Required	What it controls
startUrls	No	Public Webflow Apps catalog or category URLs. Defaults to the catalog.
search	No	Case-insensitive filter for public app names and descriptions.
maxItems	No	Maximum records to save; default is 20 and maximum is 1,000.
includeDetails	No	Visits public app detail pages for optional enrichment.

Keep the first run small. Once the output matches your workflow, raise maxItems or schedule periodic category snapshots.

Output example

{
  "name": "Example Integration",
  "slug": "example-integration",
  "developer": "Example Vendor",
  "categories": ["Automation", "Marketing"],
  "description": "Connect a Webflow workflow to a public integration.",
  "pricingSignals": ["Free plan available"],
  "rating": 4.8,
  "reviewCount": 12,
  "detailUrl": "https://webflow.com/apps/detail/example-integration",
  "iconUrl": "https://assets-global.website-files.com/example.png",
  "scrapedAt": "2026-07-11T00:00:00.000Z"
}

Values in the example illustrate the schema. The actor only emits values that are publicly present on the source page and does not invent vendor, pricing, or review information.

Build an integration landscape

Run one category at a time, then combine exports by slug or detailUrl. Typical columns for a landscape include app name, developer, categories, description, and public pricing signals.

For a recurring workflow, save one task per category and schedule it. This produces comparable snapshots that reveal newly listed apps, category changes, or vendor-description changes.

Research competitors and alternatives

Use a keyword filter for a focused slice, then export the dataset to a spreadsheet or warehouse. Pair the Webflow source with your own product categories, partner list, or CRM accounts to find overlaps and gaps.

Do not interpret a missing field as a negative claim. A blank rating, review count, developer, or pricing signal only means that the corresponding public page did not expose a value the actor could reliably extract.

Tips for reliable runs

• ✅ Begin with maxItems: 20 to validate your source and filter.
• ✅ Use category URLs for targeted, repeatable monitoring.
• ✅ Use listing-only mode for quick, frequent catalog snapshots.
• ✅ Enable details only when optional public vendor signals matter.
• ✅ Use several smaller source URLs when comparing categories.
• ✅ Treat marketplace content as a point-in-time public snapshot.

Integrations

Export to a spreadsheet

After a run, use the Apify dataset export to download CSV or Excel. This is useful for a partnership manager who needs a shareable category map without maintaining an API integration.

Send records to a database

Connect the default dataset to Make, Zapier, Google Sheets, or your warehouse workflow. Use slug as the stable key and scrapedAt as the snapshot timestamp.

Track marketplace changes

Schedule a category run weekly, retain prior datasets, and compare name, categories, and description by slug. This creates a lightweight monitor for new or repositioned Webflow apps.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/webflow-apps-marketplace-scraper').call({
  startUrls: [{ url: 'https://webflow.com/apps/automation' }],
  maxItems: 20,
  includeDetails: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("automation-lab/webflow-apps-marketplace-scraper").call(
    run_input={
        "startUrls": [{"url": "https://webflow.com/apps/automation"}],
        "maxItems": 20,
        "includeDetails": True,
    }
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL

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

Use with Apify MCP

In Claude Code, add Apify MCP with this actor available:

$claude mcp add apify -- npx -y @apify/mcp-server --tools automation-lab/webflow-apps-marketplace-scraper

For Claude Desktop, configure the Apify MCP server and open:

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

Example prompts:

• “Find public Webflow automation apps and return their marketplace URLs.”
• “Create a table of Webflow Marketplace apps with developer, categories, and ratings.”
• “Collect 50 Webflow apps that mention analytics and export their public descriptions.”

Data quality

The actor extracts public Webflow Marketplace content as displayed at run time. Marketplace cards, category membership, ratings, and vendor copy can change without notice. The scraper records a timestamp so you can distinguish snapshots.

The actor validates URLs, de-duplicates by slug, and handles individual listing or detail-page failures independently. A partial output is preferable to dropping a complete catalog run because one optional page changed.

Limitations

• The actor only accesses publicly available Webflow Marketplace pages.
• It does not bypass login, access controls, CAPTCHAs, or paywalls.
• Category pages may show a subset or pagination pattern determined by Webflow.
• Optional fields can be blank when the public page does not display them.
• maxItems is a cap, not a guarantee that the source has that many matching apps.
• Marketplace markup can change; review logs and run a small validation job after a major site redesign.

Troubleshooting

Why did my category run return fewer apps than expected?

Webflow may feature, paginate, or limit the cards available on a category page. Increase maxItems, run the catalog plus relevant categories, or split the research into separate source URLs.

Why are developer, rating, or reviewCount empty?

Those are optional public signals. Enable includeDetails for an additional public-page pass, but retain blanks when Webflow does not display the value.

Why did my keyword filter return no apps?

The filter matches public card names and descriptions. Use a shorter term, a product name, or a category URL. An empty dataset is a valid result when no public card matches the exact text.

How do I reduce run time?

Use listing-only mode, one category URL, and a small maxItems. Enable detail enrichment only for workflows that need the extra public fields.

Responsible use and legality

Use this actor only for legitimate business research and in compliance with Webflow’s terms, applicable law, and your organization’s privacy obligations. Do not use marketplace information to spam developers, evade access controls, or make unsupported claims about vendors.

The actor collects public business and product information. You remain responsible for how you store, combine, contact, or act on exported data.

FAQ

Does this require a Webflow account or API key?

No. The actor is designed for publicly accessible Webflow Apps Marketplace pages and does not require your Webflow credentials.

Can I scrape the full marketplace?

Yes. Leave startUrls empty or use https://webflow.com/apps, then set an appropriate maxItems. Start small to confirm the output you need.

Can I monitor changes over time?

Yes. Schedule recurring runs, retain the datasets, and compare records by slug and scrapedAt.

Is every app detail field guaranteed?

No. Vendor and marketplace pages vary. The actor returns only reliable public values and leaves optional fields blank when a page does not expose them.

Related scrapers

Browse the Automation Lab actor portfolio for adjacent research workflows. This actor intentionally focuses on the Webflow Apps Marketplace, making it a good fit for Webflow-specific integration discovery rather than a generic software directory crawl.

Changelog

Read the ./.actor/CHANGELOG.md for release notes.