Slack App Directory Scraper
Pricing
Pay per event
Slack App Directory Scraper
Extract Slack Marketplace apps, vendor metadata, categories, pricing labels, support links, policy URLs, permissions, and security signals.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Stas Persiianenko
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Extract public Slack Marketplace apps, categories, vendor pages, pricing signals, support links, policy URLs, permissions, and security metadata from slack.com/marketplace.
Use this actor to monitor the Slack app ecosystem, build SaaS partner lists, enrich integration databases, or track how vendors position their Slack apps over time.
What does Slack App Directory Scraper do?
Slack App Directory Scraper turns public Slack Marketplace pages into structured records.
It can start from the Marketplace home page, category pages, search URLs, or specific app detail pages.
For each app, it saves identifiers, names, descriptions, categories, pricing labels, supported languages, icon URLs, vendor URLs, support URLs, privacy links, terms links, permissions, and security signals when Slack exposes them publicly.
The actor is HTTP-first and does not require a Slack account.
Who is it for?
This actor is built for teams that need repeatable app-store intelligence.
- 🤝 Partnership and BD teams can find vendors that already invest in Slack integrations.
- 📊 Competitive intelligence teams can monitor new or changing Slack ecosystem apps.
- 🧲 Lead generation teams can build prospect lists from Slack Marketplace categories.
- 🧩 Integration marketplace operators can compare category coverage and app positioning.
- 🔐 RevOps and security teams can review public permission and policy signals before outreach.
Why use this actor?
Slack Marketplace pages contain useful vendor signals, but manually browsing categories is slow.
This actor automates that workflow and returns clean JSON rows ready for export to CSV, Excel, Google Sheets, databases, or enrichment pipelines.
It also preserves the source Slack URL and scrape timestamp so you can audit where each record came from.
What Slack data can you extract?
The output focuses on public Marketplace data.
| Field group | Examples |
|---|---|
| App identity | App ID, app name, app slug, Slack Marketplace URL |
| Positioning | Short description, long description, categories, pricing label |
| Vendor links | Website URL, support URL, privacy URL, terms URL |
| App metadata | Supported languages, icon URL, directory approval flags |
| Security signals | Security contact, SSO/SAML flags, pen-test date, vulnerability program |
| Permissions | Public permission text from app detail pages |
How much does it cost to scrape Slack app directory listings?
Slack App Directory Scraper uses pay-per-event pricing.
You pay a small $0.005 run-start fee and a per-record fee for each saved app.
The BRONZE per-app price is $0.000027939, with canonical tier discounts for higher Apify plans.
For low-cost first tests, keep maxItems small, such as 25 or 50 apps.
Input options
The actor accepts flexible source inputs.
startUrls— Slack Marketplace home, category, search, collection, or detail URLs.query— optional Slack Marketplace search phrase.maxItems— maximum number of unique apps to save.enrichDetails— visit each app detail page for deeper metadata.crawlCategories— discover category URLs from the Marketplace home page.requestDelayMs— delay between HTTP requests.
Example input
{"startUrls": [{ "url": "https://slack.com/marketplace" }],"maxItems": 100,"enrichDetails": true,"crawlCategories": true,"requestDelayMs": 250}
Search input example
{"query": "crm","maxItems": 50,"enrichDetails": false}
Use search mode when you care about a theme such as CRM, support, AI assistant, project management, sales, analytics, or security.
Category input example
{"startUrls": [{ "url": "https://slack.com/marketplace/category/At0EFXUU6N-productivity" }],"maxItems": 100,"enrichDetails": true}
Category mode is useful for recurring category monitoring.
App detail input example
{"startUrls": [{ "url": "https://slack.com/marketplace/A8VK125AS-miro" }],"maxItems": 1,"enrichDetails": true}
Detail URLs are useful when you already know which Slack apps you want to audit.
Output example
{"appId": "A8VK125AS","appName": "Miro","appSlug": "A8VK125AS-miro","appUrl": "https://slack.com/marketplace/A8VK125AS-miro","shortDescription": "Visual collaboration platform","developerName": "Miro","categoryNames": ["Design", "Productivity"],"pricingInfo": "free","websiteUrl": "https://miro.com/slack-integration/","supportUrl": "https://miro.com/integrations/slack/","privacyUrl": "https://miro.com/legal/privacy-policy/","detailEnriched": true,"scrapedAt": "2026-06-28T00:00:00.000Z"}
Output fields
The default dataset includes these fields.
appIdappNameappSlugappUrlshortDescriptionlongDescriptiondeveloperNamedeveloperCountrycategoryNamescategorySlugspricingInfosupportedLanguagesiconUrlwebsiteUrlsupportUrlprivacyUrltermsUrlpermissionsCanViewpermissionsCanDosecurityContactlatestPenTestDatesupportsSsosupportsSamlvulnerabilityDisclosureProgramisSlackCertifiedisDirectoryApprovedisDirectoryPublishedisDistributedsourceUrldetailEnrichedscrapedAt
Tips for best results
Start with the Marketplace home page and crawlCategories: true when you want broad coverage.
Use enrichDetails: false when you only need fast listing data.
Use enrichDetails: true when you need vendor URLs, policies, permission text, or security signals.
Set a moderate requestDelayMs for recurring monitoring jobs.
Keep maxItems low for quick tests, then scale once the output matches your workflow.
Common workflows
- Build a list of Slack-integrated SaaS vendors by category.
- Track app descriptions and positioning changes over time.
- Find apps with public support and privacy URLs for partner research.
- Compare categories such as productivity, sales, HR, AI, and security.
- Enrich a CRM with Slack Marketplace app URLs and vendor websites.
Integrations
You can connect the dataset to many downstream tools.
- Export CSV for spreadsheets.
- Send JSON to a data warehouse.
- Trigger Zapier or Make scenarios from completed runs.
- Use Apify webhooks to notify your team when a monitoring run finishes.
- Combine output with company enrichment APIs for lead scoring.
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/slack-app-directory-scraper').call({startUrls: [{ url: 'https://slack.com/marketplace' }],maxItems: 100,enrichDetails: true,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.slice(0, 3));
API usage with Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_APIFY_TOKEN')run = client.actor('automation-lab/slack-app-directory-scraper').call(run_input={'query': 'crm','maxItems': 50,'enrichDetails': False,})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items[:3])
API usage with cURL
curl -X POST "https://api.apify.com/v2/acts/automation-lab~slack-app-directory-scraper/runs?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"startUrls":[{"url":"https://slack.com/marketplace"}],"maxItems":100,"enrichDetails":true}'
MCP usage
Use this actor from Apify MCP tools in Claude Code or Claude Desktop.
MCP server URL:
https://mcp.apify.com/?tools=automation-lab/slack-app-directory-scraper
Claude Code setup:
$claude mcp add apify-slack-directory "https://mcp.apify.com/?tools=automation-lab/slack-app-directory-scraper"
Claude Desktop JSON config:
{"mcpServers": {"apify-slack-directory": {"url": "https://mcp.apify.com/?tools=automation-lab/slack-app-directory-scraper"}}}
Example prompts:
- "Run the Slack App Directory Scraper for CRM apps and summarize the top vendors."
- "Find Slack Marketplace apps in productivity and return vendor websites."
- "Monitor Slack app categories and flag new apps with privacy URLs."
Data freshness
The actor reads the current public Slack Marketplace HTML at run time.
Slack can change app listings, categories, pricing labels, and public security fields.
For monitoring, schedule regular runs and compare new datasets against earlier exports.
Limitations
The actor only uses public pages.
It does not authenticate to Slack.
It does not inspect private workspace installations.
Some public detail pages may not expose every security or vendor field.
Public email addresses are not guaranteed because many vendors publish support portals instead.
Legality
This actor extracts publicly available information from public Slack Marketplace pages.
You should use the data responsibly, respect Slack's terms, avoid excessive request rates, and comply with privacy, marketing, and data protection laws that apply to your use case.
If you plan outreach, verify contact details and honor opt-out requirements.
Troubleshooting
If you receive fewer items than expected, increase maxItems, enable crawlCategories, or provide more category URLs.
If detail fields are empty, make sure enrichDetails is enabled and that the specific Slack app detail page exposes those fields publicly.
If a run is slower than expected, disable detail enrichment for listing-only workflows.
FAQ
Do I need a Slack account?
No. The actor works from public Slack Marketplace pages.
Can it scrape every app in the Marketplace?
It can crawl public category payloads exposed by Slack Marketplace pages. Coverage depends on what Slack returns in server-rendered public HTML.
Can I scrape one app only?
Yes. Provide one Slack app detail URL and set maxItems to 1.
Does it use a browser?
No. It uses HTTP and Cheerio for lower cost and faster runs.
Related scrapers
Automation Lab maintains multiple marketplace and directory intelligence actors.
Explore related actors at https://apify.com/automation-lab/.
Good companion workflows include SaaS directory scraping, app marketplace monitoring, lead enrichment, and website contact discovery.
Support
If you need a custom field, a specific Slack Marketplace category workflow, or an integration with your database, open an issue on the actor page.
Include your input JSON and a short example of the output you expected.
Changelog
- Initial version: Slack Marketplace listing extraction, category discovery, search input, detail enrichment, and structured app output.