Slack App Directory Email Scraper

Slack App Directory Email Scraper — vendor support emails from Slack app listings

The Slack App Directory Email Scraper builds a contact list of the software vendors who publish integrations for Slack. Every app listing is a small storefront, and a storefront needs a support address.

That is what makes this Actor productive: a Slack app listing exists to convince a workspace admin to install something, so the publisher has a strong incentive to print a way of reaching them. In our measured runs the Slack App Directory Email Scraper recovered account identity on 8 out of 10 rows.

The audience the Slack App Directory Email Scraper reaches is unusually well-qualified. A company shipping a Slack integration is a funded, technical, B2B SaaS vendor — exactly the profile most partner, agency and developer-tool teams are trying to reach.

What the Slack App Directory Email Scraper does

The Slack App Directory Email Scraper builds Google searches using the site: operator against slack.com, fetches result pages through the Apify GOOGLE_SERP proxy, and extracts email addresses from the title and snippet text of each result block.

It does not log into Slack, use the Slack API, or open the Slack App Directory in a browser. There is no JavaScript rendering, no authentication and no cookies anywhere in the pipeline.

App listings live under slack.com/apps/<id>, which is a path-based handle. That is why the Slack App Directory Email Scraper can usually attach a username and a working profileUrl to the address it finds.

Why the Slack app ecosystem is a strong prospecting surface

Integration vendors are buyers of everything an app company buys: analytics, billing, support tooling, security review, localisation, design and marketing services.

They are also partners. If you sell into the same workspaces, a publisher found by the Slack App Directory Email Scraper is a natural candidate for co-marketing, a bundle or a technical integration of your own.

The Slack App Directory Email Scraper gives you that list with a publicly published address attached, keyed to the app name and listing you can open and verify.

Key features of the Slack App Directory Email Scraper

Feature	What it means for your Slack app vendor list
Google site: targeting	Queries are scoped to slack.com, focused on app listing pages
Path-based handle parsing	slack.com/apps/<id> yields a username and a matching profileUrl
Vendor-tuned modifiers	Defaults include support, developer and publisher — the words listings actually use
Query expansion	Each keyword × domain pair runs as a base, quoted and intitle: query plus one variant per modifier
Domain filtering	Only emails ending in your customDomains list are kept
Global deduplication	An address appears once per run, across every query and page
Email normalisation	Handles name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and full-width ＠
Junk filter	Rejects email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Discards a hit that is only the tail of another email in the same block
Structural parsing	Finds the <h3> title then the smallest surrounding block; no reliance on Google CSS classes
Whole-page fallback parser	A Google layout change degrades to "emails without account details", not "no emails"
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Retries with backoff	Up to 3 attempts per page, exponential backoff, fresh proxy session per request
Failed-query requeue	Blocked or failed queries are retried once at the end of the run
Async concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Resumable state	Key-value store state keyed by an input hash, saved on PERSIST_STATE, MIGRATING and ABORTING
Run summary	Logs pages fetched, blocked pages, retries and emails per page

How the Slack App Directory Email Scraper works

1. The Slack App Directory Email Scraper reads your keywords, optional location, email domains and limits.
2. It composes queries such as site:slack.com slack app support "@gmail.com".
3. It fetches Google result pages asynchronously through the Apify GOOGLE_SERP proxy with aiohttp.
4. It parses each result block structurally, isolating the listing title and its snippet.
5. It applies a domain-filtered regex, normalises candidates and filters placeholder addresses.
6. It deduplicates globally and pushes each lead to the Apify dataset immediately.

Base queries run first, so the most relevant listings arrive before the expanded long tail. A conservative maxEmails still returns the best of the run.

The Slack App Directory Email Scraper halts as soon as your quota is met, so nothing is spent on pages you will not use.

Input reference for the Slack App Directory Email Scraper

These nine fields are the complete input surface of the Slack App Directory Email Scraper.

