Pipedream Apps Directory Scraper

Scrape Pipedream's public app directory into clean Apify datasets.

Use it to collect app names, slugs, descriptions, categories, website URLs, API docs URLs, public app URLs, actions, triggers, and component names from pipedream.com/apps.

What does Pipedream Apps Directory Scraper do?

Pipedream Apps Directory Scraper extracts public integration metadata from the Pipedream app directory.

It turns app directory pages and public app detail data into structured rows.

Each row represents one Pipedream app.

The actor is useful when you need a current map of Pipedream's integration ecosystem.

It can scrape broad directory samples or a focused search query.

It can also target specific Pipedream app URLs.

Who is it for?

Automation consultants use it to compare platform coverage.

RevOps teams use it to audit which SaaS tools are supported.

SaaS partnership teams use it to find integration gaps.

Integration platform vendors use it for competitive intelligence.

Growth teams use it to find co-marketing and ecosystem opportunities.

Developers use it to inspect available Pipedream actions and triggers before building workflows.

Why use this actor?

✅ Structured output instead of manual directory browsing.

✅ Public app detail enrichment.

✅ Search-query runs for focused app categories.

✅ Specific app URL runs for repeatable monitoring.

✅ API-friendly datasets for BI, enrichment, and lead workflows.

✅ No Pipedream account required for the public data this actor collects.

What data can you extract?

Field	Description
appName	Pipedream app name
slug	URL slug
appId	Pipedream internal app ID
appUrl	Public Pipedream app URL
description	App description
status	Pipedream app status
premium	Whether the app is marked premium
category	Public category when available
websiteUrl	App website URL
apiDocsUrl	API documentation URL
logoUrl	Public logo URL
numActions	Number of actions when exposed
triggers	Trigger names
actions	Action names
componentNames	Combined component names
components	Component detail objects
scrapedAt	ISO scrape timestamp

How much does it cost to scrape Pipedream apps?

This actor uses pay-per-event pricing.

There is a small run-start event of $0.005 per run and a per-result event charged for each Pipedream app row saved.

The measured BRONZE per-result price is about $0.000052 per app. Other Apify plan tiers use automatic discounts: FREE about $0.000060, SILVER about $0.000041, GOLD about $0.000031, PLATINUM about $0.000021, and DIAMOND about $0.000015 per app.

You control cost with maxItems.

A small first run with maxItems: 25 costs roughly $0.0063 on BRONZE: $0.005 start fee plus about $0.0013 for results.

A realistic directory intelligence run with maxItems: 100 costs roughly $0.0102 on BRONZE: $0.005 start fee plus about $0.0052 for results.

A larger 1,000-app export costs roughly $0.057 on BRONZE before Apify platform usage costs: $0.005 start fee plus about $0.052 in result events.

The final price users see is calculated by Apify from the live pay-per-event pricing for their account tier.

How to scrape Pipedream apps

1. Open the actor on Apify.

2. Enter an optional searchQuery, such as crm, sales, or database.

3. Set maxItems to the number of apps you need.

4. Keep includeDetails enabled when you need actions, triggers, categories, docs URLs, and website URLs.

5. Run the actor.

6. Export the dataset as JSON, CSV, Excel, or via API.

Input options

searchQuery filters the public Pipedream app directory.

startUrls accepts app detail URLs such as https://pipedream.com/apps/notion.

maxItems limits the number of app rows saved.

includeDetails controls detail GraphQL enrichment.

maxComponentsPerApp limits the number of action/trigger/component names stored per app.

Example input

{
  "searchQuery": "crm",
  "maxItems": 100,
  "includeDetails": true,
  "maxComponentsPerApp": 50
}

Specific app URL example

{
  "startUrls": [
    { "url": "https://pipedream.com/apps/notion" },
    { "url": "https://pipedream.com/apps/slack" }
  ],
  "maxItems": 20,
  "includeDetails": true
}

Output example

