Turn LinkedIn event attendees into ready-to-send email drafts

Build me an agent workflow that turns LinkedIn event attendees into warm, ready-to-send email drafts, every Monday at 8am. The trigger is a weekly cron.

Inputs I will configure once and edit over time:

1) A list of LinkedIn event URLs (webinars, conferences, product launches I hosted or attended). 2) My ICP definition in plain English, defaulting to director-plus titles in my target industries. 3) The Attio object I want people written to (default: People) and the tag pattern to use for the event they attended (default: the event name). 4) The Slack channel that should receive the weekly digest. 5) A short description of my product and the reason it is relevant to my ICP, so the agent can write a specific opener.

Each Monday, the agent should do the following for every event URL in the list:

Step 1 — Pull the attendee list. Use PhantomBuster's Launch Agent with Output (v1) to run the LinkedIn Event Guests Export Phantom against the event URL, then use Fetch Agent Output to retrieve the resulting attendee rows. Handle the case where the Phantom is still running by polling Fetch Agent Output.

Step 2 — Filter to ICP. For each attendee, evaluate their title, seniority, company, and industry against the ICP definition. Drop anyone who is clearly out of profile.

Step 3 — Upsert into Attio. For each qualified attendee, use Attio's Assert a Record (Upsert) on the People object, matching on email (or LinkedIn URL when email is missing), so we never create duplicates. Add the event tag and any relevant attributes (title, company, LinkedIn URL). If the person already exists in Attio with recent activity in the last 30 days, skip them for outreach drafting so we do not spam existing contacts — still tag them with the event.

Step 4 — Draft the email. For each qualified attendee who has an email and is not already in active outreach, use Gmail's Create a Draft to compose a personalized message. The draft must reference the specific event by name, the attendee's role, and a concrete reason our product is relevant to their company. Keep it under 120 words, plain text, first-person, no marketing tone. Leave the draft in Gmail — do not send.

Step 5 — Slack digest. When all events are processed for the week, use the Slack Bot Send a Message action to post a single digest to the configured sales channel. Include: total attendees seen across events, how many were qualified, how many drafts are queued in Gmail, and the top 5 prospects to review first (name, title, company, event, one-line reason they are hot). Add a link back to the Gmail drafts folder.

Guardrails: never send an email automatically — always leave drafts. Never create a duplicate Attio record — always upsert. Skip anyone with recent activity (last 30 days) in Attio. If the LinkedIn Event Guests Export Phantom fails for a specific event, log it in the Slack digest and continue with the other events instead of stopping the whole run.