> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Match an Apollo contact from Claude Code

> Use customer-connected Apollo matching and verify identity before a CSV workflow.

[Human guide: work with your agent →](https://deepline.com/docs/human/guides/apollo-claude-code.md)

Run one Apollo person-match pilot from Claude Code with your connected Apollo
account. Keep the returned identity evidence before any CRM or sequencer update.

## Before you start

[Install Deepline](https://deepline.com/docs/sdk-v2/coding-agents.md). A workspace owner or admin must
connect your Apollo credentials through [Integrations](https://deepline.com/docs/integrations.md).
Apollo is customer-credential-only in Deepline. Do not assume managed fallback.

## 1. Inspect access and the operation

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline describe apollo_people_match --json
```

Read the current identity fields, reveal options, pricing, and connection state.
Preview search and matched-person retrieval are different actions.
The [Apollo guide](https://deepline.com/docs/providers/apollo/guide.md) explains supported behavior.

## 2. Run one match without requesting phone reveal

Use one authorized identity. Replace this fictional sample before execution:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute apollo_people_match \
  --input '{"first_name":"Jane","last_name":"Doe","domain":"example.com"}' \
  --json
```

This can incur provider-account usage. Preserve the returned execution identity
and any next-step commands. A missing match is a possible valid outcome.

Phone reveal has a separate asynchronous contract. Do not assume a completed
person match means phone data is ready.

## 3. Review the actual response

Check the intended person and organization, available fields, and any no-result
or error state. Follow the declared output schema. A response does not guarantee
every email, title, or phone field is populated.

> [!TIP]
>
> Identity evidence supports the intended person and company. Unknown fields
> remain unknown, and the execution outcome is retained for later inspection.

## 4. Build a file workflow only after review

Ask Claude to author a CSV Play from the inspected contract. Preserve source
IDs and keep external writes disabled for the pilot.
Use [Write Plays](https://deepline.com/docs/sdk-v2/plays.md) and
[CSV-safe pilots](https://deepline.com/docs/sdk-v2/batch-csv.md).

Automatic column flattening, acceptance rules, or fallback order must be
implemented explicitly. Do not infer them from a natural-language request.

Your Apollo agreement governs provider usage. Deepline compute or other
applicable charges can remain. Inspect recorded Deepline usage separately.
Ask Claude to explain a mismatch before another paid attempt.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.