Connect an Apollo workspace with one API key and sync its CRM records, outreach emails, calls, users, tasks, sequences, and stages without using enrichment credits.
Connect Apollo as a managed warehouse source with one API key. Embrasure reads records already saved in your Apollo workspace. It does not search Apollo's prospect database or call enrichment endpoints, so ingestion does not spend enrichment credits.
You need:
Apollo documents API-key authentication in its API overview.
In Apollo, open Settings → Integrations → API and create an API key for Embrasure warehouse ingestion. Use a dedicated key so it can be rotated or revoked without interrupting another integration.
In Embrasure, open Warehouse → Ingestion. Select Connect warehouse source for the first source, or New sync if the workspace already has ingestion syncs. Choose Apollo, paste the key, and select Connect.
Embrasure checks the Apollo user and workspace identity, then reads one bounded page from each supported resource. The original CRM resources are required. Outreach emails, calls, and users are optional: a permission denial does not prevent connection, and metadata discovery omits those unavailable tables.
Keep the apollo schema selected, sync metadata, choose the tables you need, and start the batch sync. Each source record keeps useful columns for common analysis and the complete provider response in data.
| Table | Contents | How it updates |
|---|---|---|
apollo.contacts | Contacts with names, email, title, account, owner, stage, and timestamps. | Incremental by Apollo's updated timestamp with a five-minute overlap. |
apollo.accounts | Accounts with name, domain, website, industry, owner, stage, employee estimate, and timestamps. | Incremental by Apollo's updated timestamp with a five-minute overlap. |
apollo.opportunities | Opportunities with amount, outcome, account, owner, stage, and close date. | Bounded snapshot rescan. |
apollo.tasks | Tasks with type, status, priority, due time, owner, contact, and account. | Bounded snapshot rescan. |
apollo.sequences | Sequence definitions and status. | Bounded snapshot rescan. |
apollo.outreach_emails | Sequence emails with contact, account, sender, sequence, delivery status, failure reason, and reply class. | Bounded snapshot rescan. |
apollo.calls | Apollo dialer calls with contact, account, user, opportunity, outcome and purpose IDs, direction, status, duration in seconds, and start/end times. | Snapshot rescan. |
apollo.users | Workspace users with names, email, team, title, and deleted flag. Join id to owner/user IDs in other tables. | Snapshot rescan. |
apollo.contact_stages | Contact stage definitions. | Snapshot rescan. |
apollo.account_stages | Account stage definitions. | Snapshot rescan. |
apollo.opportunity_stages | Opportunity stages, pipeline, probability, and outcome flags. | Snapshot rescan. |
The new tables use Apollo's outreach email search, call search, and user list endpoints. All three cost zero API credits. Call search requires a master API key; emails and users require their endpoint access or a master key, subject to Apollo plan and role restrictions. After granting access, refresh source metadata to discover newly available tables.
These tables rescan all pages on each sync so changes to older email delivery outcomes, calls, and user details are captured. They expose current state, not event history. Email engagement fields such as replied and bounce, and any other counters or timestamps returned by Apollo, remain queryable in data. Extra fields, including email content when Apollo supplies it, remain in data; ingestion does not make separate content or recording requests.
Apollo caps contacts, accounts, tasks, and outreach email searches at 50,000 matching records. Embrasure reports that limit instead of silently producing an incomplete table. If email search omits totals, a full page at that boundary also fails because completeness cannot be confirmed.
Regular syncs merge current records and do not detect hard deletes. Use Actions → Full resync to replace destination contents from a complete new scan and remove records that no longer appear in Apollo.
Embrasure stores only the API key in encrypted connector credentials. It sends the key in Apollo's x-api-key header and makes read-only requests. The connector does not create or update Apollo records and does not call prospecting or enrichment APIs.