How to Use Lusha to Enrich an Event Attendee List

The short answer: export the attendee list with LinkedIn URLs or work emails, save it as a comma-separated UTF-8 file within your plan's row limit, upload it under Tools, CSV enrichment, map the columns, enrich emails first and phones only for your top accounts, then open the result as a table and push it to HubSpot.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

You are not misreading it: Lusha's pricing page lists CSV enrichment as a Pro feature, while its CSV enrichment article gives even the Free plan a 100-row limit per file, then up to 300 rows on Professional, the plan the pricing page calls Pro, 500 on Premium and 10,000 on Scale. Plan around the row limits either way, because they decide how many uploads one event takes. For what Lusha is and costs, see the Lusha glossary entry.

What to have ready:

1. A credit plan for this list. For example, 450 attendees on Pro means two files, because 450 / 300 = 1.5. Emails for all of them use at most 450 credits, inside Pro's 600 a month at $69.90 on the pricing page, checked on 24 October 2026. Phones for 50 top-account attendees add 50 x 5 = 250 and take you to 700, so run them next month or upgrade.
2. The export from your event platform, with identifiers. The matching article ranks the inputs: LinkedIn URL first, then email, then full name plus company domain or name. Add a LinkedIn URL field to the registration form next time; this time, keep every column you have.
3. Admin rights on both sides. The HubSpot integration article requires you to be both a Lusha admin and a HubSpot admin to connect them.
4. A note on what attendees agreed to. People registered with the event, not with Lusha. Enrichment adds data they did not give you, so GDPR Article 14 applies to it: say where the data came from, at the latest in your first message.

Step 1: Save a file Lusha will accept

The file needs at least one of: a LinkedIn profile URL, an email, or a full name with a company name. It must be a real CSV of no more than 20 MB and 10,000 rows, per the CSV enrichment article. Two failures are common in Europe. Excel in many European locales saves with semicolons, which Lusha rejects, and some files carry a byte order mark. Re-save as "CSV UTF-8 (Comma delimited)" from Excel, or download as CSV from Google Sheets, and delete blank columns and trailing empty rows. Then split the file at your plan's row limit.

Step 2: Upload and map the columns

Go to Tools, CSV enrichment, and click + Upload CSV file. Map each column to a Lusha field: a single "Full Name" column maps to First Name plus Last Name, "Company" to Company Name. The more identifying fields you map, the higher the match rate, so map the LinkedIn and email columns even when they are only partly filled.

Step 3: Choose emails, phones or both

Pick what to enrich and click Start Enrichment. The CSV article charges per matched contact at the normal reveal rate: 1 credit for an email, 5 for a phone, up to 6 for both, and nothing for rows Lusha cannot match. For a first pass on a whole event list, emails only is the sensible default.

Step 4: Read the result before downloading

When processing ends, the file shows two numbers: scanned rows and enriched rows, where at least one field was added. Their ratio is your match rate, and the matching article lists the usual reasons it runs low: missing identifiers, stale company names, personal emails in the email column, or people Lusha does not hold. Download the file; unmatched rows come back with their original data and blank enrichment columns.

Step 5: Open it as a table and push it to HubSpot

Click View table to turn the enriched file into a Workspace table. Connect HubSpot under Settings, Integrations, review the default field mapping, then select the rows and click CRM in the toolbar. Tick Skip already exported, choose HubSpot and export. HubSpot takes up to 1,000 records per export job, and only one export runs at a time per user. The export article charges 1 credit per updated export row, with unchanged CRM rows free and reveal costs counted separately.

Step 6: Let Claude prepare the follow-up for the top accounts

Connect Lusha in Claude through its connector directory, which uses OAuth, as the MCP setup guide describes. Then ask for one bounded piece of work: "From the companies in my table of event attendees, take the 20 largest. For each, list recent hiring, headcount or funding signals and the buying committee, and show me the list before exporting anything to HubSpot."

The MCP tools reference shows why the review step is natural here. Lookup and search tools generally charge only for matched results, filter tools are free, and exporting to the CRM is a separate tool, capped at 100 records per HubSpot run, that reports each row it wrote. You read the list, remove anyone who is not a buyer, and only then tell Claude to export. Connecting a CRM through MCP is admin-only.

How to know it worked

Write down the match rate per file and the share of attendees with a usable email after enrichment. Then compare meetings booked per 100 attendees with the last event you followed up without enrichment. If the matched share is low, the fix is usually upstream: a LinkedIn URL field on the registration form.

What Lusha's docs warn about

• Semicolons, byte order marks and blank columns. Each one can stop an upload; the CSV article walks through re-saving the file.
• Files that expire. Enriched CSVs stay in the Enrich tab for 3 months; after that the data lives only in the table created with View table.
• The phone button on the results screen. Rows marked "Potential enrichment" have phone data waiting, and "Enrich X phones" spends credits to reveal it. Placing that button at the moment you see the results is how a 1-credit email list becomes a 6-credit contact list, so decide which tier deserves phones before you click.
• Opt-outs after the event. Opt-out reports arrive at an admin about monthly and list only new opt-outs since the previous report, per the opt-out article, so keep each one and remove those people from HubSpot.

FAQ

What happens to attendees Lusha cannot match?

They stay in the download with your original data and empty enrichment columns, and they cost nothing, per the CSV enrichment article.

Can I enrich the companies only?

Yes. Map company name or domain, and Lusha returns firmographics such as industry, size, revenue and headquarters location for each company row, the same article says.

How many contacts can I send to HubSpot at once?

Up to 1,000 per export job from a table. Larger selections export the first 1,000 and mark the rest Not exported for the next run, per the HubSpot integration article.