10steps·2providers·SQLyou own

Business Emails for an SMB CSV

Find business email candidates for CSV rows using the same bounded lookup and validation as smb-business-email.

Shared June 2026

  1. 1

    Install & authenticate

    $ npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json

  2. 2

    Test out this play on my data

What this workflow does

Find business email candidates for CSV rows using the same bounded lookup and validation as smb-business-email.

Business Emails for an SMB CSV (Deepline play "smb-business-email-batch", version 1). Find business email candidates for CSV rows using the same bounded lookup and validation as smb-business-email. Pipeline: 10 steps, 2 providers, processes input rows as a dataset. Inputs: csv. Outputs: business_name, domain, city, state, country, business_email_result, email, email_source, candidates, candidate_count, truncated, miss_reason, business_email_result.business, business_email_result.email_candidates, business_email_result.validated_candidates.

Inputs you need

Bring these fields

  • csv

Outputs you get

Produced by the run

  • business_email_result
  • email
  • email_source
  • candidates
  • candidate_count
  • truncated
  • miss_reason
  • business_email_result.business
  • business_email_result.email_candidates
  • business_email_result.validated_candidates

How it works

  1. Step 1

    Read input rows

    play entry

  2. Step 2

    Dataset rows

    over business_name, domain, city, state

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 Openmart and Leadmagic 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

Work Email CSV from LinkedIn Profiles

csv, columns → email, email_source, email_validated

Work Email from LinkedIn Profile

linkedin_url → email, email_source, email_validated

Find SMB Owners from Legal Entities

csv, columns → entity_match, matched_entity, owner_candidates

Run or fork with Deepline CLI

Business Emails for an SMB CSV is a Deepline play. Inputs: csv. Outputs: business_email_result, email, email_source, candidates, candidate_count, truncated, miss_reason, business_email_result.business, business_email_result.email_candidates, business_email_result.validated_candidates.

# Inspect the contract

$ deepline plays describe prebuilt/smb-business-email-batch --json

# Copy to an owned scratchpad

$ deepline plays get prebuilt/smb-business-email-batch --source --out smb-business-email-batch-scratchpad.play.ts

# Check before running

$ deepline plays check smb-business-email-batch-scratchpad.play.ts

# Paste into Claude Code, Cursor, or Codex.

$ Use the deepline-gtm skill's plays recipe to turn the Deepline play "Business Emails for an SMB CSV" (https://deepline.com/p/deepline/smb-business-email-batch) into an editable scratchpad play. Inputs: csv. Outputs: business_email_result, email, email_source, candidates, candidate_count, truncated, miss_reason, business_email_result.business, business_email_result.email_candidates, business_email_result.validated_candidates. 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 npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json # inspect the live contract deepline plays describe prebuilt/smb-business-email-batch --json # copy to an owned scratchpad, then rename the play inside the file before first run deepline plays get prebuilt/smb-business-email-batch --source --out smb-business-email-batch-scratchpad.play.ts # edit smb-business-email-batch-scratchpad.play.ts: set an owned play name, add mappings/validation/status/miss_reason/final columns deepline plays check smb-business-email-batch-scratchpad.play.ts # run the scratchpad on your data deepline plays run --file smb-business-email-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/smb-business-email-batch --input '{"csv":"<your-file.csv>"}' --watch Play spec (JSON): https://deepline.com/api/v2/shared-plays/prebuilt-smb-business-email-batch

Version

v1 · Shared June 2026 · Unlisted page