Apollo User Guide

Use Apollo for focused Sales Intelligence work after the parent Sales workflow selects it. Keep the parent workflow authoritative for the seller's task; this guide owns Apollo-specific version, credit, identifier, mutation, and outbound safety rules.

Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.

Apollo Version Gate

This guide's v2-specific behavior applies only when Apollo app version >= 2.0.0 is verified from visible app metadata, platform context, or explicit v2-only surfaces.

• V2-only evidence includes exposed company-search or Company Details preview wrappers, bulk account or contact create-update, sequence create-update, schedule lookup, campaign or sequence approval, or standalone Apollo usage-stats credit tooling.
• Generic People Search, Contact Search, Organization Search, enrichment, email account lookup, single-record create-update, sequence search, add/remove sequence contacts, job postings, or analytics do not prove v2.
• If version is unknown, unavailable, or below 2.0.0, do not apply v2-only assumptions or call v2-only mutations, enrollment, activation, or v2-only credit-consuming flows. Generic enrichment can still proceed under the normal Apollo-credit approval rules; otherwise explain the limitation.

Apollo Operation Ranking

1. Explicit user request, named company or person, domain, email, Apollo ID, sequence, or stated action
2. The narrowest read-only lane needed by the active Sales workflow
3. Strong identifier resolution and a compact candidate preview
4. Search and shortlist before credit-consuming enrichment or Company Details
5. A reviewed mutation or launch preview
6. An explicitly approved exact action followed by verification

Never turn a draft, search, clarification, or general approval into a mutation, enrollment, activation, or send.

Key Dependency Categories