Create an event list from the most reliable input you already have: a prepared file, a supported LinkedIn event, or a clearly scoped request to the Scraping Service. Choose the route first, then qualify the people or companies before planning outreach.
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.
| 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.

A good request lets the service assess the source and deliver the right structure without guessing. Describe the result, not only the website.
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.

A Scraping Service request uses scraping credits, which are separate from your regular credits. Creating the request costs 1 scraping credit. Once you have received a file, you can order a new scrape of the same source with Request to re-scrape the list. The confirmation dialog shows the price, 0.5 scraping credits, and how many scraping credits you have left.
| You cancel | Notice |
|---|---|
| The first request for a source | "Scraping request cancelled — 1 scraping credit returned" |
| A re-scrape | "Re-scrape cancelled — 0.5 scraping credits returned" |
| A request that was never charged (for example, an older request from before scraping credits were introduced) | "Request cancelled — nothing was charged for this request, so there is nothing to return" |
| A request we cannot match to a charge | "Request cancelled — we could not match it to a charge, so no credit was returned automatically. Contact support if you were charged." |
Your scraping credit balance updates right away; you do not need to reload the page.

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.

| 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. |
| "The re-scrape could not be requested. Please try again." | A re-scrape is already open for this source, or no file has been delivered yet. Wait for the open request to be delivered, or cancel it first. Nothing was charged. |
Archive a list you no longer work with. An archived list keeps its leads, but it does not run and it is hidden from your list overview. Unarchive it when you want to work with it again.
Columns add your own information to a list's lead table: a note, a number, a link, a checkbox, a random value, or an enrichment such as AI Prompt or Deep Research . When you create a Text or enrichment column, you also choose which leads it is filled for.
Signalist can tell you which companies visit your website and find the right people at each of them. You install a small script on your website once; after that, every identified company can land in a Website visitors lead list.