Apollo enrichment

Two integration paths

Apollo does not have a native HTTP-enrichment column like Clay. The two practical patterns are:

1. Workflow + webhook: trigger a Workflow on account creation or list addition, call out to CipherCue with the domain, and write the response back to Apollo custom fields via the Apollo API.
2. CSV enrichment loop: export an Apollo list as CSV, enrich each row against CipherCue, re-import to update account fields. Best for one-off backfills of large lists.

Most teams use Clay as the orchestrator and write back into Apollo from Clay. If that's your setup, follow the Clay recipe and configure Clay's Apollo writeback action separately.

Workflow + webhook

1. In Apollo, create a Workflow triggered by Account Created or your list membership trigger.
2. Add an HTTP Request step (or a Zapier/Make hop, depending on plan):

   GET https://ciphercue.com/api/v1/entities/lookup?domain={{account.domain}}
   Authorization: Bearer YOUR_CIPHERCUE_TOKEN

3. Add a follow-up step to Update Account via the Apollo API, mapping JSON paths from the response into Apollo custom fields:
   • entity.facts.kev_matches.length → KEV count (number)
   • entity.facts.kev_matches[0].cve_id → Top KEV CVE (text)
   • entity.facts.dns_compliance.dmarc → DMARC policy (text)
   • entity.facts.tech_stack[?(@.category=='cms')].product → CMS (text)
4. Use If/then branches on the KEV count field to gate sequences. The canonical play: only enroll in the security-vendor sequence if KEV count > 0.

CSV enrichment loop

1. Export an Apollo list as CSV with the domain column.
2. Run a script that walks the CSV, calls GET /api/v1/entities/lookup?domain=… per row, appends the fields you want, and writes a new CSV.
3. Re-import the enriched CSV to Apollo to update the account records.

For lists larger than a few thousand rows, watch the X-Quota-Remaining response header. Paid workspaces have 100,000 calls per month — contact us for higher limits.