Field	Type	Default	Meaning
keywords	array (required)	["slack app", "integration"]	Search terms: app category, vertical, use case
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; @ optional
maxEmails	integer 1–10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE…)
expandQueries	boolean	true	Search each keyword × domain in several phrasings
queryModifiers	array	["email","contact","support","developer","publisher"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1–50	30	Page cap per query
maxConcurrency	integer 1–20	5	Parallel queries

Category-shaped keywords work best here: crm integration, standup bot, incident management, time tracking. They mirror how the directory itself is organised.

Example input for the Slack App Directory Email Scraper

{
  "keywords": ["standup bot", "crm integration", "incident management"],
  "location": "",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 400,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "support", "developer", "publisher"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Point customDomains at corporate suffixes when you specifically want company addresses rather than founder Gmail accounts. Both patterns exist in this directory.

Output reference for the Slack App Directory Email Scraper

Every dataset item the Slack App Directory Email Scraper produces carries all fourteen fields.

Field	Meaning
network	Platform name — Slack App Directory
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (app handle or vendor display name)
fullName	Display name parsed from a profile-style title; empty for plain listing snippets
username	App listing handle when Slack exposes one; otherwise null
profileUrl	Canonical listing URL when a handle is known; otherwise empty
url	Direct Slack link when exposed, else the profile URL
description	Listing snippet, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email
foundAt	ISO 8601 UTC timestamp

Example output row from the Slack App Directory Email Scraper

{
  "network": "Slack App Directory",
  "keyword": "standup bot",
  "query": "site:slack.com standup bot support \"@gmail.com\"",
  "title": "Standuply — Slack App Directory",
  "accountName": "A0F7XDUAZ",
  "fullName": "Standuply",
  "username": "A0F7XDUAZ",
  "profileUrl": "https://slack.com/apps/A0F7XDUAZ",
  "url": "https://slack.com/apps/A0F7XDUAZ",
  "description": "Async standups and team reports for Slack. Support: standuply.support@gmail.com",
  "email": "standuply.support@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T10:41:19Z"
}

The profileUrl shape is https://slack.com/apps/{username}. Open it before any outreach — a two-second manual check keeps a lead list clean.

Use cases for the Slack App Directory Email Scraper

Use case	How the Slack App Directory Email Scraper helps
SaaS partner recruitment	Find integration vendors already building for the same workspaces you sell into
B2B outbound sales	Reach app companies who buy analytics, billing, support and security tooling
Agency prospecting	Identify vendors whose listings need better copy, design or localisation
Competitive research	Map who ships in your category and how they present support
Marketplace benchmarking	Track which vendors publish contact details and which do not
Developer relations	Build an early-access list of teams shipping on a platform
Recruiting	Source engineers and PMs at companies working in your problem space
CRM enrichment	Attach a public support address to vendors already in your pipeline

For neighbouring integration marketplaces, run this alongside the Zapier App Directory Email Scraper, the HubSpot Marketplace Email Scraper or the Atlassian Marketplace Email Scraper — many vendors list on several at once.

Tuning the Slack App Directory Email Scraper

Feed the Slack App Directory Email Scraper category language, not brand names. helpdesk integration finds a whole segment; a single vendor's name finds one listing.

Keep expandQueries on. Google caps a single query at roughly 300 results, and expansion is the mechanism designed around that cap.

Raise maxPagesPerQuery only when a query is genuinely deep. Most directory queries exhaust well before the 30-page default.

Try countryCode when you want vendors positioned for a particular market — Google's regional results differ, and so do the listings the Slack App Directory Email Scraper surfaces.

Honest limitations of the Slack App Directory Email Scraper

• The Slack App Directory Email Scraper only finds listings whose email is publicly visible in Google's index. Vendors who route support through a form instead of an address will not appear.
• Google caps a single query at roughly 300 results, which is why query expansion exists.
• possiblyTruncated: true means Google's snippet ellipsis touched the address. Verify those rows before sending.
• The Slack App Directory Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
• username and profileUrl are only populated when a listing handle appears in Google's result. Where Google prints only a vendor display name, you keep accountName and fullName with an empty handle — a Google limitation, not a bug.
• Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
• Slack App Directory Email Scraper results vary with keywords, domains and location. No volume is guaranteed.

Frequently asked questions about the Slack App Directory Email Scraper

Does the Slack App Directory Email Scraper use the Slack API?

No. The Slack App Directory Email Scraper never logs in, never calls the Slack API and never opens the directory in a browser. All data comes from publicly indexed Google search results.

Where do the emails come from?

The Slack App Directory Email Scraper reads the titles and snippets Google prints for app listing pages on slack.com — most often the support address a vendor publishes on their listing.

Is the Slack App Directory Email Scraper affiliated with Slack?

No. The Slack App Directory Email Scraper is an independent Actor, not supported, endorsed or affiliated with Slack.

Why is username sometimes empty?

The Slack App Directory Email Scraper parses a handle only when Google's result exposes one in the URL path or a profile-style title. Where Google prints only a vendor name, the row keeps accountName and fullName and leaves username as null.

Why does the Slack App Directory Email Scraper recover identity more often than a community scraper?

Because Slack app listings are path-addressed under slack.com/apps/, so the handle usually sits right in the indexed URL and maps cleanly onto username and profileUrl.

How is the Slack App Directory Email Scraper different from the Slack Community Email Scraper?

That Actor targets public invite and community landing pages, where volume is modest because workspaces are private. This one targets vendor app listings, which are public by design and yield more.

How many emails will one Slack App Directory Email Scraper run return?

It depends on your keywords and domains. Free Apify plans stop at 100 emails per run; paid plans are uncapped up to your maxEmails.

What does possiblyTruncated mean?

Google shortens long snippets with an ellipsis. If it touched the address, the Slack App Directory Email Scraper sets the flag to true so you can verify or discard that row.

Can I collect corporate domains instead of Gmail?

Yes. customDomains accepts any domains, with or without the leading @, and only those are kept.

Does a Slack App Directory Email Scraper run survive a migration?

Yes. State lives in the key-value store keyed by a hash of your input, and is saved on PERSIST_STATE, MIGRATING and ABORTING.

What if Google changes its markup?

The Slack App Directory Email Scraper parses structurally, not by CSS class name, and a whole-page fallback parser takes over. Worst case: emails without account details.

Can I export the results?

Yes — the Slack App Directory Email Scraper dataset exports to CSV, JSON, Excel or the Apify API, like any Apify dataset.

Related Actors

Actor	What it collects
Slack App Directory Email and Phone Number Scraper	Emails and phone numbers from Slack App Directory
Slack App Directory Phone Number Scraper	Public phone numbers from Slack App Directory
App Store Email Scraper	Public contact emails from App Store
Atlassian Marketplace Email Scraper	Public contact emails from Atlassian Marketplace
Bitbucket Email Scraper	Public contact emails from Bitbucket
Chrome Web Store Email Scraper	Public contact emails from Chrome Web Store
CodePen Email Scraper	Public contact emails from CodePen
Confluence Email Scraper	Public contact emails from Confluence
Dev.to Email Scraper	Public contact emails from DEV Community
Docker Hub Email Scraper	Public contact emails from Docker Hub
Figma Community Email Scraper	Public contact emails from Figma Community
Firefox Add-ons Email Scraper	Public contact emails from Firefox Add-ons
GitHub Email Scraper	Public contact emails from GitHub
GitLab Email Scraper	Public contact emails from GitLab
Google Play Email Scraper	Public contact emails from Google Play
Hashnode Email Scraper	Public contact emails from Hashnode
HubSpot Marketplace Email Scraper	Public contact emails from HubSpot Marketplace
Hugging Face Email Scraper	Public contact emails from Hugging Face
Jira Email Scraper	Public contact emails from Jira
Maven Central Email Scraper	Public contact emails from Maven Central
Microsoft AppSource Email Scraper	Public contact emails from Microsoft AppSource
Salesforce AppExchange Email Scraper	Public contact emails from Salesforce AppExchange
Shopify App Store Email Scraper	Public contact emails from Shopify App Store
SourceForge Email Scraper	Public contact emails from SourceForge
Stack Overflow Email Scraper	Public contact emails from Stack Overflow
Unity Asset Store Email Scraper	Public contact emails from Unity Asset Store
Unreal Engine Marketplace Email Scraper	Public contact emails from Unreal Engine Marketplace
WordPress Plugin Directory Email Scraper	Public contact emails from WordPress Plugin Directory
WordPress Theme Directory Email Scraper	Public contact emails from WordPress Theme Directory
Zapier App Directory Email Scraper	Public contact emails from Zapier App Directory
App Store Email and Phone Number Scraper	Emails and phone numbers from App Store
Atlassian Marketplace Email and Phone Number Scraper	Emails and phone numbers from Atlassian Marketplace
Bitbucket Email and Phone Number Scraper	Emails and phone numbers from Bitbucket
Chrome Web Store Email and Phone Number Scraper	Emails and phone numbers from Chrome Web Store
CodePen Email and Phone Number Scraper	Emails and phone numbers from CodePen
Confluence Email and Phone Number Scraper	Emails and phone numbers from Confluence
DEV Community Email and Phone Number Scraper	Emails and phone numbers from DEV Community
Docker Hub Email and Phone Number Scraper	Emails and phone numbers from Docker Hub
Figma Community Email and Phone Number Scraper	Emails and phone numbers from Figma Community
Firefox Add-ons Email and Phone Number Scraper	Emails and phone numbers from Firefox Add-ons
GitHub Email and Phone Number Scraper	Emails and phone numbers from GitHub
GitLab Email and Phone Number Scraper	Emails and phone numbers from GitLab

Leave a review

If the Slack App Directory Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions, a bug report, or a custom build of the Slack App Directory Email Scraper? Email neurodata.apify@gmail.com and we will get back to you.