31steps·9providers·SQLyou own

Mobile Phone CSV from People

Find mobile phone numbers for a CSV of people in one pass.

Shared June 2026

  1. 1

    Install & authenticate

    $ curl -fsSL "https://deepline.com/api/v2/sdk/install" | bash

  2. 2

    Test out this play on my data

What this workflow does

Find mobile phone numbers for a CSV of people in one pass.

Mobile Phone CSV from People (Deepline play "person-to-phone-batch", version 1). Find mobile phone numbers for a CSV of people in one pass. Pipeline: 31 steps, 9 providers, processes input rows as a dataset. Inputs: csv, columns. Outputs: rows.

Inputs you need

Bring these fields

  • csv

Outputs you get

Produced by the run

  • phone_result
  • phone
  • phone_source
  • phone_validated
  • phone_validation_status
  • phone_activity_score
  • phone_activity_band
  • phone_line_type
  • phone_carrier
  • phone_reject_reason
  • phone_result.dropleads_mobile
  • phone_result.forager_reverse_lookup_by_email
  • phone_result.leadmagic_mobile_from_linkedin
  • phone_result.leadmagic_mobile_from_email
  • phone_result.datagma_mobile_from_email
  • phone_result.datagma_mobile_from_linkedin
  • phone_result.wiza_phone
  • phone_result.ai_ark_mobile
  • phone_result.native_phone
  • phone_result.fullenrich_phone
  • phone_result.trestle_validated_phone

How it works

  1. Step 1

    Read input rows

    play entry

  2. Step 2

    Dataset rows

    over upcell_phone

Cost/latency when available

This public page does not show cost or latency yet. Deepline only displays those metrics when the published package has safe, comparable run samples, and cost is always shown in Deepline credits.

Common edits

  • Rename the copied play before the first run so it is owned by your workspace.
  • Map your CSV headers into the expected input fields and add status or miss_reason columns.
  • Keep stable step, fetch, dataset, and play-call ids so retries and durable receipts stay useful.
  • Edit the final projection before scale so the output table matches your CRM or campaign import.

Use it when

  • You need data from Dropleads, Trestle, Forager, Leadmagic, Datagma, Wiza, Ai, Deepline and Fullenrich in one pass.
  • You want a repeatable pipeline instead of one-off lookups.
  • You want an agent or teammate to run the same workflow on demand.

Related workflows

LinkedIn Profile CSV from Personal Emails

csv, columns → rows

Work Email CSV from Names and Domains

csv, columns → rows

Job Change Detection

linkedin_url, contact_linkedin, current_domain → rows

Run or fork with Deepline CLI

Mobile Phone CSV from People is a Deepline play. Inputs: csv. Outputs: phone_result, phone, phone_source, phone_validated, phone_validation_status, phone_activity_score, phone_activity_band, phone_line_type, phone_carrier, phone_reject_reason, phone_result.dropleads_mobile, phone_result.forager_reverse_lookup_by_email, phone_result.leadmagic_mobile_from_linkedin, phone_result.leadmagic_mobile_from_email, phone_result.datagma_mobile_from_email, phone_result.datagma_mobile_from_linkedin, phone_result.wiza_phone, phone_result.ai_ark_mobile, phone_result.native_phone, phone_result.fullenrich_phone, phone_result.trestle_validated_phone.

# Inspect the contract

$ deepline plays describe prebuilt/person-to-phone-batch --json

# Copy to an owned scratchpad

$ deepline plays get prebuilt/person-to-phone-batch --source --out person-to-phone-batch-scratchpad.play.ts

# Check before running

$ deepline plays check person-to-phone-batch-scratchpad.play.ts

# Paste into Claude Code, Cursor, or Codex.

$ Use the deepline-gtm skill's plays recipe to turn the Deepline play "Mobile Phone CSV from People" (https://deepline.com/p/deepline/person-to-phone-batch) into an editable scratchpad play. Inputs: csv. Outputs: phone_result, phone, phone_source, phone_validated, phone_validation_status, phone_activity_score, phone_activity_band, phone_line_type, phone_carrier, phone_reject_reason, phone_result.dropleads_mobile, phone_result.forager_reverse_lookup_by_email, phone_result.leadmagic_mobile_from_linkedin, phone_result.leadmagic_mobile_from_email, phone_result.datagma_mobile_from_email, phone_result.datagma_mobile_from_linkedin, phone_result.wiza_phone, phone_result.ai_ark_mobile, phone_result.native_phone, phone_result.fullenrich_phone, phone_result.trestle_validated_phone. The .play.ts file is the source of truth: copy the play, rename it for this user's workflow, encode input mapping/validation/status/output projection in the play, and iterate there instead of doing one-off CSV post-processing. Keep stable dataset names, dataset row keys, and step/fetch/play-call ids across edits. Provider tool calls reuse paid work by play, tool, semantic input, auth scope, provider action version, and cache policy unless you intentionally change those inputs or refresh stale data. # install Deepline if the CLI is missing curl -fsSL "https://deepline.com/api/v2/sdk/install" | bash # inspect the live contract deepline plays describe prebuilt/person-to-phone-batch --json # copy to an owned scratchpad, then rename the play inside the file before first run deepline plays get prebuilt/person-to-phone-batch --source --out person-to-phone-batch-scratchpad.play.ts # edit person-to-phone-batch-scratchpad.play.ts: set an owned play name, add mappings/validation/status/miss_reason/final columns deepline plays check person-to-phone-batch-scratchpad.play.ts # run the scratchpad on your data deepline plays run --file person-to-phone-batch-scratchpad.play.ts --input '{"csv":"<your-file.csv>"}' --watch # only for an exact one-off with no edits or custom output deepline plays run prebuilt/person-to-phone-batch --input '{"csv":"<your-file.csv>"}' --watch Play spec (JSON): https://deepline.com/api/v2/shared-plays/prebuilt-person-to-phone-batch

Version

v1 · Shared June 2026 · Unlisted page