Data and research
Apollo.io
An Apollo.io integration connects an Apollo API key to Mobius so loops can search and enrich people and organizations.
Use Apollo.io when a run needs sales or account research before creating a ticket, updating a CRM, or drafting a human review artifact.
Capability map
| Capability | Value |
|---|---|
| Provider ID | apollo |
| Auth kind | api_key |
| Connect flow | Inline API key |
| Actions | Yes |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | No |
Connect Apollo.io
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose Apollo.io, and paste the API key. |
| CLI | The mobius CLI does not connect Apollo.io integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/apollo/connect with the Apollo credential body from the API reference. |
Use a project-owned key when output depends on your Apollo plan, saved filters, or account quota.
Actions
apollo.organizations.enrich
apollo.organizations.search
apollo.people.enrich
apollo.people.searchSearch before enrichment when the run starts from partial account or contact data. Enrichment calls usually spend provider quota, so keep them behind a specific trigger condition.
Events
Apollo.io does not register source events. Start the run from a schedule, HTTP trigger, or another provider event, then call Apollo actions.
Next
- Put research calls in action steps.
- Store result sets in tables.
- Keep provider credentials in integrations.