Figma Community · Unique Plugin Authors

Build an outreach file from the public Figma Community plugin directory. One row per unique author — not one row per plugin.

Community scrapers dump listings. You want the people who already ship plugins: who to email, which profile they run, whether they scale (installs / plugin count).

Each row is that file, when the publisher lists it:

• Public support inbox from the plugin support field
• Community handle and profile
• Installs and plugin portfolio in this run
• Sample plugin (highest-install listing in the pool)

Empty fields mean the author did not publish that data — not a failed scrape. Two plugins under the same publisher stay one lead. When Figma lists extra publishers on a plugin (team + named co-publisher), each unique Community profile is its own row. The public support inbox is still the plugin’s listed contact — Figma does not publish a separate email per co-author.

No login. No Figma API token. No Community account.

Keyword search stays on that keyword (not the popular ranking). Paste a plugin URL to refresh that listing’s publishers (name, Community handle, profile). The public support inbox is filled only when Figma publishes it on the plugin — a URL-only run can still return profile rows without an email.

Who is this for?

You are…	Typical goal	Suggested setup
Figma plugin / design-tool SaaS	Authors who already monetize or distribute plugins	Search chart or icon, Require public email = Yes
Design-ops / agency	Independent plugin vendors to partner with	Search your niche, Authors — Outreach view
Recruiter / product design	Plugin creators with a public inbox	Popular plugins, then filter authorLocation
Outbound / SDR	CRM-ready inbox + profile	Authors — Outreach, CSV
Market research	Who scales on Community	Paid Popular catalog, raise Max authors

What you get by default: unique author, public email when published, Community profile, install totals, plugin names in this run — only fields already public.

When a field is empty: Figma did not show a support inbox or site on those plugins. Turn Require public email to No if you still want profile-only rows (typical after pasting a single plugin URL).

How to scrape Figma Community plugin authors

1. Open this Actor in Apify Console.
2. Step 1 — Mode: leave Search (a niche) or switch to Popular catalog (unique authors from the public ranking, paid). Catalog ignores keyword.
3. Step 2 — Search (Search mode only): keep icon, or paste https://www.figma.com/community/plugin/735643587159282891.
4. Leave Max unique authors at 20 for a first run, then raise it. Popular catalog: raise toward 5,000.
5. Click Start. Download JSON / CSV / Excel. Use Authors — Outreach for the inbox; Overview for who scales.

In Search mode, a keyword or plugin URL is required. Popular catalog is paid Apify plans only.

Ready-made examples (published tasks)

Example	What you get
Find Figma icon-plugin authors with emails	Unique authors in the icon niche, public inbox
Export Figma chart-plugin authors for CRM	Chart / data-viz vendors, one author per row
Refresh author contacts from a plugin URL	Paste one Community plugin URL
Popular Figma plugin authors for outreach	Ranking walk, outreach view

What data can this Figma plugin author scraper extract?

Field	Why it matters for ICP
authorEmail, emails	Public support inbox to email
authorWebsite, authorDomain, authorProfileUrl, authorHandle	Company site (when inferable) + Community profile
pluginCount, totalInstalls, pluginNames	Who already ships and scales
samplePluginName, samplePluginIcon, listingUrl	Sample listing + logo
authorLocation, sourceQuery, scrapedAt	Geo + run metadata

Not extracted (and not invented): private Figma account emails, guessed inboxes, team-internal handles, widgets/files (this Actor is plugins).

How much does it cost to scrape Figma plugin authors?

This Actor uses pay-per-event pricing. Actor start is $0.00005. You only pay per unique author written to the dataset. You are not charged per plugin. Paid Apify plans get a lower price per author.

Free plan: a run stops at 20 authors. Search: paid plans can raise Max authors up to 2,000. Popular catalog (paid only) goes up to 5,000 unique authors.

	Free	Bronze	Silver	Gold	Platinum	Diamond
Per unique author	$0.002	$0.0018	$0.0016	$0.0014	$0.0012	$0.001
20 authors (Try)	$0.04	$0.04	$0.03	$0.03	$0.02	$0.02
1,000 authors	$2.00	$1.80	$1.60	$1.40	$1.20	$1.00
5,000 authors	$10.00	$9.00	$8.00	$7.00	$6.00	$5.00

Totals include the $0.00005 start. Figma Community scrapers on Apify charge per plugin (~$1–$4 / 1k listings). Here two plugins from the same author are one charge.

Set Max unique authors and, on Apify, a max total charge so a run cannot exceed your budget.

Is it legal to scrape Figma Community?

This Actor only reads data Figma already publishes on Community plugin pages (name, profile, public support contact, install counts). Director-style private data is not available here. Use personal data under GDPR and your own legitimate-interest / consent basis. Do not spam. See Apify’s note on the legality of web scraping.

Also available

• WordPress.org Plugin Author Contacts — unique plugin authors with public emails
• Firefox Add-ons Developer Contacts — unique AMO publishers
• Chrome Web Store — same unique-author recipe on other marketplaces when listed

Input

Field	Type	Default	Notes
coverage	search | catalog	search	Catalog = paid popular ranking
query	string	icon	Keyword or figma.com/community/plugin/{id} URL. Ignored in catalog
maxAuthors	integer	20	Unique-author cap. 1–2000 search, 1–5000 catalog
requireEmail	yes | no	yes	Skip authors with no public support inbox
excludeGmail	no | yes	no	Skip consumer inboxes
minInstalls	integer	empty	0 in Search, 100 in catalog if omitted
proxyConfiguration	object	cloud default	API-only. Cloud uses Apify residential proxy. Plugin URLs also open the listing in a browser when Community challenges bare HTTP.

{
  "coverage": "search",
  "query": "icon",
  "maxAuthors": 20,
  "requireEmail": "yes"
}

Output example

{
  "authorName": "Acme Studio",
  "authorHandle": "acme",
  "authorId": "917906786944138227",
  "authorProfileUrl": "https://www.figma.com/@acme",
  "authorLocation": "Indonesia",
  "authorWebsite": "https://studio.io",
  "authorDomain": "studio.io",
  "authorEmail": "hello@studio.io",
  "emails": ["hello@studio.io"],
  "supportUrl": null,
  "pluginCount": 3,
  "pluginIds": ["735643587159282891"],
  "pluginNames": ["Icon tools"],
  "totalInstalls": 12000,
  "samplePluginName": "Icon tools",
  "sampleInstalls": 8000,
  "listingUrl": "https://www.figma.com/community/plugin/735643587159282891",
  "sourceQuery": "icon",
  "scrapedAt": "2026-08-19T07:00:00.000Z"
}

Local development

npm install
npm test
node scripts/probe-figma-listing.mjs   # optional: listing vs API vs local Chrome
apify run --purge --input-file=./input.json

storage/ is local-only. output.csv is written on local runs. scripts/ is not in the Docker image.

Support

Contact corentin@outreacher.fr if you need a custom scraper or a tailored export.