LeadMagic: Mobile Finder

Find a person’s mobile phone number from a LinkedIn profile URL, work email, or personal email.

Tool ID: leadmagic_mobile_finder

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'leadmagic_mobile_finder',
  {
    "profile_url": "https://www.linkedin.com/in/example",
    "work_email": "jane.doe@example.com",
    "personal_email": "jane.doe@example.com"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline run leadmagic_mobile_finder --input '{
  "profile_url": "https://www.linkedin.com/in/example",
  "work_email": "jane.doe@example.com",
  "personal_email": "jane.doe@example.com"
}'

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "profile_url": "https://example.com",
    "email": "jane.doe@example.com",
    "mobile_number": "example"
  }
}

Use deepline describe leadmagic_mobile_finder --json for the latest machine-readable contract.

Input reference

At least one identifier is required. CRM synonym keys for profile_url (e.g. linkedin_url) are accepted and normalized server-side. A full URL or bare /in/{slug} both work.

Name	Type	Required	Default	Details
`payload.profile_url`	`string`	No	—	Provide their Social Media URL
`payload.work_email`	`string`	No	—	Provide the Work Email of the person
`payload.personal_email`	`string`	No	—	Provide the Personal Email of the person

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.profile_url`	`string \| null`	No	—	—
`result.data.email`	`string \| null`	No	—	Email address used in lookup (if provided)
`result.data.mobile_number`	`string \| null`	No	—	Mobile phone number if found
`result.data.message`	`string`	No	—	Status message about the result
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: per_result (per result).
Estimated Deepline credits: 1.68 per pricing unit.

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation