# FullEnrich Event Attendees > Canonical: https://www.yalc.ai/skills/fullenrich-event-attendees/ A LinkedIn event has 200 qualified attendees. You have access to zero of them. 9 minutes later, here is the SDR ready CSV. ## Categories - prospecting - enrichment **Repo:** https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system **Skill Dir:** .claude/skills/fullenrich-event-attendees **Booker Url:** https://app.iclosed.io/e/acquisition-and-consulting-llp/yalc-implementation-call **Github Skill Url:** https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/fullenrich-event-attendees **Hook:** I used to skip LinkedIn events because attendees were a black box. **Before State:** A relevant event has 200 qualified prospects. You have access to none of them. The attendee list is gated behind a "register to view" wall and even then the export does not exist. **After State:** One command turns any attendee list into an SDR ready CSV with verified work emails and mobile phones, run from your terminal in 9 minutes. ## Gates - **Bring your attendees** - N: 1 - Body: Two ways in. Drop a CSV from PhantomBuster, Evaboot, Sales Navigator, or manual paste. Or run a BYO Apify actor against a LinkedIn event URL with your own LinkedIn cookies. Both paths converge on the same enrichment pipeline. - Tools: PhantomBuster,Evaboot,Apify - **Map any header** - N: 2 - Body: The script reads PhantomBuster, Evaboot, Sales Navigator, and Apify exports out of the box. Pulls first name, last name, LinkedIn URL, company, and title from whichever column shape your source uses. - Tools: - **Estimate cost upfront** - N: 3 - Body: Before any API call the script prints estimated credits, current balance, and remaining balance after the run. No silent burns. - Tools: FullEnrich - **Hard approval gate** - N: 4 - Body: The script blocks on stdin and refuses to spend a single credit until you literally type "yes". Pass --max-credits 100 to cap the spend ceiling. Pass --dry-run to skip enrichment entirely. - Tools: - **Bulk enqueue** - N: 5 - Body: Contacts are batched into 100 per FullEnrich bulk request. Each batch returns an enrichment_id within seconds. - Tools: FullEnrich - **Webhook callback** - N: 6 - Body: FullEnrich runs the 20 vendor waterfall asynchronously and POSTs the result back within 30 seconds per batch. Webhook payload includes cost in credits so spend is auditable. - Tools: FullEnrich - **SDR ready CSV** - N: 7 - Body: One flat CSV with first_name, last_name, linkedin_url, email, email_status, phone, company_domain. email_status is DELIVERABLE, RISKY, INVALID, or UNKNOWN per FullEnrich triple verification. - Tools: **Result Stat:** 200 attendees in. ~140 verified emails out. ~600 credits. 9 minutes from URL to CSV. ## Closer Open source. Bring your own attendees. Bring your own FullEnrich account. Built in partnership with FullEnrich. ## Glance - License: MIT (Yalc) - Input modes: CSV file or BYO Apify actor - Provider: FullEnrich v2 (20 vendor waterfall) **Clone Command:** gh repo clone Othmane-Khadri/YALC-the-GTM-operating-system && cd YALC-the-GTM-operating-system/.claude/skills/fullenrich-event-attendees && cp .env.example .env **Yalc Fit Score:** 9 **Yalc Verdict:** Turns LinkedIn events into a usable lead source for the first time. The CSV input mode means anyone can use it without scraper drama. FullEnrich does the verification waterfall so the output is ready for outreach, not a list of guesses. ## Plain Description The FullEnrich Event Attendees skill takes a list of LinkedIn event attendees and turns it into an SDR ready CSV with verified work emails and mobile phones. Attendees come from a CSV file you drop in (PhantomBuster, Evaboot, Sales Navigator, or manual paste from the LinkedIn event page) or from a BYO Apify actor you configure with your own LinkedIn cookies. Once the contact list lands, the skill estimates the credit cost, blocks on a hard approval prompt, then runs the contacts through FullEnrich v2 bulk enrichment with webhook callback delivery. Output is a flat CSV with email status from the FullEnrich triple verification waterfall. Built in partnership with FullEnrich for the Yalc x FullEnrich skill family. ## Yalc Framework **Workflow Step:** source ### Workflow Narrative The FullEnrich Event Attendees skill sits at the **source** node of the Yalc workflow. Most operators ignore LinkedIn events as a lead source because the export does not exist and the attendee list is gated. This skill collapses that gap into a single command. The hard approval gate before any FullEnrich API call is the safety story. You always know exactly how much you are about to spend, and the script will not spend a single credit until you type "yes" or pass --yes. **Workflow Position:** First step in any event driven outbound campaign. Output flows downstream into qualify-leads (if you want ICP scoring) or directly into unipile-campaign or email-sequence for outreach. ### Trigger Phrases - enrich this LinkedIn event - enrich attendees of this event - enrich this attendees CSV - scrape and enrich LinkedIn event - FullEnrich event attendees - turn LinkedIn event into SDR list ### Required Inputs - Either a CSV of attendees (any common header shape) or a LinkedIn event URL plus a BYO Apify actor with cookies - FULLENRICH_API_KEY from https://app.fullenrich.com/app/api ### Outputs - Flat CSV with first_name, last_name, linkedin_url, email, email_status, phone, company_domain - Per row email_status from FullEnrich triple verification (DELIVERABLE, RISKY, INVALID, UNKNOWN) - Auditable cost report (credits spent per batch via the webhook payload) ### Chaining **Upstream:** PhantomBuster, Evaboot, Sales Navigator, or BYO Apify actor with LinkedIn cookies **Downstream:** Qualified rows can flow into qualify-leads or directly into unipile-campaign or email-sequence ### Anti Patterns - Do not skip the --dry-run preview on first run. The cost preview tells you exactly what is about to happen. - Do not run without a --max-credits ceiling on lists you have not verified. Bad CSVs with 5,000 rows are how accidents happen. - Do not paste LinkedIn cookies into a public repo or shared chat. They authenticate the entire account. ## Dependencies ### Mcps - FullEnrich MCP (optional, for interactive enrichment via Claude) ### Env - FULLENRICH_API_KEY (always) - APIFY_TOKEN (Apify mode only) - LINKEDIN_LI_AT, LINKEDIN_JSESSIONID, LINKEDIN_USER_AGENT (Apify mode only) **Notes:** The skill runs the FullEnrich v2 API directly so it works without the FullEnrich MCP. The MCP is a bonus path for ad hoc enrichment from inside Claude Code. ## Pros - Two input modes cover every realistic source (BYO CSV or BYO Apify) - Hard approval gate makes credit spend explicit, never silent - Header mapping is tolerant of PhantomBuster, Evaboot, Sales Navigator, and manual paste - Webhook based delivery, not polling, so 200 contacts come back in 30 seconds not 5 minutes - --max-credits ceiling auto trims the list, --dry-run shows the preview without spending ## Cons - Apify mode needs you to extract LinkedIn cookies once. They rotate every few weeks. - FullEnrich credits cost real money. A 200 attendee event runs about 600 credits. - The skill does not write outreach copy. Pair with personalize-message after. ## Who For - GTM operators running event driven outbound (you find a relevant LinkedIn event, you want the attendees in pipeline by end of day) - Founders pre and post launch who want to mine industry events without paying for Sales Navigator - Agencies running multi client outbound who need a repeatable event to outreach pipeline ## Related ### Skill **Rule:** Sister skill for LinkedIn post engagers. Same pipeline, different source. **Url:** /skills/linkedin-content-engagers/ ## Alternatives - **Manual outreach with LinkedIn DMs** - Rule: Skip the skill if your event has under 30 attendees and DMing each one is faster than the CSV round trip. - Url: # - **Clay.com workflow** - Rule: Switch if you want a visual no code waterfall instead of a single command. - Url: https://clay.com ## Faq - Q: Why two input modes instead of one? - A: LinkedIn does not expose event attendees through any clean API and Unipile does not cover events. So we ship both paths and let the user pick. CSV mode is the easier path. Apify mode is the URL to CSV path if you have set up an Apify actor with cookies. - Q: Which Apify actor should I use? - A: We do not pin a specific actor. Pick one in the Apify Store like giovannibiancia/linkedin-events-partecipants-scraper. Different actors have different input shapes; pass --actor-input '{"...":"..."}' if needed. - Q: How much do FullEnrich credits cost? - A: Refer to your FullEnrich plan. As a rule of thumb, 1 credit per work email lookup, 2 per phone. A 200 attendee event with both fields runs about 600 credits. - Q: What happens if I run out of credits mid run? - A: The script reads your balance before any API call and the --max-credits ceiling auto trims the contact list to fit. Even without it, you can pass --max-credits N to set a hard cap. - Q: Can I trust the email_status values? - A: FullEnrich runs every email through a 20 vendor waterfall plus triple verification. DELIVERABLE means it deliverable today. UNKNOWN means the verification was inconclusive. Use DELIVERABLE only for cold outreach. **Reviewer:** Othmane Khadri