The independent directory for business agents

Field notes · Updated July 2026

CRM & Sales · agent plugin

Apollo

Prospect, enrich, and manage sales sequences from Claude.

OfficialEditor's picksalesprospectingenrichmentsequences

Editorial profile

Apollo's official plugin connects Claude to its hosted sales MCP server for person and company research, enrichment, contact creation, sequence work, and analytics. It is a powerful outbound tool whose write actions deserve explicit review.

Evidence noteThis profile is based on the linked publisher documentation or public source repository checked on 2026-07-23. A directory listing is not a security audit or a guarantee that the current product will fit your client, account, or data policy.

Where Apollo fits

The useful question is not whether this agent plugin can be installed. It is whether its scope matches a named workflow, keeps the authoritative system clear, and gives a reviewer enough evidence to trust the result.

  • ICP and account research
  • Prospect enrichment
  • Assisted sequence operations

Documented capabilities

These are the practical capabilities described by the current public source. Confirm the exact tool surface, account limits, and enabled permissions in the client you plan to use.

  • Search people and companies
  • Enrich and create contact records
  • Enroll, remove, or stop contacts in sequences and inspect sales analytics

Setup outline

Treat setup as a small integration project. Use a dedicated test identity, begin with the narrowest access available, and record who owns upgrades and credential revocation.

  1. Install apollo@claude-plugins-official
  2. Connect through the plugin's MCP flow
  3. Authenticate and select the correct Apollo workspace

What to check before adoption

Product documentation normally shows the happy path. The items below are the constraints or open questions most likely to affect a business rollout.

  • Sequence enrollment creates outbound communication.
  • Preview recipients, monitor credit use, and follow privacy and anti-spam requirements.

Botfinder's take

Apollo has the advantage of first-party provenance: the publisher controls the underlying product and its integration surface. That reduces one layer of ambiguity, but it does not remove the need to test permissions, failure handling, output quality, and the complete data path.

Start with a read or draft workflow where a person can compare the result with the source system. Add mutation only after the team can explain approvals, duplicate protection, partial failures, and recovery without relying on the model to infer whether a write succeeded.

Adjacent tools may solve a different layer of the same job. Check the authority, scope, and approval model.