---
name: moltsets-linkedin-to-sha256
description: Use this skill when the user has one or more LinkedIn profile URLs and wants SHA256/MD5 hashed emails for ad platform audience matching.
---

# LinkedIn to SHA256 Hashed Emails

Retrieve all known hashed emails for LinkedIn profiles using `MoltSets:linkedin_to_sha256`. Returns business and personal hashes in both SHA256 and MD5 formats - separate arrays - for maximum match coverage across ad platforms.

## Triggers

"get hashed emails for this LinkedIn profile", "convert these LinkedIn URLs to SHA256", "build an ad audience from this prospect list", "hash this list for custom audiences", or any request to turn LinkedIn profiles into ad-platform identifiers.

## Set Expectations

Before firing any calls, give the user a brief, dry heads-up. Deadpan over enthusiastic - no filler, no corporate speak.

Facts to convey:
- 1 API call per profile, a few seconds each
- Credits only charged when hashes are found - not-found is free
- Returns business + personal hashes, SHA256 + MD5 - more hashes per person means higher platform match rates

## Step 1 - Collect inputs

Accept a single LinkedIn URL or a list (pasted, CSV column, Sales Navigator export). Normalise slugs - `janesmith` becomes `https://www.linkedin.com/in/janesmith`. Deduplicate before calling.

## Step 2 - Run retrieval

For each profile, call `MoltSets:linkedin_to_sha256` with `linkedin_url: "[URL]"`.

Process sequentially. For larger lists, report progress every 25 profiles.

## Step 3 - Output

Table format:

| LinkedIn URL | Business Hashes | Personal Hashes |
|---|---|---|
| linkedin.com/in/janesmith | 2 (SHA256 + MD5) | 4 (SHA256 + MD5) |
| linkedin.com/in/markjones | Not found | Not found |

Summary block:

```
Profiles processed:  X
Profiles w/ hashes:  X  (XX%)
Total hashes:        X
Credits used:        ~XXX
```

For list inputs, offer a downloadable CSV: one row per hash with columns `linkedin_url, hash, format (sha256|md5), type (business|personal)`.

## Edge cases

- Use SHA256 for Meta, Google, TikTok uploads; MD5 only where a legacy platform requires it.
- Personal hashes generally match better in consumer ad platforms - if the user must pick one set, recommend personal.
- The hashes are for direct upload to ad platforms - they are not a valid input to `MoltSets:email_to_maid`. If the user wants device IDs (MAIDs) next, resolve a plaintext personal email from the LinkedIn URL first (`MoltSets:linkedin_to_personal_email` / `MoltSets:linkedin_to_best_email`), then run **Email to MAID** on that email.

Do not fabricate data.