Apollo.io

An Apollo.io integration connects an Apollo API key to Mobius. Assistants can use it to search and enrich people and organizations and to work with accounts and contacts already saved in Apollo.

Use Apollo.io when an assistant needs sales or account research before creating a ticket, updating a CRM, or drafting something for human review.

Capability map

Connect Apollo.io

The Account manager choice controls who manages the saved key in Mobius. Choose You for a personal key or Your team for a company key that organization administrators should maintain. The key's Apollo workspace, plan, and quota still determine what calls can return.

Under Assistant access, grant this exact Apollo connection to the assistants that need it and choose its Mobius result audience. If you connect more than one key, set the intended connection in Account preferences or save it on the routine. Mobius does not ask the model to choose among interchangeable API keys for each call.

Actions

Apollo holds two separate populations of records, and each action reads exactly one of them. People and organizations are Apollo's global prospecting database. You search it to find companies and people you do not yet know, and these calls spend Apollo credits. Accounts and contacts are the records already saved in your own Apollo workspace, and those calls are free.

Prospecting, against Apollo's database:

apollo.person.search
apollo.person.enrich
apollo.organization.search
apollo.organization.enrich
apollo.organization.bulk_enrich
apollo.job_posting.list
apollo.news_article.search

Your Apollo workspace:

apollo.account.search
apollo.account.get
apollo.account.create
apollo.account.update
apollo.account.update_owner
apollo.account_stage.list
apollo.contact.search
apollo.contact.create
apollo.contact.update
apollo.contact_stage.list
apollo.list.search

Search before enrichment when the assistant starts from partial account or contact data. Enrichment calls usually spend provider quota, so grant them only to assistants that need them.

apollo.person.search identifies matches but withholds contact data: last names come back partially masked and emails and phone numbers appear only as availability flags. Pass a match to apollo.person.enrich to resolve the contact details.

Use apollo.organization.bulk_enrich instead of repeated apollo.organization.enrich calls when working through a list; it takes up to ten domains per call.

apollo.job_posting.list and apollo.news_article.search are timing signals for account research: open roles and funding or hiring news for a company you have already identified. Both take an Apollo organization ID and spend a credit per page.

Searching your own workspace first is usually cheaper than enriching. A turn that calls apollo.contact.search before apollo.person.enrich skips paying for people you already know.

Writing back to Apollo

apollo.account.create, apollo.contact.create, and the matching update actions save assistant research into the customer's Apollo workspace so it is visible to the humans working there.

Apollo applies no deduplication when creating an account, so a repeated call creates a second account. Search first, or update the existing record. Contact creation is safer: set run_dedupe and Apollo updates a matching contact in place instead.

Creating or updating Apollo accounts and contacts runs without an automatic Mobius confirmation after the selected key and grant pass their live checks. Search, enrichment, get, and list actions can also spend Apollo credits, so use the narrowest action set and provider quota that fit the job.

The stage and list actions exist to resolve names into IDs. Apollo expects an account_stage_id or contact_stage_id, not a stage name, so call apollo.account_stage.list or apollo.contact_stage.list first and match on the display name.

Events

Apollo.io does not register source events. Start the work another way, such as a message to the assistant or a routine, then call Apollo actions from that turn.

Next

• Review API-key management in Connect accounts.
• Grant research actions to an assistant from actions.
• Store result sets in tables.