Apollo.io
Read and write Apollo contacts, accounts, deals and tasks, enrol contacts in sequences, and run credit-metered enrichment.
Keep prospecting data in Apollo aligned with the CRM, and enrich records from Apollo's database where credits allow.
Source actions
16
Destination actions
12
Data types
15
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
account stages
- List account stagesSource
List account stages configured for the team.
accounts
- Create accountDestinationNot retried automatically
Creates an account. Apollo does not deduplicate accounts on create.
- Get accountSource
One account by Apollo ID.
- Search accountsSource
Accounts saved in the team's Apollo account.
- Update accountDestinationDuplicate protected
Updates the mapped account fields.
calls
- Search callsSource
Call records logged in Apollo, optionally within a date range.
contact stages
- List contact stagesSource
List contact stages configured for the team.
contacts
- Create contactDestinationNot retried automatically
Creates a contact. Without deduplication Apollo always creates a new contact.
- Get contactSource
One contact by Apollo ID.
- Search contactsSource
Contacts saved in the team's Apollo account; filter by keywords, stage or list.
- Update contactDestinationDuplicate protected
Updates the mapped contact fields. label_names replaces existing lists.
- Create or match contactDestinationDuplicate protected
Creates a contact, or returns the existing matching contact (run_dedupe).
deal stages
- List deal stagesSource
List deal stages configured for the team.
deals
- Create dealDestinationNot retried automatically
Creates a deal.
- Get dealSource
One deal by Apollo ID.
- List dealsSource
All deals (opportunities) in the team's Apollo account.
- Update dealDestinationDuplicate protected
Updates the mapped deal fields, for example to move its stage.
fields
- List fieldsSource
Standard and custom fields with their Apollo types, for mapping typed_custom_fields.
notes
- List notesSource
Notes for a contact, account or deal.
organizations
- Enrich organizationDestinationNot retried automatically
Returns enriched company data for one domain. Consumes one Apollo credit per organization.
people
- Enrich personDestinationNot retried automatically
Matches one person in Apollo's database and returns enriched profile data. Consumes Apollo credits per match.
- Search Apollo people databaseSource
Searches Apollo's people database by title, location and employer. Does not reveal emails or phone numbers and does not consume credits. Requires a master API key.
sequence contacts
- Add contact to sequenceDestinationNot retried automatically
Enrols one contact in a sequence. Apollo then sends the sequence's emails, so enable this only for explicit enrolment flows.
sequences
- Search sequencesSource
Sequences in the team's Apollo account. Requires a master API key.
tasks
- Create taskDestinationNot retried automatically
Creates a task for a user to act on a contact.
- Search tasksSource
Tasks in the team's Apollo account. Requires a master API key.
- Update taskDestinationDuplicate protected
Updates a scheduled task (owner, contact, type, priority, due date, title or note).
users
- List usersSource
Users in the Apollo team. Requires a master API key.
Authentication
Apollo API key (x-api-key header)
Plans and access
API access depends on the Apollo plan; enrichment consumes plan credits. Some endpoints (people search, users, sequences) need a master API key. API-key requests act as the workspace's longest-standing admin.
Test environment
A free Apollo account can be used to test non-credit endpoints.
Rate limits
Per-endpoint minute, hour and day limits by plan (for example 50/200/600 on free plans); HTTP 429 when exceeded.
Provider events
Apollo does not offer general record-change webhooks for this API. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- people.enrich and organizations.enrich consume Apollo credits; they are billable and never retried automatically.
- people.enrich sends the identifying fields as query parameters, as Apollo documents; phone reveal (which requires a webhook) is not offered.
- Contact search returns at most 50,000 records (100 per page, 500 pages).
- Adding contacts to a sequence enrols one contact per operation; Apollo then sends sequence emails on its own schedule.
- Contact and record creation have no idempotency key except contacts.upsert, which uses Apollo's run_dedupe.
- Apollo has no last-modified filter on contact or account search; sort by updated date instead.