Apollo MCP integration for AI agents.
Connect AI agents to Apollo through 5 structured actions, including get api usage stats, enrich organization, and enrich person. Review authentication, input…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Apollo integration exposes
The Apollo Agent App exposes 5 provider-backed actions for marketing and data work. Its current contract lets an authorized agent retrieve apollo api usage statistics for the current team and key, enrich an apollo organization by domain, and enrich an apollo person with the first-pass matching inputs. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Apollo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Apollo capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_usage_statsREADRetrieve Apollo API usage statistics for the current team and key.
enrich_organizationREVIEWEnrich an Apollo organization by domain.
INPUTS: domain
enrich_personREVIEWEnrich an Apollo person with the first-pass matching inputs.
INPUTS: id / email / hashedEmail / linkedinUrl / name
search_organizationsREADSearch Apollo organizations with the first-pass organization filters.
INPUTS: page / perPage / organizationIds / organizationName / organizationLocations
search_peopleREADSearch Apollo people with the first-pass prospecting filters.
INPUTS: page / perPage / keywords / personTitles / includeSimilarTitles
INPUT CONTRACTS
Know what the action needs before it runs.
enrich_organization
domainOPTIONAL- The bare company domain used to enrich an Apollo organization.
enrich_person
idOPTIONAL- The Apollo person identifier.
emailOPTIONAL- The person's email address.
hashedEmailOPTIONAL- The hashed email used for Apollo person matching.
linkedinUrlOPTIONAL- The LinkedIn profile URL used for Apollo person matching.
nameOPTIONAL- The full name used for Apollo person matching.
search_organizations
pageOPTIONAL- The 1-based page number to request.
perPageOPTIONAL- The number of records to request per page.
organizationIdsOPTIONAL- Apollo organization IDs used to scope the search.
organizationNameOPTIONAL- The organization name query used for partial company-name matching.
organizationLocationsOPTIONAL- The organization headquarters locations to include in the search.
search_people
pageOPTIONAL- The 1-based page number to request.
perPageOPTIONAL- The number of records to request per page.
keywordsOPTIONAL- The Apollo keywords string used to refine the people search.
personTitlesOPTIONAL- The current job titles to include in the people search.
includeSimilarTitlesOPTIONAL- Whether Apollo should include titles similar to the supplied person titles.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Usage Stats
Retrieve Apollo API usage statistics for the current team and key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_usage_statsVerify with Search Organizations
Search Apollo organizations with the first-pass organization filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
search_organizationsSAFETY BOUNDARY
Operate Apollo with explicit limits
- Authorize Apollo with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Apollo data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Apollo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Apollo task completed successfully.
CONNECTION MODEL
API key
Apollo API key sent with the x-api-key header. Create it in Settings > Integrations > API Keys: https://docs.apollo.io/docs/create-api-key. The first-pass actions require a master API key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Apollo.