---
name: moltsets-business-email-to-sha256
description: Use this skill when the user has one or more business email addresses and wants SHA256-hashed personal emails for ad platform custom audiences (Meta, Google, LinkedIn, TikTok).
---

# Business Email to SHA256 Audience

Convert business email addresses into SHA256-hashed personal emails using `MoltSets:business_email_to_sha256`. Output is ready for direct upload to ad platforms that support customer match or custom audience workflows.

## Triggers

"convert this business email to SHA256", "get hashed emails for [email]", "build a custom audience from these business emails", "hash these emails for Meta / Google", or any request to turn business emails 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 email, a few seconds each
- Credits only charged when a match is found - not-found is free
- Output is privacy-safe: hashes only, no plaintext personal emails exposed

## Step 1 - Collect inputs

Accept a single business email or a list (pasted, CSV column, or file). Validate format; skip and report malformed rows. Deduplicate before calling.

## Step 2 - Run conversion

For each email, call `MoltSets:business_email_to_sha256` with `email: "[business email]"`.

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

## Step 3 - Output

Table format:

| Business Email | SHA256 Personal Hashes |
|---|---|
| jane@acmecorp.com | a1b2c3… , d4e5f6… |
| mark@beta.io | Not found |

Summary block:

```
Emails processed:  X
Hashes returned:   X  (XX%)
Credits used:      ~XXX
```

For list inputs, offer the results as a downloadable CSV with one hash per row (the format ad platforms expect).

## Edge cases

- Multiple hashes per email is normal - one person, several personal addresses. Include all.
- If the user asks for plaintext personal emails instead of hashes, point them to `MoltSets:linkedin_to_personal_email` (requires a LinkedIn URL, not an email).
- If the user starts with LinkedIn URLs, use `MoltSets:linkedin_to_sha256` instead - one call returns business + personal hashes in both SHA256 and MD5.
- The SHA256 hashes are for direct upload to ad platforms. If the user wants device IDs (MAIDs) next, that needs a plaintext email - resolve a personal email first (e.g. `MoltSets:linkedin_to_personal_email`), then run **Email to MAID** on it. Hashes are not a valid MAID input.

Do not fabricate data.