# Figma Community · Plugin Author Emails (`corent1robert/figma-community-plugin-authors`) Actor

Export unique Figma Community plugin authors for design-tool outreach. Public support email, Community profile and plugin portfolio — one author per row, not per plugin. Keyword, plugin URL, or popular catalog. No login. No API key.

- **URL**: https://apify.com/corent1robert/figma-community-plugin-authors.md
- **Developed by:** [Corentin Robert](https://apify.com/corent1robert) (community)
- **Categories:** Lead generation, Developer tools, Business
- **Stats:** 3 total users, 2 monthly users, 85.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 unique plugin authors

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Figma Community · Unique Plugin Authors

Build an **outreach file** from the public [Figma Community plugin directory](https://www.figma.com/community/plugins). **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](https://apify.com/corent1robert/figma-community-plugin-authors/examples/figma-icon-plugin-authors-emails) | Unique authors in the icon niche, public inbox |
| [Export Figma chart-plugin authors for CRM](https://apify.com/corent1robert/figma-community-plugin-authors/examples/figma-chart-plugin-authors-crm) | Chart / data-viz vendors, one author per row |
| [Refresh author contacts from a plugin URL](https://apify.com/corent1robert/figma-community-plugin-authors/examples/figma-plugin-url-author-refresh) | Paste one Community plugin URL |
| [Popular Figma plugin authors for outreach](https://apify.com/corent1robert/figma-community-plugin-authors/examples/popular-figma-plugin-authors-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](https://blog.apify.com/is-web-scraping-legal/).

### Also available

- **[WordPress.org Plugin Author Contacts](https://apify.com/corent1robert/wordpress-plugin-author-contacts)** — unique plugin authors with public emails
- **[Firefox Add-ons Developer Contacts](https://apify.com/corent1robert/firefox-addons-developer-contacts)** — unique AMO publishers
- **[Chrome Web Store](https://apify.com/corent1robert)** — 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. |

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

### Output example

```json
{
  "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

```bash
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.

# Actor input Schema

## `coverage` (type: `string`):

**Search (default):** use Step 2 (keyword or plugin URL).

**Popular catalog (paid):** walks the public plugin list (most installed) into unique authors. Leave Step 2 empty — it is ignored. Set Max unique authors to how many rows you will pay for. Free Apify plans cannot use Popular catalog.

## `query` (type: `string`):

Examples: `icon` · `chart` · `https://www.figma.com/community/plugin/735643587159282891`

**Ignored** when Mode is Popular catalog.

## `maxAuthors` (type: `integer`):

**Global** cap of unique-author rows (one publisher, many plugins). Default **20** keeps first runs cheap. Search: up to **2,000**. Popular catalog (paid): up to **5,000**.

## `requireEmail` (type: `string`):

**Yes (default):** skip authors with no public support inbox on their plugins. **No:** also keep authors with only a Community profile.

## `excludeGmail` (type: `string`):

**No (default):** keep Gmail / Yahoo / Outlook / iCloud / Proton. **Yes:** skip consumer inboxes so the file is closer to company outreach.

## `minInstalls` (type: `integer`):

Keep authors whose **strongest plugin in this run** is at or above this install count. Leave empty: **0** in Search, **100** in Popular catalog.

## Actor input object example

```json
{
  "coverage": "search",
  "query": "icon",
  "maxAuthors": 20,
  "requireEmail": "yes",
  "excludeGmail": "no"
}
```

# Actor output Schema

## `overview` (type: `string`):

Who to contact: outreach email, plugin count, sample listing

## `outreachCrm` (type: `string`):

Inbox, website and Community profile for a first email

## `marketResearch` (type: `string`):

Installs and portfolio size

## `dataset` (type: `string`):

All author rows

## `output` (type: `string`):

Authors scraped, plugins scanned, filters

## `runLog` (type: `string`):

Live progress

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "icon"
};

// Run the Actor and wait for it to finish
const run = await client.actor("corent1robert/figma-community-plugin-authors").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "icon" }

# Run the Actor and wait for it to finish
run = client.actor("corent1robert/figma-community-plugin-authors").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "icon"
}' |
apify call corent1robert/figma-community-plugin-authors --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,corent1robert/figma-community-plugin-authors"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NP5E1CFbkHLulxmSK/builds/gHHFRW0YyOLZh4qe3/openapi.json