← Back to Skills Marketplace
hundevmode

Linkedin Email Phone Apify

by hundevmode · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
309
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install linkedin-email-phone-apify
Description
Enrich LinkedIn profile URLs with mobile phone numbers and work/personal emails using Apify actors, merging results into unified output records.
README (SKILL.md)

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
  1. Run selected actors on the same URL list.
  2. Merge results by normalized LinkedIn URL.
  3. Return summary + merged rows.

Authentication

export APIFY_TOKEN='apify_api_xxx'

or

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

Quick start

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

Toggle branches

Emails only:

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:

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

  • references/input-contract.md
  • references/troubleshooting.md
Usage Guidance
This skill is internally consistent with its purpose: it needs an Apify API token to run two actors and merge results. Before installing, verify the following: 1) The APIFY_TOKEN is legitimate and scoped appropriately (avoid using a highly privileged token in shared environments); 2) Confirm the two hardcoded actor IDs on your Apify account/console to ensure you trust those actors and their provider; 3) The registry metadata mismatch (claims no env vars vs SKILL.md requiring APIFY_TOKEN) should be corrected — assume the skill needs APIFY_TOKEN; 4) Test with a very small set of LinkedIn URLs first and avoid supplying secrets or unrelated files; 5) Consider legal/ToS implications of scraping LinkedIn data and ensure your use complies with applicable rules; 6) If you deploy in automation, monitor runs and be prepared to rotate/revoke the APIFY_TOKEN if anything unexpected occurs.
Capability Analysis
Type: OpenClaw Skill Name: linkedin-email-phone-apify Version: 1.0.0 The skill bundle is benign. The Python script `linkedin_email_phone_pipeline.py` securely handles the `APIFY_TOKEN` from environment variables or command-line arguments and performs input validation. Network calls are strictly limited to `https://api.apify.com` and hardcoded Apify actor IDs (`X95BXRaFOqZ7rzjxM`, `q3wko0Sbx6ZAAB2xf`), preventing arbitrary external connections. There are no `os.system` or `subprocess` calls that could lead to shell injection, no evidence of data exfiltration beyond the stated purpose of contact enrichment, and no attempts at persistence or obfuscation. The `SKILL.md` and `README.md` provide clear, non-malicious instructions for skill usage, with the `README.md` even offering good security advice regarding API tokens.
Capability Assessment
Purpose & Capability
The name/description (LinkedIn enrichment via Apify) match the implementation: the script calls Apify actor endpoints using two hardcoded actor IDs and merges results. However, registry metadata provided at the top of the submission claims no required env vars/credentials while SKILL.md and the script clearly require an APIFY_TOKEN — this mismatch should be resolved.
Instruction Scope
SKILL.md and the included Python script limit actions to: accepting LinkedIn URLs, normalizing them, calling Apify run-sync endpoints for two actor IDs, merging responses, and returning JSON. The instructions do not ask the agent to read unrelated system files, call obscure endpoints, or exfiltrate secrets beyond using the declared APIFY_TOKEN.
Install Mechanism
No install spec — instruction-only skill with a bundled Python script. There are no downloads or archive extraction steps. Risk from installation is low; the script runs in the user's environment and relies on standard library modules only.
Credentials
The script requires a single credential (APIFY_TOKEN), which is appropriate for running Apify actors. The inconsistency: registry metadata earlier listed 'Required env vars: none' and 'Primary credential: none' while SKILL.md and the script declare APIFY_TOKEN as required/primary. Confirm the registry metadata or SKILL.md to avoid surprises.
Persistence & Privilege
The skill does not request permanent 'always' inclusion and does not modify other skills or system-wide agent settings. It runs only when invoked and accepts the token via env var or CLI argument.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install linkedin-email-phone-apify
  3. After installation, invoke the skill by name or use /linkedin-email-phone-apify
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: combined LinkedIn email and phone enrichment skill using actors X95BXRaFOqZ7rzjxM and q3wko0Sbx6ZAAB2xf.
Metadata
Slug linkedin-email-phone-apify
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Linkedin Email Phone Apify?

Enrich LinkedIn profile URLs with mobile phone numbers and work/personal emails using Apify actors, merging results into unified output records. It is an AI Agent Skill for Claude Code / OpenClaw, with 309 downloads so far.

How do I install Linkedin Email Phone Apify?

Run "/install linkedin-email-phone-apify" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Linkedin Email Phone Apify free?

Yes, Linkedin Email Phone Apify is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Linkedin Email Phone Apify support?

Linkedin Email Phone Apify is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Linkedin Email Phone Apify?

It is built and maintained by hundevmode (@hundevmode); the current version is v1.0.0.

💬 Comments