Apollo data, on your key, with a paper trail.
Search Apollo's people database from inside PEMAX, enrich only the people you pick, and import them with their source, a phone in E.164 and a lawful basis per address. Your key, your credits, and a monthly budget that is checked before anything is spent.
Apollo is a data source only: PEMAX never uses Apollo sequences, never sends through Apollo and never writes back.
Budget checked before every enrich · phones normalised to E.164 · duplicates merged
How it works
From a search to a prospect you may contact.
Four steps, each with one job. Nothing reaches your prospects table without a source, an owner and an honest answer to the question: may we email this person?
- 01
Connect your key
A workspace admin enters your Apollo key once. The worker checks it, seals it with your workspace's own encryption key and never shows it again. - 02
Search for free
People search runs on Apollo's search endpoint, which returns no contact data and costs no credits. Five pages per search by default, up to fifty. - 03
Enrich who you pick
Select people, choose email, mobile or both, and see the credit estimate first. The budget is checked when you ask and again before a credit is spent. - 04
Import with provenance
Each person becomes a prospect owned by you, with the Apollo id, the time of acquisition, a phone in E.164 and the lawful basis you recorded, if any.
Your key
Sealed the minute it arrives, never shown again.
- The pending row expires after 15 minutes, sealed or not.
- Editors can see that Apollo is connected, never the key.
- One key for the workspace, or a key per market.
- Only the worker can decrypt it, and every use is audited.
- 1Entered
Joost Hendriks · admin · 10:42
Held as a pending row for at most 15 minutes. The web app cannot read it back.
- 2Verified and sealed
PEMAX worker · 10:43
Checked with one call to Apollo, then encrypted with this workspace's own key.
- 3In use
Search and enrich jobs
Never shown again. Replace it or disconnect it from this card.
Apollo credits · this UTC month
1,240 of 2,000 workspace budget
Checked when someone asks to enrich and again on the worker before a credit is spent. Credits belong to one Apollo account, so use counts across the workspace. A market budget never exceeds the workspace budget.
Credit budget
A monthly budget that is checked twice.
- Checked when someone asks to enrich, and again on the worker before spending.
- A market admin can set a market budget, never above the workspace budget.
- Credits per market are shown to the admins who may read spend.
- The month is a UTC calendar month; the card says when it resets.
How a credit is checked
- 1RequestThe estimate for the selected people is compared with what is left this month, at the market's budget.
- 2WorkerBefore calling Apollo, the worker checks the budget again, next to the workspace's spend cap.
- 3MeterThe credits Apollo reports are written to the workspace's usage, so the next check sees them.
Estimates are estimates
Apollo decides what an enrichment costs. PEMAX estimates about one credit per email and eight more per mobile number, and always meters the number Apollo reports.Lawful basis
Ready to call. Blocked for email until there is a ground.
- Choose a ground at import only when you hold its evidence; it is shape-checked first.
- Call-only cadences need no ground and can start right away.
- Consent given on a call is recorded in two clicks and allows email to that person.
What to fetch
Lawful basis for email · Tw 11.7
Apollo is a source, not a ground. They land ready to call; email stays blocked until a ground with evidence is recorded per person.
Pick a ground only when you hold its evidence. It is shape-checked before anything is spent.
After import
What you get
Data you can stand behind.
The details that decide whether enrichment saves your reps time or creates a cleanup job.
Search costs nothing
Filter by job title, seniority, company size, industry, location and company domain. Results show whether an email or phone exists before you pay for either.Pay only for who you pick
Nothing is enriched until you select it. The estimate (about one credit per email, eight more per mobile) is shown before you confirm; PEMAX meters what Apollo reports.Phones in E.164
Numbers are normalised with your market as the region. A number that cannot be made valid E.164 is refused, never stored as given, so the dialer only sees numbers it can dial.Duplicates merge, owners stay
Dedupe runs on email, then the Apollo id, then the LinkedIn URL. A duplicate keeps its existing owner and its existing lawful basis.Erased stays erased
Someone you erased under the GDPR is skipped on every later import, from Apollo or a CSV, and counted as erased in the result.Searches are personal
With own-scope reps, a search and its results are visible to the person who ran it and to admins, not to the rest of the team.CSV import, same rules
Bring a CSV with one ground for the whole file, a ground and evidence per row, or explicitly none. A row needs an email or a phone; phones are normalised the same way.Callbacks routed safely
Apollo delivers phones later by callback. Each job gets its own random token, so PEMAX knows the workspace before it reads a byte, and the token retires when the job is done.Export your searches
Searches, results with their provenance and enrichment jobs are exportable. The prospects export carries owner, lawful basis and the Apollo acquisition time.
Details
What PEMAX keeps for each imported person.
Every field has a reason to exist. Erasure clears the personal ones; the suppression entry stays, so nobody contacts that person again by accident.
| Field | What it holds |
|---|---|
| Source and Apollo idsource, external_ref | Always “apollo” and the person's Apollo id. Used for provenance and as the second dedupe key. |
| Acquired atapollo_acquired_at | When the person came from Apollo. It travels with every prospects export. |
| Ownerowner_user_id | The person who ran the import. Never taken over when the prospect already existed. |
| Phonephone (E.164) | Normalised with the market as region, or left empty. Mobile numbers arrive later by callback and are never attached to someone who unsubscribed, bounced or was archived. |
| Lawful basisground, evidence, source, recorded at, recorded by | Empty unless you chose a ground with its evidence at import. While empty, email stays blocked for that person; calling does not need it. |
| Provider recordprovider_payload | The raw Apollo answer, kept for provenance. Not part of any export, and cleared when the person is erased. |
| Search resultprospect_search_results | Name, title, company facts and whether an email or phone exists, plus a marker when the person is already a prospect. Visible to the searcher and admins. |
FAQ
Questions we get
Do I need my own Apollo account?
Does searching cost credits?
Can I email people I imported from Apollo straight away?
What happens when we reach the budget?
Does PEMAX send through Apollo or sync back to it?
Can PEMAX search companies instead of people?
One workspace
Works with the rest of PEMAX
Bring your Apollo key. Keep your records straight.
We show search, enrich and import on a real workspace, including what happens to a person without a lawful basis, and answer the questions your DPO will ask.
Invite-only workspaces · Hosted in the EU · Bring your own keys