Sched Conference Scraper — Speakers, Sessions & Sponsors (Bios, Social Links & Leads)

Extract complete data from any Sched conference site — the full speaker roster with bios and personal social links, the entire agenda (times, venues, tracks, descriptions), and the sponsor list with tiers and logos. Every speaker is a ready-to-use B2B lead: name, job title, company, profile, social links, and the sessions they speak at.

No login, no cookies, no browser — fast, reliable extraction that works on any *.sched.com event (KubeCon, MacAdmins, academic and association conferences, summits, and thousands more).

Why this Sched scraper?

Generic "paste-a-URL" crawlers grab a few visible fields and miss the data that actually matters. This actor reads Sched's public speaker, session, and sponsor pages directly and ships the richest dataset in the category — and it merges the speaker roster from both the speaker directory and every session line-up, so you get the most complete list possible.

Data	Generic crawlers	This actor
Speaker name, title, company	partial	✅ ~95–100%
Speaker full bio	❌	✅ ~90%
Speaker personal social links (Twitter/X, LinkedIn, GitHub, website…)	❌	✅ when published
Sessions each speaker is presenting	❌	✅
Speaker role (speaker / moderator)	❌	✅
Full agenda: time, venue, track/type, description	partial	✅
Session → speaker mapping	❌	✅
Sponsors with tier (Platinum/Gold…) + logo	❌	✅
Roster merged from directory + session line-ups	❌	✅
One clean dataset per entity (no empty columns)	❌	✅

Use cases

• Lead generation — conference speakers are senior, in-market decision-makers (founders, VPs, directors). Export them with title, company, and social links and feed your CRM or outreach sequence.
• Sponsorship & exhibitor prospecting — see exactly who sponsors an event and at what tier, then pitch competitors and adjacent vendors.
• Event discovery & aggregation — power agendas, newsletters, and apps with structured session data: titles, times, rooms, tracks, and descriptions.
• Competitive & market research — track who is speaking on which topics, across an entire conference circuit.
• Recruiting — find domain experts by topic, with company and links, straight from the speaker roster.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the Sched Conference Scraper, paste one or more Sched event URLs (e.g. https://kccncna2023.sched.com or just psumac2024.sched.com), and choose what to output (Speakers by default).
3. Click Start and watch results stream into the dataset table.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
    "eventUrls": ["https://kccncna2023.sched.com", "psumac2024.sched.com"],
    "outputType": "speakers",
    "enrichSpeakerProfiles": true
}

• eventUrls — one or more Sched event sites. Full URL or just the subdomain.
• outputType (default speakers) — speakers, sessions, or sponsors give one clean, dense table; all returns everything in one dataset, each row tagged with a type field.
• includeSessions / includeSpeakers / includeSponsors (default true) — which entities to scrape when outputType is all.
• enrichSpeakerProfiles (default true) — open each speaker's profile for their full bio, personal social links, and the sessions they present (one page per speaker).
• enrichSponsorProfiles (default false) — open each sponsor's profile for description and website (one page per sponsor).
• maxSessions / maxSpeakers (default 0 = no limit) — caps per event, handy for quick test runs.
• maxConcurrency (default 6) — parallel page fetches.
• proxyConfiguration — proxy settings (Apify datacenter proxy by default).

Output

By default you get one clean, dense table of speakers — every column applies to every row. Set outputType to sessions or sponsors for those tables, or all to combine everything in one dataset (each row tagged with a type of speaker, session, sponsor, or event).

A speaker record (type: "speaker"):

{
    "type": "speaker",
    "eventUrl": "https://kccncna2023.sched.com",
    "name": "Flynn",
    "company": "Buoyant",
    "position": "Technical Evangelist",
    "role": "speaker",
    "profileUrl": "https://kccncna2023.sched.com/speaker/flynn@buoyant.io",
    "avatarUrl": "https://avatars.sched.co/.../avatar.jpg",
    "bio": "Flynn is a technical evangelist at Buoyant, educating developers about Linkerd…",
    "socialLinks": { "linkedin": "https://www.linkedin.com/in/…", "website": "https://…" },
    "sessions": [
        { "title": "Emissary-Ingress: Self-Service APIs and the Kubernetes Gateway API", "venue": "W196C", "url": "https://kccncna2023.sched.com/event/1R2p0/…" }
    ],
    "sessionCount": 3,
    "scrapedAt": "2026-06-11T12:00:00.000Z"
}

