Apollo is your sequencer and your enrichment source. Luminik orchestrates on top.
Bring your own plan.
OAuth or API key. Enrichment runs on your Apollo credit pool. Ranked attendees enroll into sequences your team already wrote. Your Apollo plan does the work; Luminik orchestrates.
How the Apollo integration works
Four steps that run on your existing Apollo account. No duplicate seat. No repackaged data deal.
Connect via OAuth or API key
Apollo Professional and Organization seats can connect via OAuth. Team accounts that prefer an API key can paste one in. Either way, Luminik reads your saved lists and sequences so the push flow shows targets where your reps already look.
OAuth scopes or x-api-key header Ranked targets, your existing sequences
After ICP scoring, ranked attendees enroll into the Apollo sequence you nominate: the one your team already wrote, tested, and runs. Event-specific angles get added as step variables. Luminik does not create a parallel sequence.
POST /v1/emailer_campaigns/:id/add_contact_ids Lists for browse, sequences for run
Each event's ICP-matched contacts also land as a named Apollo saved list so reps can browse before sequences kick off. Booth scan context, voice notes, and AI summaries land on the Apollo contact notes so the SDR sees them in the sidebar.
Saved list per event + contact note sync Bring your own Apollo plan
Luminik uses your Apollo seat and your credit pool. We don't resell Apollo data. We don't mark up the line item. If you're already paying Apollo Professional or Organization, that's the plan that runs the work.
No Luminik-side Apollo seat required Your Apollo seat runs the work. Luminik routes the traffic.
Your credit pool pays for enrichment. Your sequences send the outreach. Luminik runs the event pipeline on top: ranking, routing, and attribution. If you already have Apollo Professional or Organization, you already have the plan that runs this.
What writes where
Default routing below. Change any row during setup.
| Luminik field | Apollo surface |
|---|---|
| ICP-matched attendees | Saved list (named per event) |
| Ranked top-tier targets | Sequence (your chosen emailer_campaign) |
| Event-specific messaging tokens | Sequence step variables {{event_name}}, {{booth_no}} |
| Booth scan + voice note summary | Contact note (typed Luminik-capture) |
| AI-extracted next step | Contact custom field + note |
| Meeting booked | Task on contact, paused sequence step |
We ran 15 events across 4 continents in a single half. Every ICP-matched attendee landed in our Apollo sequences with event-specific angles. 270+ qualified meetings. Reps never opened a second tool.
Apollo-specific questions
Do we need OAuth, or is API key fine?
Both paths ship. OAuth works on Apollo Professional and Organization seats. API key works on any paid plan, including Team. OAuth gets us the cleaner scope model and easier reconnect. API key gets you going in 30 seconds if OAuth isn't available on your plan.
What about sequence step limits and bounce handling?
Luminik adds contacts to the sequence. Apollo runs the cadence. Bounce suppression, reply detection, and step limits are Apollo's domain and Luminik respects them, we don't re-add a contact Apollo has parked.
How does list hygiene work across many events?
Each event gets its own named saved list, prefixed with the event code, so the reps' Apollo sidebar stays navigable. Luminik deduplicates against contacts already in an active sequence, so an attendee in flight from a prior event doesn't get double-enrolled.
Can we route different ICP segments to different sequences?
Yes. During setup you nominate a default sequence, then optional per-segment overrides. A CISO-tier attendee can go to an executive sequence; a SOC analyst can go to the technical track. All on your existing Apollo campaigns, not Luminik-built ones.
See Apollo routing on your next event.
20 minutes. Bring an upcoming event and the Apollo sequence your reps are already running. We scope the ICP filter and confirm the tier that fits.