luma-event-campaign

# Luma event campaign (DRAFT) ## When to use You have (or are creating) a Luma event and need a **repeatable campaign system**: guest acquisition → enrichment → messaging → staged outreach → registration hygiene. Not for one-off "write me an invite tweet." ## Non-negotiables - Keep outbound campaigns **paused** until a human approves sends. - Pilot enrich on ≤10 rows before full waterfall. - No invented speaker bios, titles, or company facts. - Templates use placeholders (`{{event_name}}`, `{{city}}`, `{{speaker_1}}`). - Prefer systems language: skills, plays, webhooks, score → approve → door — not "blast the list." ## Inputs | Input | Required | Notes | | --- | --- | --- | | Luma event URL or export CSV | yes | At least name, email, status | | ICP / TAL sheet (domains) | no | Boosts scoring | | Brand voice notes | no | Else use `templates/voice.md` | | Sequencer (Lemlist/Instantly/etc.) | no | Stage paused campaign only | ## Standard flow ### 1. Frame the system Say out loud (or in the run log): 1. Source of truth for guests (Luma) 2. Enrich + score path 3. Messaging artifacts (invite email, LI DM, social) 4. Outreach object (paused) 5. Inbound sync (registration webhook — see `luma-inbound-webhook-enrich`) ### 2. Guest list hygiene 1. Export or API-pull guests. 2. Normalize emails; drop empties; flag duplicates. 3. Map ticket/status: pending / approved / waitlist / checked_in. 4. Write `guests.normalized.csv`. ### 3. Enrich + score (pilot first) 1. Run a **10-...