/v1/actions/linkedin-extract-event-attendees/run/liveExtract LinkedIn Event Attendees pulls the full guest list from any LinkedIn event page into a structured payload you can pipe into your CRM, sequencer, or data warehouse. You point it at an event URL and get back every registered attendee as clean rows — name, headline, profile URL, and connection degree.
The action runs on the LinkedIn level and is built for teams who treat events as demand signals rather than one-off touchpoints.
You pass the LinkedIn event URL or ID, Edges authenticates with your connected LinkedIn session, and it paginates through the attendee tabs until the list is exhausted. The run executes on Edges infrastructure with safe rate pacing, so you do not need to manage cookies, headless browsers, or retries.
Results stream back as JSON. For large events you can run the action async and collect the result once the pagination completes; smaller events resolve in a single synchronous call.
Use this action whenever a LinkedIn event is a proxy for buying intent — webinars, product launches, industry conferences, or partner roundtables. The attendee list is a high-signal audience that tends to convert better than cold lists, and it maps cleanly into the LinkedIn search API use case.
Most teams run it the morning of the event to capture late registrants, then again the day after to catch walk-ins and replay viewers.
Edges paginates the full list. For public events that means tens of thousands of rows per run. Very large events should be run async so the job is not bound to a single HTTP connection.
It uses the LinkedIn account you connected to Edges. The extraction is executed through your authenticated session, which means visibility matches what you can see in the browser on LinkedIn.
Yes. A common pattern is Extract LinkedIn Event Attendees into Extract LinkedIn Event for event metadata, then into Message LinkedIn Profile for a contextual first touch.
Run Extract LinkedIn Event Attendees from the Edges library, call it from the Edges API, or wire it into your n8n, Make, or Zapier flow. Browse the full Actions library to see what you can chain before and after the extraction.
curl -X POST "https://api.edges.run/v1/actions/linkedin-extract-event-attendees/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"linkedin_event_url": "https://www.linkedin.com/in/example-profile",
"custom_data": "example_value"
}
}'[
{
"company_name": "Example Name",
"linkedin_event_url": "https://www.linkedin.com/in/example-profile",
"first_name": "John",
"full_name": "John Doe",
"linkedin_profile_handle": "example-123",
"sales_navigator_profile_id": "example-123",
"linkedin_profile_id": 42,
"job_title": "Software Engineer at Example Corp",
"last_name": "Doe",
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"headline": "Software Engineer at Example Corp",
"location": "example_value",
"profile_image_url": "https://www.linkedin.com/in/example-profile",
"connection_degree": "example_value",
"current_title": "Software Engineer at Example Corp",
"shared_connection_search_url": "https://www.linkedin.com/in/example-profile",
"number_shared_connections": 42,
"shared_connection_profile_urls": [
"item1",
"item2",
"item3"
]
}
]