Create event lists and use the Scraping Service

Event workflows are time-sensitive, but the event date is not a reason to skip data checks, consent and exclusion rules, or sender safeguards. Work backwards from the event and leave time for collection, enrichment, review, and corrections.

Before you start

Record the event name, date, official URL, and organiser.
Confirm whether you need attendees, speakers, sponsors, exhibitors, companies, or a specific combination.
Decide which roles and company profiles are relevant and which must be excluded.
Confirm that you are allowed to use the source and process the resulting data.
Set an owner, a review deadline, and a small initial limit.

Choose the right route

What you have	Recommended route	Important check
A prepared attendee or exhibitor file	Use the relevant XLSX upload for people or companies.	Clean the file, remove duplicates, and confirm that you may process the data.
A supported LinkedIn event URL	Use Find attendees of a specific event where it is available.	Use the exact event URL. LinkedIn availability can change, and not every event may be discoverable.
A public event website or exhibitor directory	Request the Scraping Service if that option is available.	Describe the source and desired output precisely; the service must assess feasibility.
A login-protected portal or mobile event app	Ask whether the Scraping Service can support the source.	Do not paste credentials into free-text fields, comments, or the chatbot. Agree on a secure access method if access is required.
No attendee data, only an event topic	Do not assume a topic-based attendee source exists.	Use the sources currently shown in your workspace or start from another approved data source.

A source being technically accessible does not make every record suitable for outreach. Preserve the source context and separate collection from qualification.

Signalist The verified Create new list view showing the available upload, specific LinkedIn event, and Scraping Service routes.

Prepare a Scraping Service request

A good request lets the service assess the source and deliver the right structure without guessing. Describe the result, not only the website.

Event name and event date
Official source URL and source type, such as website, participant portal, or mobile app
Whether you need people, exhibitor companies, or both
Required fields, such as name, company, role, website, or public profile URL
Target segments and explicit exclusions
Desired delivery timing and the business reason for the deadline

Do not include passwords, access tokens, private invitation links, or personal data in the description. If restricted access is necessary, wait for an approved secure handover method.

Signalist The verified Scraping Service request form with fields for source name, source type, event date, URL, and desired output where available.

Steps

**Collect the event details. **Record the official name, date, URL, organiser, and any approved file or access route.
**Choose upload, LinkedIn event, or Scraping Service. **Use XLSX for a prepared dataset, Find attendees of a specific event for a supported LinkedIn event, or the service request for a source that needs extraction.
**Define the requested output. **State whether you need people, companies, or both, and list only the fields required for qualification.
**Define qualification rules. **Add relevant company characteristics, persona roles, geographic scope, and exclusions before processing a large result.
**Set a small limit or sample. **Where the flow allows it, request or process enough records to evaluate coverage and quality without creating unnecessary work.
**Review Found, Not Found, and data quality. **Check names, companies, roles, domains, profile URLs, duplicates, and exclusion reasons against the source.
**Plan the timing backwards. **Reserve time for enrichment, lead review, message review, sender checks, and corrections before pre-event outreach.
**Choose a suitable next action. **Use the approved segment for pre-event outreach, on-site planning, post-event follow-up, or monitoring according to timing and permissions.

Signalist A verified event list review showing event date, source, Found and Not Found results, and qualification fields where available.

Plan around the event date

Work backwards from the date rather than starting outreach as soon as records arrive. Collection and enrichment can reveal missing or outdated data, and every segment still needs a human quality review.

Before the event: use a relevant, factual reason to connect or arrange a meeting.
During the event: keep messages useful and avoid assumptions about attendance or availability.
After the event: verify attendance context and avoid claiming that a person visited a booth or session unless the source supports it.
At every stage: respect opt-outs, ownership, other-list status, blacklists, and channel-specific sending limits.

Signalist A simple verified list or campaign planning view with the event date and review milestones visible.

Troubleshooting

Problem	Solution
The LinkedIn event cannot be found	Check the exact URL and whether the event is current and accessible. LinkedIn event discovery can be incomplete; use an approved file or request another supported route if needed.
The event page is login-protected	Use the Scraping Service request flow and explain the source and outcome. Never include login credentials in a free-text request.
The result contains many irrelevant roles	Keep the raw event data separate from qualification. Apply persona criteria, company fit, exclusions, and a manual review before outreach.
The Scraping Service request is unclear	Add the event name, date, official URL, source type, required output, relevant fields, and whether you need people, companies, or both.
The event date is too close for safe outreach	Reduce scope or use the list for follow-up instead. Do not bypass enrichment review, message review, or sender limits to meet the date.

Frequently asked questions

Which route should I use if I already have an attendee file?

Use the relevant XLSX upload. Clean and test the file first; requesting another extraction would add unnecessary uncertainty.

Can Signalist find attendees for every LinkedIn event?

No guarantee should be assumed. Use Find attendees of a specific event only when it is available and accepts the event URL in your workspace.

Can the Scraping Service access a login-protected event app?

It may be possible after a feasibility and access review. Submit the source and desired output, but never put credentials into free-text fields or the chatbot.

Should I request people or companies?

Choose the smallest dataset that supports your goal. Request people for role-specific outreach, companies for account planning, or both only when you need the relationship between them.

How far in advance should I start?

Leave enough time for source collection, enrichment, quality review, message review, and sender checks. If the date is too close, reduce scope or plan a post-event workflow.

Can I contact everyone on an event list?

No. Apply company and persona relevance, exclusions, existing relationship and opt-out checks, and a manual review before choosing any outreach action.

Keep reading

Choose the right list source

Choose your list source by starting with what you already have and what you want the list to do next. If you begin with the source name alone, it is easy to pick something too broad, too narrow, or not available in your workspace.

Use LinkedIn list sources safely

LinkedIn activity can help you build timely lists from profile visits, followers, events, posts, engagement, or prepared LinkedIn URLs. Use the source that matches the specific signal, then qualify the people before you treat them as outreach candidates.

Using AI Company Search and News Monitoring

Use AI Company Search to describe target companies in natural language, and use news or signal monitoring to watch for specific events. Both work best when your prompt is verifiable, your exclusions are explicit, and each result has a defined review or follow up action.