Match an Apollo contact from Claude Code

Human guide: work with your agent → 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. A workspace owner or admin must connect your Apollo credentials through Integrations. Apollo is customer-credential-only in Deepline. Do not assume managed fallback.

1. Inspect access and the operation

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 explains supported behavior.

2. Run one match without requesting phone reveal

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

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.

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 and CSV-safe pilots. 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.

​Before you start

​1. Inspect access and the operation

​2. Run one match without requesting phone reveal

​3. Review the actual response

​4. Build a file workflow only after review

Before you start

1. Inspect access and the operation

2. Run one match without requesting phone reveal

3. Review the actual response

4. Build a file workflow only after review