Install Listful
Add the Chrome extension from the Chrome Web Store. CSV download needs no Listful account.
Listful exports event attendees from an event permalink with a 19-digit event id (or a people-search URL with eventAttending=) to CSV, when this account is attending. Some events still hide the list. Free, no account, no row credits. Ceiling ~1,000. A generic /events/ directory without an id will not recipe.
Webinar and meetup attendees are a time-boxed audience. LinkedIn shows faces; Listful writes the attendee list to CSV when the event id is in the URL — typically up to ~1,000 — so follow-up happens in your tools, not the events UI.
Add the Chrome extension from the Chrome Web Store. CSV download needs no Listful account.
Use a permalink that contains a 19-digit event snowflake, or a people-search URL with eventAttending=. The generic /events/ index will not work.
Attend the event in this account, then run Export when the side panel detects the event id. LinkedIn only returns the list to attendees, and some events still hide it. Expect LinkedIn to stop around ~1,000 attendees.
After a virtual summit, the host opens the event permalink (URL includes a long numeric id) to capture who marked attending.
CSV of attendees for follow-up sequences. A teammate who bookmarked only /events/ gets no mount until they open the specific event.
| Field | Description |
|---|---|
| profile_url | Canonical /in/ URL when LinkedIn provides one. |
| full_name | Display name as returned by LinkedIn. |
| headline | Headline text. May be empty. |
| location | Location string when present. |
| first_name | First token of the card name. |
| last_name | Remainder of the card name. |
| job_title | Title parsed from the headline when LinkedIn uses “at”. |
| current_title | Same as job_title when the card includes a title. |
| company_name | Company parsed from the headline when present. |
| current_company | Same as company_name from the card. |
| linkedin_profile_id | Member id from the search card tracking URN when LinkedIn sends one. |
| sales_navigator_profile_id | Profile id segment from the card entity URN. |
| linkedin_profile_handle | Public /in/ handle from the card URL. |
| connection_degree | Degree badge on the card when present. |
| profile_image_url | Photo URL from the card when present. |
| linkedin_people_post_search_url | Content search scoped to this profile id. |
| shared_connection_search_url | Mutual-connections link when the card includes it. |
| number_shared_connections | Mutual connection count from the card insight. |
| shared_connection_profile_urls | Space-separated mutual profile URLs from the card. |
| linkedin_event_url | Event or attendee-search URL for this export. |
Full unsupported list: what Listful does not export.
Open an event permalink with a 19-digit id, or a people-search URL with eventAttending=, then export.
Yes for CSV — no Listful account, no row credits.
Ceiling 1,000. Attendee search typically stops there.
The directory has no event id. Open the specific event URL with the snowflake.
Yes when you can see the attendee list. Export, then enrich or webhook if you want.
No. It only exports lists visible in your session.
Some events resolve via ugcPost ids — if the export mounts, you are fine; if not, use a URL with the 19-digit event id.
Not through Listful. Export only.
Confirm the id in the URL and that attendees are visible to your account on that event.
No — different URL patterns and ceilings. Groups go to 5,000; events typically stop near 1,000.
No account, no row credits. LinkedIn’s own page caps still apply — see the limits guide.