Brella — attendee & speaker lists for your event

Brella is an event platform used for programmes, networking, and meetings (in-person, hybrid, or virtual). Attendees use the Brella app to show who they are, what they’re looking for, and to book meetings. This Actor is for organizers, marketing, and sales who need that same data in one spreadsheet — one row per person — instead of opening hundreds of profiles by hand.

What you get: a single table you can open in Excel or Google Sheets, filter, and send to your CRM or outreach tools. Export everyone in the networking list or speakers from the agenda, for the Brella event presets listed below. Download from the Dataset tab when the run finishes.

Emails only appear if that person chose to show their email in Brella — otherwise the cell may be empty. Use the data in line with Brella’s rules and privacy law.

Your event isn’t in the list below? Send your event details (name, dates, and what we need to wire the Brella org/event) — we can add a new preset to this Actor so it appears in the dropdown and you can export the same way as ChangeNOW or START Summit. corentin@outreacher.fr

---

Supported events

Pick these in the Actor input (or use the dropdown in the Apify console).

Event	Value to choose	Notes
ChangeNOW	changenow	Current preset for the ChangeNOW edition configured in this Actor
START Summit	startsummit	Current preset for the START Summit edition configured in this Actor

If the conference year changes, presets may be updated in a new Actor version. Running a different Brella event? Share the event info — we’ll create the preset and add it to this list so you don’t have to fork anything; you’ll pick it in the input and run as usual.

---

Why use it

You want…	You get…
A real lead list after the show	Names, companies, titles, interests, and links in columns — ready to work with
Speakers only	A focused list of people on stage (with bio text when Brella shows it)
Less manual work	No exporting contacts one by one from the app
Visibility while it runs	Progress and time remaining in the run view so you know it’s working

---

What you get (dataset fields)

Each item is one object (one row after export). Key fields:

Field	Description
role	attendee or speaker
attendeeId	Brella attendee / speaker record id
userId	Brella user id (attendees; speakers may be empty)
firstName, lastName, fullName	Name fields
email	If visible on profile; often null
companyName, companyTitle	Company and title
companyCountries	Array of region/country strings
imageUrl	Photo URL when available
linkedin, twitter, website	Social / web
persona	e.g. Investor, Startup — Brella taxonomy
jobFunction, industry	Function and industry labels
pitch	Short intro text (attendees) or bio-derived text (speakers)
bio	Speaker bio (speakers mode; when present)
joinedAt	Registration / join timestamp (attendees)
interests	Array of strings (stages, topics, “network about” lines)
profileUrl	Link to the person on Brella (attendees)

The Apify Dataset also offers a simple table view so you can preview before downloading.

Attendees vs speakers: “Attendees” is the full crowd who registered. “Speakers” is the people on the agenda. The exact columns can differ slightly (e.g. more speaker bio on stage mode).

---

How to run

Step 1 — Mode

• Attendees — Export everyone who participated (the full participant list).
• Speakers — Export only speakers (people on the agenda).

Step 2 — Event

Choose ChangeNOW or START Summit — same list as Supported events.

Step 3 — Filters & profile depth (JSON or API only)

The Apify Console form only shows Mode and Event. Filters and “complete profiles” are not on the visual form — set them in the JSON input (switch to JSON in the run dialog) or via the API.

Use the exportOptions array (multiselect values listed below). Empty array [] = quickest export (list data only).

Value	Meaning
require_email, require_website, require_linkedin, require_company, require_photo, require_pitch	Row filters (AND — all selected must match).
complete_profiles	Slower run: extra step per person for best email & photo when Brella shows them.

• Attendees: filters use list-phase data. For maximum email coverage, run without require_email once or filter in Excel afterward.
• Speakers: use company / photo / pitch requirements only — email / website / LinkedIn filters alone are rejected (empty columns for speakers).

Examples

Prefilled test run (Console JSON tab & repo input.json) — ChangeNOW, 5 rows, enriched (complete profiles):

{
  "mode": "attendees",
  "event": "changenow",
  "maxResults": 5,
  "exportOptions": ["complete_profiles"]
}

For a full export with list-only (no per-person detail step), set "exportOptions": [] or "attendeeData": "list". Omit maxResults to load everyone (default is no cap).

ChangeNOW — full list, list-only (fastest)

{
  "mode": "attendees",
  "event": "changenow",
  "exportOptions": []
}

Only people with an email and a company (quick export)

{
  "mode": "attendees",
  "event": "changenow",
  "exportOptions": ["require_email", "require_company"]
}

Legacy JSON still works: attendeeData ("full" / "list") overrides exportOptions; old boolean fields (onlyWithEmail, etc.) still work if present.

{
  "mode": "attendees",
  "event": "changenow",
  "attendeeData": "list"
}

START Summit — speakers

{
  "mode": "speakers",
  "event": "startsummit"
}

Fine-tuning (optional JSON): power users can adjust maxResults, detailConcurrency, and detailBatchDelayMs — see Developers below. List requests always use the API maximum page size (100 rows per page) until all participants are loaded.

Apify “Run options” in the console

The Apify interface always shows timeout, build, and sometimes maximum cost per run — that’s platform UI, not something this Actor can remove. This Actor sets a default timeout of 3600s; you can lower the cap or cost limit in the run dialog if your plan allows it.

---

Speed tips

• Big event + Complete profiles on = longest runs — use filters so fewer people enter that step, or leave Complete profiles off.
• If a run struggles or Brella rate-limits you, turn Complete profiles off first, or ask a developer to tune advanced settings (see Developers).

---

Output & export

• On Apify: Open the finished run → Dataset → Download — pick the format you prefer (Excel-friendly CSV and Excel are the most common for marketing teams).
• Local runs: the Actor can also write output.csv in the project folder for developers.

---

Who it’s for

• Marketing & growth — post-event lead lists, partner reporting, campaign follow-up
• Event teams — participant or speaker exports after the conference
• Sales / BD — outreach prep from persona and interest data
• Analysts — persona and industry mix
• Data / ops — clean tables for your tools and workflows

---

Developers

• Stack: TypeScript, Apify SDK, Node 20 (see Dockerfile).
• Entry: src/main.ts — event presets in EVENT_PRESETS, Brella service URL in code.
• Local: npm install && npm run build — copy input.json to the default key-value store or use npm run run:local if defined in package.json.
• Tests: No network mocks in repo; validate with a small maxResults against a real session.

Performance (technical): List endpoints use a fixed 100 rows per page (Brella max) until all pages are fetched. Full attendee mode issues one detail request per person for richer rows; list-only mode skips that. Default parallel detail concurrency is 120 (cap 300). List paging uses batched parallel fetches. On HTTP 429 from Brella, lower detailConcurrency or set detailBatchDelayMs (e.g. 25–100 ms).

Changelog: see CHANGELOG.md.

---

Legal

Use only when you have legitimate access to the event data in Brella. Respect the platform’s terms and GDPR / local privacy rules; do not use the Actor to bypass access controls.

---

Support

Custom events: Not listed in Supported events? Email what we need for your Brella event — we add it to the Actor’s preset list so extraction stays one click. corentin@outreacher.fr