---
template: "marketing.peb"
title: "Apollo.io Prospector Agent"
displayName: "Apollo.io Prospector Agent"
description: "Build net-new Account and Contact prospect lists from Apollo.io, dedupe against Salesforce, and write only approved records."
category: "agents"
contentType: "details"
audience: "end-user"
tags: "agents,gallery,sales,apollo,prospecting,lead-generation,crm-data"
section: "agents"
seoTitle: "Apollo.io Prospector Agent"
seoDescription: "Build net-new Account and Contact prospect lists from Apollo.io, dedupe against Salesforce, enrich selected candidates, and write approved records back to CRM."
seoImage: "https://www.idialogue.app/assets/img/agents/apollo_prospector_hero.png"
---

## Apollo.io Prospector Agent

Build net-new Account and Contact prospect lists from inside Salesforce with a governed workflow for Apollo.io search, Salesforce deduplication, candidate review, enrichment, and approved CRM writeback.

Apollo.io Prospector Agent is net-new discovery first. It is designed for sales teams, revenue operations, SDR managers, and Salesforce admins who need repeatable account and contact list building without creating duplicate or weak CRM records.

Use [Apollo.io CRM Enrichment](/agents/apollo-crm-enrichment.html) instead when the Lead, Contact, or Account already exists in Salesforce and the job is to improve current CRM data.

![Apollo.io Prospector Agent for governed prospecting inside Salesforce](/assets/img/agents/apollo_prospector_hero.png)

## Why teams use this agent

- Turn prospecting objectives into focused Apollo.io People Search or Organization Search filters.
- Resolve technology filters safely with Apollo-supported technology identifiers before searching.
- Dedupe candidate companies and people against existing Salesforce Accounts, Leads, and Contacts.
- Review candidates, field mappings, and proposed operations before records are created or updated.
- Keep Apollo usage and Salesforce writeback approval-based for demos, pilots, and production workflows.
- Move larger prospecting jobs into background execution after an approved plan is defined.

## What it handles

- Account prospecting for company targets, named account lists, territories, and technology-based company searches.
- Contact prospecting for buyers, champions, executives, or people at target accounts.
- Plan-only prospecting when users want a reviewed search strategy without calling Apollo.io.
- Apollo technology lookup for filters such as companies using a named product, platform, or vendor.
- Salesforce duplicate checks using domains, websites, names, email addresses, LinkedIn URLs, and mapped Apollo identifiers when available.
- Enrichment for selected people or organizations before approved Salesforce writeback.

## Inputs and prerequisites

- The iDialogue managed package installed in Salesforce.
- An active [Apollo.io connection](/connections/apollo.html) enabled for the Salesforce org.
- Permission to search and enrich Apollo.io records under your organization's Apollo account policy.
- Permission to read Salesforce Accounts, Leads, Contacts, and any custom fields used for dedupe or mapping.
- Permission to create or update only the Salesforce records and fields your team approves for prospecting writeback.
- Internal guidance for whether new people should become Leads, Contacts, or recommendation-only candidates.

## Setup and configuration

1. Install Apollo.io Prospector Agent from the [Agent Gallery](../agent-gallery/index.html).
2. Configure or reconnect the [Apollo.io connection](/connections/apollo.html) for the Salesforce org.
3. Assign access to sales operations, SDR, and admin users who manage prospecting workflows.
4. Confirm which Account, Lead, and Contact fields are approved for prospecting dedupe and writeback.
5. Map any custom Apollo identifier fields that should be used for stronger duplicate detection.
6. Test with small page sizes before allowing broader territory or technology-based searches.

## Recommended operating model

Use the agent as a guided **Plan, Search, Review, Enrich, Approve, Execute** workflow.

The agent first confirms whether the user wants Account Prospector, Contact Prospector, or Plan Only mode. It then collects filters, resolves technology names when needed, describes relevant Salesforce objects, and summarizes the plan before any Apollo search runs.

![Apollo.io Prospector Agent workflow for search, dedupe, enrichment, and approved Salesforce writeback](/assets/img/agents/apollo_prospector_agent.png)

For small demos and interactive prospecting, start with low page sizes and review candidates in chat. For larger jobs, approve the plan interactively, then use background execution so the agent can continue the work while preserving the same approval rules.

## Governance and controls

- Require plan approval before Apollo.io People Search or Organization Search.
- Resolve ambiguous technology names before using technology-based search filters.
- Dedupe against Salesforce before proposing new Accounts, Leads, or Contacts.
- Enrich selected candidates before final writeback when full person or organization details are needed.
- Require explicit approval for the exact records, target objects, operations, and mapped fields before Salesforce DML.
- Do not overwrite high-quality user-curated CRM values with weaker, stale, blank, or conflicting Apollo values.

## Success metrics

- More targeted account and contact lists created from Salesforce.
- Fewer duplicate Leads, Contacts, and Accounts created during prospecting.
- Higher confidence in prospecting writeback because candidates and mappings are reviewed before DML.
- Better use of Apollo.io credits by planning search and enrichment before execution.
- Reduced manual list-building time for sales and revenue operations teams.

## Next steps

- Review the [Apollo.io Connection](/connections/apollo.html) guide before enabling prospecting workflows.
- Switch to [Apollo.io CRM Enrichment](/agents/apollo-crm-enrichment.html) when existing Salesforce records need ongoing enrichment instead of net-new discovery.
- Use [Data Context Builder](/agents/data-context-builder.html) when the agent needs richer Account, Lead, or Contact context for dedupe and mapping decisions.