Linkedin Email Phone Apify

# LinkedIn Email + Phone Enrichment (Apify)

## Overview

This skill runs two Apify actors in one pipeline and merges results by LinkedIn profile URL:
- Phone actor: `X95BXRaFOqZ7rzjxM`
- Email actor: `q3wko0Sbx6ZAAB2xf`

Use this when the user wants one command to enrich a LinkedIn URL list with:
- mobile phones
- work emails
- personal emails
- unified rows for n8n/Sheets/CRM

## Step-by-step workflow

1. Accept LinkedIn URLs (`linkedinUrls`) from user.
2. Validate and normalize URLs.
3. Decide branches:
- run phone actor if `includePhones=true`
- run email actor if `includeEmails=true`
4. Run selected actors on the same URL list.
5. Merge results by normalized LinkedIn URL.
6. Return summary + merged rows.

## Authentication

```bash
export APIFY_TOKEN='apify_api_xxx'
```

or

```bash
python3 scripts/linkedin_email_phone_pipeline.py run \
  --apify-token 'apify_api_xxx' \
  --input-file references/sample_input.json
```

## Quick start

```bash
APIFY_TOKEN='apify_api_xxx' \
python3 scripts/linkedin_email_phone_pipeline.py run \
  --input-file references/sample_input.json
```

## Toggle branches

Emails only:

```bash
APIFY_TOKEN='apify_api_xxx' \
python3 scripts/linkedin_email_phone_pipeline.py run \
  --input-json '{
    "linkedinUrls": ["https://www.linkedin.com/in/williamhgates"],
    "includeEmails": true,
    "includePhones": false,
    "includeWorkEmails": true,
    "includePersonalEmails": true,
    "onlyWithEmails": true
  }'
```

Phones only:

```bash
APIFY_TOKEN='apify_api_xxx' \
python3 scripts/linkedin_email_phone_pipeline.py run \
  --input-json '{
    "linkedinUrls": ["https://www.linkedin.com/in/williamhgates"],
    "includeEmails": false,
    "includePhones": true,
    "onlyWithPhones": true
  }'
```

## Notes

- Actor IDs are hardcoded to your provided IDs.
- `linkedinUrls` is required.
- At least one branch must be enabled (`includeEmails` or `includePhones`).
- Output rows contain available email/phone fields in one record.

## References

- `re...

# LinkedIn Email and Phone Finder Skill for OpenClaw (Apify)

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
[![Apify Phone Actor](https://img.shields.io/badge/Phone%20Actor-X95BXRaFOqZ7rzjxM-ff6b00)](https://console.apify.com/actors/X95BXRaFOqZ7rzjxM)
[![Apify Email Actor](https://img.shields.io/badge/Email%20Actor-q3wko0Sbx6ZAAB2xf-ff6b00)](https://console.apify.com/actors/q3wko0Sbx6ZAAB2xf)

This repository contains a production-ready OpenClaw skill for **LinkedIn contact enrichment** using two Apify actors in one pipeline:
- Phone enrichment actor: [X95BXRaFOqZ7rzjxM](https://console.apify.com/actors/X95BXRaFOqZ7rzjxM)
- Email enrichment actor: [q3wko0Sbx6ZAAB2xf](https://console.apify.com/actors/q3wko0Sbx6ZAAB2xf)

It is built for teams that need one workflow to enrich LinkedIn URLs with both **emails and mobile phones**, then return clean merged rows for outbound operations.

## Why this skill

Most lead-gen stacks split email and phone scraping into separate tools. That creates duplicate mapping logic and inconsistent outputs. This skill gives you one run command, optional branch control, and merged contact data keyed by normalized LinkedIn URL.

Use cases:
- LinkedIn lead scraping for agencies and SDR teams
- B2B prospecting list enrichment
- CRM-ready contact data preparation
- n8n automation and Google Sheets pipelines

## Stack

- OpenClaw skill framework
- Apify actors for LinkedIn data lookup
- Python 3.10+ runner (no external dependencies)
- Secure token auth via `APIFY_TOKEN`

## Quick start

### 1) Set token

```bash
export APIFY_TOKEN='apify_api_xxx'
```

### 2) Run combined pipeline

```bash
python3 scripts/linkedin_email_phone_pipeline.py run \
  --input-file references/sample_input.json
```

### 3) Run with inline JSON

```bash
python3 scripts/linkedin_email_phone_pipeline.py run \
  --input-json '{
    "linkedinUrls": [
      "https://www.linkedin.com/in/williamhgates",
      "https://www.linkedin.com/in/jeffwe...