A session record (type: "session") carries title, date, startTime/endTime, timezone, venue, sessionType, description, a speakers array, and any exhibitors. A sponsor record (type: "sponsor") carries name, tier, logoUrl, profileUrl, and optional website/description.

What to expect (field coverage)

Sched is organizer-entered data, so a few fields are populated only when the organizer or speaker filled them in. Verified across multiple conferences, you can typically expect:

Entity	Always present	Usually present	Present when published
Speaker	name, profile URL, role	company ~95%, position ~95%, avatar ~95%, bio ~90%, sessions ~98%	socialLinks ~50–60% (speakers who added them)
Session	title, date, start/end, timezone, venue, type	description ~88%	speakers / exhibitors (sessions that list them)
Sponsor	name, tier, logo, profile URL	—	website, description (with enrichSponsorProfiles)

A blank field means the organizer didn't publish it for that record — not that scraping failed. Nothing is dropped, so you always get the richest dataset available.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it daily/weekly to capture new speakers and sessions as a conference's agenda fills in.
• Webhooks — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/sched-conference-scraper').call({
    eventUrls: ['https://kccncna2023.sched.com'],
    outputType: 'speakers',
    enrichSpeakerProfiles: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} speakers`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new speaker leads straight into your CRM.
• Slack — get notified when a monitored conference adds speakers or sessions.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "list every speaker at this conference with their company and LinkedIn" and let it run the scraper for you.

More scrapers from scrapesage

Build a complete event intelligence & lead-gen stack — scrape the speaker, attendee, and exhibitor side of the events your prospects run:

• Whova Event Scraper — attendees, sessions, speakers, and sponsors from Whova event apps.
• Swapcard Exhibitor Scraper — exhibitor lists, speakers, and contacts from Swapcard-powered events.
• Eventbrite Scraper — events plus organizer leads (ticket prices, emails, socials).
• Airbnb Scraper — listings, prices, and availability.
• Bark Listing Scraper — service-provider leads from Bark.
• Facebook Ad Library Scraper — competitor ad intelligence on Meta & Instagram.
• Google Ads Transparency Scraper — who's advertising what on Google.
• LinkedIn Jobs Scraper — job postings as hiring-intent signals.

Tips

• Pick a single outputType (Speakers/Sessions/Sponsors) for a clean, fully-populated table that's perfect for direct export. Use all when you want everything in one combined dataset (filter on the type field, or use the Speakers / Sessions / Sponsors dataset views).
• Speaker leads: keep enrichSpeakerProfiles on to capture bios and social links — it's the difference between a name and a contactable lead. It adds one fast page per speaker.
• Big conferences: speaker enrichment is one request per speaker, so a 400-speaker event makes ~400 requests. For very large rosters, residential proxies run smoother than datacenter.
• Recurring monitoring: combine Schedules to track a conference as its agenda and speaker list grow in the weeks before the event.

FAQ

How do I scrape a specific conference? Put its Sched address in eventUrls — the full URL or just the subdomain (kccncna2023.sched.com, psumac2024.sched.com). You can pass several at once.

Does it need the Sched API or a key? No. Sched's official API requires an organizer API key; this actor reads the same (and richer) data from the public speaker, session, and sponsor pages — no key or login needed.

Can I export to Google Sheets, CSV, or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

How do I monitor a conference for new speakers/sessions? Create a Schedule (e.g. daily) and optionally add a webhook or Zapier zap to push new records into your CRM as they appear.

Where do speaker social links come from? From each speaker's own Sched profile, where they choose to list their Twitter/X, LinkedIn, GitHub, website, etc. About half of speakers add them — when they don't, the field is simply absent.

A field is empty — why? Some speakers don't publish a bio or socials, some sessions have no description, and some events don't list sponsors. Fields are blank only when the organizer didn't publish that data — never because the scraper skipped it.

Does it include attendees? No. Sched attendee directories are login-gated by organizers, so they aren't publicly available. This actor covers public speakers, sessions, and sponsors.

Is scraping Sched legal? This actor collects publicly available data only. You're responsible for using the data in compliance with applicable laws (e.g. GDPR/CCPA for personal data) and Sched's terms.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.