{
  "appName": "Notion",
  "slug": "notion",
  "appId": "app_X7Lhxr",
  "appUrl": "https://pipedream.com/apps/notion",
  "description": "Notion is a new tool that blends your everyday work apps into one.",
  "category": "Productivity",
  "websiteUrl": "https://notion.so",
  "apiDocsUrl": "https://developers.notion.com/reference/intro",
  "actions": ["Append Block to Parent", "Create Comment"],
  "triggers": [],
  "source": "pipedream-graphql",
  "scrapedAt": "2026-07-07T00:00:00.000Z"
}

Tips for best results

Start with a focused query when exploring a niche.

Use an empty search query when you need a broad directory snapshot.

Keep detail extraction on for competitive intelligence.

Lower maxComponentsPerApp when you only need high-level coverage.

Use specific app URLs for monitoring key integrations.

Common use cases

Build a Pipedream integration coverage database.

Compare Pipedream app coverage with Zapier, Make, and n8n.

Find apps with rich action coverage.

Find categories where your SaaS should build integrations.

Create lead lists for partnership outreach.

Monitor new or changed app support over time.

Integration workflows

Send output to Google Sheets for RevOps review.

Load output into BigQuery or Snowflake for ecosystem analytics.

Join app names with CRM account lists.

Compare app slugs against internal integration roadmaps.

Feed component names into product documentation audits.

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/pipedream-apps-directory-scraper').call({
  searchQuery: 'crm',
  maxItems: 100,
  includeDetails: true
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/pipedream-apps-directory-scraper').call(run_input={
    'searchQuery': 'crm',
    'maxItems': 100,
    'includeDetails': True,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~pipedream-apps-directory-scraper/runs?token=MY-APIFY-TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"searchQuery":"crm","maxItems":100,"includeDetails":true}'

MCP integration

Use this actor from Claude Desktop or Claude Code through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/pipedream-apps-directory-scraper

Claude Code quick add command:

claude mcp add apify-pipedream-apps --transport http \
  https://mcp.apify.com/?tools=automation-lab/pipedream-apps-directory-scraper

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-pipedream-apps": {
      "url": "https://mcp.apify.com/?tools=automation-lab/pipedream-apps-directory-scraper"
    }
  }
}

Example prompt:

"Scrape 100 Pipedream CRM apps and summarize which apps have the most available actions."

Another prompt:

"Compare these SaaS vendors against Pipedream app coverage and flag missing integrations."

Data quality notes

The actor uses Pipedream's public GraphQL responses.

Fields may be null when Pipedream does not expose that metadata.

Component lists are capped by maxComponentsPerApp to keep rows manageable.

The source can change without notice because it is a public website and API used by that website.

Performance notes

Directory-only runs are fastest.

Detail runs perform one extra public GraphQL request per app.

For large exports, increase maxItems gradually.

The actor is HTTP/API based and does not need a browser.

Troubleshooting

If you get fewer rows than expected, remove the search query and increase maxItems.

If specific URLs return no rows, check that the app slug exists in the public directory.

If component arrays are short, increase maxComponentsPerApp.

If a website/API docs URL is null, Pipedream did not expose it for that app.

Legality: is scraping Pipedream legal?

This actor collects public directory metadata.

You should use the data responsibly.

Respect Pipedream's terms, privacy rules, and applicable laws.

Do not use output for spam or abusive automation.

Related scrapers

Explore related automation and directory actors from Automation Lab:

• https://apify.com/automation-lab/zapier-app-directory-scraper
• https://apify.com/automation-lab/n8n-nodes-directory-scraper
• https://apify.com/automation-lab/website-contact-finder

FAQ

Does this require a Pipedream login?

No. The actor targets public directory and public app detail metadata.

Can it scrape all Pipedream apps?

Yes, set a high maxItems and leave searchQuery empty.

Can it monitor changes?

Yes. Schedule recurring runs and compare datasets by appId, slug, and component arrays.

Does it scrape private workflow data?

No. It only extracts public app directory metadata.

Can I filter by category?

Use searchQuery for category-like terms. Category-specific filtering can be added later if Pipedream exposes a stable public category parameter.

Changelog

Initial version extracts public Pipedream app directory rows with detail enrichment.