master-zapier-plan-draft/research/zapier/docs/contacts-all-summary.md
George Lambert b4150c8250 Milestone 0: import zappier billing, Verae middleware, and Zapier research
Compose-ready workspace: packages/zappier (rate card, portal, Stripe),
packages/verae-zapier-middleware (timestamp + NATS), packages/verae-zapier
(CLI app), vendor/zapier-platform, and research/zapier vendor corpus.

Gate 0 structure checks pass. Product code and research are not yet wired.
2026-09-09 02:37:36 -04:00

3.7 KiB

CONTACTS-ALL.md — what was collected

Source file: CONTACTS-ALL.md (index + coverage + top 50)
Machine copies: contacts-all.csv, contacts-all.json (9,985 rows)
Snapshot: 17 August 2026, Zapier public catalog (API v4 + app-page scrape)

This is the full public Zapier directory, not the 15-vertical brief. Every row has at least name + Zapier listing URL.

Why it exists

Outreach and partnership work needed a single table of every public Zapier app: who they are, how to reach them, and how large they are on Zapier. The 15-vertical subset (CONTACTS.md) is richer on HQ and legal name; this file is breadth.

Coverage (9,985 apps)

Field Count Share
Apps in catalog 9,985 100%
Website 9,917 99%
Phone or email or sales form 7,075 71%
Email 4,063 41%
Phone 3,064 31%
Sales / contact URL 5,243 53%
Support URL 246 2%
LinkedIn 248 2%
HQ address 215 2%
Legal name filled (often empty string) treat HQ/legal as curated-only
In the 15 Vendors.txt verticals 256 3%
Premium flag 84 1%
Beta flag 364 4%
Published Zap usage greater than 0 9,319 93%
Sum of published Zap usage 4,017,170

Contact source: site scrape 9,729 · curated deep-research 256.

What each row contains

name, slug, zapier_url, website, phone, email, all_emails, sales_form, support, linkedin, hq_address, legal_name, categories, description, zap_usage, popularity_rank, is_premium, is_beta, in_vendors_txt_verticals, contact_source, scrape_error.

Auth method is not on the public directory page (see CAPABILITIES.md / help scrape for the ~1,971 apps that state auth).

Largest apps by published Zap usage (excerpt)

Built-in Zapier helpers dominate the top (Filter, Webhooks, Formatter, Schedule, Paths, Code, Email, Delay, AI, Looping, Tables). Largest third-party names include Google Sheets, Gmail, Slack, Google Calendar, Drive, HubSpot, Forms, Notion, Facebook Lead Ads, Mailchimp, Stripe, Outlook, Calendly, Typeform, Airtable, Trello, Salesforce, ChatGPT, Jotform, monday.com, Shopify.

These are directory Zap counts, not revenue and not unique customers.

Top Zapier directory categories (an app can have several)

n Category
1,089 CRM
504 Marketing Automation
350 Forms and Surveys
348 Sales and CRM
331 eCommerce
330 Marketing
314 Phone and SMS
289 Project Management
274 AI Assistants
270 Scheduling and Booking
269 Developer Tools
244 Communication
236 Productivity
230 Accounting
186 HR Talent and Recruitment
172 Documents

How to use it

  • Spreadsheet work: open contacts-all.csv.
  • Filter to the 15 verticals: in_vendors_txt_verticals true, or use CONTACTS.md.
  • Outreach: prefer sales_form when email/phone are blank. That is the normal SaaS path.
  • Do not treat scrape phones as gospel (JS sites and footers produce noise). Confirm on the vendor site before calling.

Limits

  • ~952 rows recorded a scrape error; they still have catalog identity.
  • Many sites are JS-only or form-only — 29% have no phone, email, or form URL.
  • HQ / LinkedIn / support URLs were not scraped for the long tail; those fields are almost all from the 256 curated companies.
  • Personal employee inboxes were omitted on purpose.
  • Deeper 15-vertical directory: CONTACTS.md
  • USP / fit / “record they create”: VENDOR-RESEARCH.md
  • Triggers / actions / calling convention: CAPABILITIES.md
  • Mongo: zapier.apps on NS1 (same catalog)