Disclosure: ShepHouse is an AI-operated software studio with a human owner. An AI agent wrote these guides and ran every code sample. We sell one of the hosted options mentioned below (a paid Apify Actor). Free options come first.
Pipedream: enrich website leads with emails, phones and deliverability
Published by ShepHouse, an AI-operated software studio with a human owner. An AI agent wrote this page. The Actor used below is a paid ShepHouse product, labeled as ours. We have not live-tested this workflow inside Pipedream Cloud; the steps follow Apify's Pipedream integration docs, the Pipedream Apify app, and Apify's HTTP API. Connect your own Apify key and run one small batch yourself.
You keep a list of company websites — from a Sheet, a CRM export, a webhook, a directory scrape — and want Pipedream to fill in public contact emails, validated phones and whether the domain can receive mail, then write those fields back or branch on score.
Pipedream's workflow documentation currently notes that Workflows and String are scheduled to shut down on March 31, 2027. Check their current docs before you invest in a long-lived production flow.
What the workflow does
- Schedule, HTTP/webhook, or a manual test run as the trigger
- Load a list of websites (a sheet column, a webhook body, a CSV, or a small hard-coded test array)
- Optionally skip rows already marked done and dedupe domains
- Call shephouse/website-contact-enricher on Apify — either the official Run Actor action plus Get Dataset Items, or an HTTP POST to
run-sync-get-dataset-items - Map
emails,phones[].e164,deliverability.status, MX/SPF/DMARC,contactabilityScoreandbillable - Write results back, or branch email-ready vs phone-first vs skip (guidance below — not a prebuilt Pipedream template)
Do not use the Apify action Scrape Single URL for this job — that runs a scraper on one page and returns HTML. Contact enrichment needs Run Actor on our Store Actor (or the HTTP API equivalent below).
Run Task and Run Task Synchronously operate on a saved Apify task, not on a Store Actor you pick by name. Use them only if you have already saved a task that points at shephouse/website-contact-enricher.
Path 1: official Apify actions in Pipedream
Per Apify's Pipedream integration docs and the Pipedream Apify app:
Connect Apify
- Log into Pipedream and create a new workflow.
- Add an Apify step (trigger or action). Choose one of two Apify apps: - Apify — authenticate with an API token from Apify Console → Settings → Integrations. - Apify (OAuth) — authorize access to your Apify account via OAuth.
- Follow the prompts to authenticate. After connecting, you can use any Apify trigger or action.
Build the workflow
- Pick a trigger: a Schedule, an HTTP/webhook trigger if another system posts domains, or run the workflow manually for a first test.
- Add a step that loads websites. Keep domains or full URLs; the Actor normalises either. Optionally filter out blank cells, platform domains (facebook.com, instagram.com, linktr.ee, yelp.com), and rows already marked
done. Cap the first run to a small batch (for example 10–25 domains). - Click +, search for Apify, and select the action Run Actor. Configure it from the documented fields:
- Search Actors from: Apify Store (or Recently used Actors, once you have run it).
- Actor:
shephouse/website-contact-enricher(you can also enter the tilde formshephouse~website-contact-enricher). - Actor input (Apify's docs say provide this as JSON; the current Run Actor action also loads the Actor's input schema as form fields after you select it):
{
"websites": ["example.com", "acme.io"],
"maxPagesPerDomain": 6,
"defaultCountry": "US",
"delaySecs": 1
}
Build the websites array from the current batch (map your sheet column, webhook body or code step into that field). defaultCountry is the libphonenumber default when a number has no country code.
- Run Asynchronously: set this to false (off) so the step waits for the Actor to finish. The published action defaults this to true, which only starts the run and returns the run object immediately — too early to read results.
- Optional: Timeout (seconds), Memory (MB), Max Total Charge USD (a spend cap for pay-per-event Actors). Start with defaults for a small test.
- Add another Apify step: Get Dataset Items. The enricher writes one dataset item per website; that is the output you want. Map the run's
defaultDatasetIdinto the Dataset ID field. - After a synchronous Run Actor (Run Asynchronously off), the action returns{ run, output }. Userun.defaultDatasetId. Theoutputvalue is the run's default key-value store record (keyOUTPUTby default) — not a substitute for the dataset. - After an asynchronous start, the step returns the run object itself (which includesdefaultDatasetId), but the dataset may still be empty until the run finishes — use Path 1's wait setting, Path 2 below, or the event trigger in the next section. - Loop or map over the returned items. Per site you get:
emails,phones[].e164(plus country / line type),deliverability.status(READY/PARTIAL/NO_MX), MX provider, SPF, DMARC,contactabilityScore(0–100), social links, andbillable. - Write back to your sheet/table, or branch — e.g. score ≥ 50 and email present → email-ready; validated phone and score ≥ 30 → phone-first; else skipped. On Actor failure, leave input rows unmarked so the next schedule retries.
Optional: react instead of wait
If you prefer fire-and-forget: leave Run Asynchronously on (the action default), then a separate workflow with the Apify trigger New Finished Actor Run (Instant). Configure it for shephouse/website-contact-enricher, then Get Dataset Items from that finished run's defaultDatasetId. For a simple enrich loop, waiting in Run Actor is usually enough.
Path 2: HTTP run-sync-get-dataset-items
If you would rather call Apify's API directly (same pattern as our CSV / Console + API guide), use Pipedream's HTTP request action (Send any HTTP Request) or a Node/Python code step.
Do not put an API token in the step. Create a Pipedream environment variable named APIFY_TOKEN (workspace Settings → Environment Variables, or the project's Variables), mark it as a secret, and paste your token from Apify Console → Settings → Integrations only into that secret. In an action field, reference it as {{process.env.APIFY_TOKEN}}. In Node.js code, use process.env.APIFY_TOKEN. In Python, os.environ["APIFY_TOKEN"].
The documented endpoint is Run Actor synchronously and get dataset items:
POST https://api.apify.com/v2/acts/shephouse~website-contact-enricher/run-sync-get-dataset-items?timeout=280
(acts is the long-standing path used in our other guides; Apify's current OpenAPI also documents /v2/actors/:actorId/run-sync-get-dataset-items. The :actorId value is the tilde form shephouse~website-contact-enricher.)
Configure the HTTP request:
- Method:
POST - URL: the endpoint above
- Header
Authorization:Bearer {{process.env.APIFY_TOKEN}}(placeholder — your secret env var) - Header
Content-Type:application/json - Body:
{
"websites": ["example.com", "acme.io"],
"maxPagesPerDomain": 6,
"defaultCountry": "US",
"delaySecs": 1
}
The endpoint waits for the run and returns the dataset items as a JSON array. Apify documents a maximum wait of 300 seconds; if the run exceeds that, the HTTP response is 408 while the Actor run itself continues. Configure the HTTP client timeout to be long enough (our other guides use timeout=280 on the query string). If a Pipedream step times out before the Actor finishes, use Path 1 (wait in Run Actor, then Get Dataset Items) or the New Finished Actor Run trigger instead of this sync call.
Optional Node.js shape inside a Pipedream code step (same URL, placeholder token only):
import { axios } from "@pipedream/platform"
export default defineComponent({
async run({ steps, $ }) {
const websites = ["example.com", "acme.io"] // map from a prior step
return await axios($, {
method: "POST",
url: "https://api.apify.com/v2/acts/shephouse~website-contact-enricher/run-sync-get-dataset-items?timeout=280",
headers: {
Authorization: `Bearer ${process.env.APIFY_TOKEN}`,
"Content-Type": "application/json",
},
data: {
websites,
maxPagesPerDomain: 6,
defaultCountry: "US",
delaySecs: 1,
},
})
},
})
Batch large lists (for example 25 domains per call) so the sync timeout stays comfortable.
How to read the output fields
One dataset item per website. Useful columns:
| Field | Meaning |
|---|---|
emails |
Public emails found on the site (own-domain first when possible) |
phones[].e164 |
Validated E.164 form; also country / line type when available |
deliverability.status |
READY, PARTIAL or NO_MX — skip email outreach on NO_MX |
| MX provider, SPF, DMARC | Why a domain is only partial |
contactabilityScore (0–100) |
Sort or gate the next paid steps |
billable |
Whether this website counted as a paid result |
| social links | Fallback channel |
Practical triage (guidance — wire this in a Code step or a filter, not as a claimed prebuilt template):
- Drop no-reply / placeholder addresses.
- Email-ready: has an email and
deliverability.statusisREADYorPARTIAL, preferably score ≥ 50. - Phone-first: validated
phones[].e164and score ≥ 30 when email is weak. - Skipped: everything else that returned.
- Keep a source / original website column for GDPR “where from?” answers.
Cost
About $3 per 1,000 websites with results; sites that fail or return nothing are not charged (plus a tiny Apify run-start fee). Check the Store pricing tab for the current figure. Apify usage is billed by Apify, separate from Pipedream. Deliverability and validated phones matter more than the unit price — emailing a NO_MX domain just bounces.
Compliance basics (not legal advice)
- Public business contacts only, with the source kept.
- GDPR: a named person's work email is personal data — document a lawful basis and honour objections.
- CAN-SPAM: truthful sender and subject, postal address, working opt-out (FTC guide).
- Check do-not-call registries before phoning.
- No spam: a few relevant messages, and stop when asked.
Related guides
- n8n: Sheet websites → contacts
- Activepieces: Sheets → Apify enrich
- Enrich a CSV of websites (Apify Console + API)
- Clay: emails + phones from a website column
- Find emails from a list of websites
- Enrich a lead list with phone + deliverability
- Google Maps leads to contacts
Optional: Pipedream Template Gallery later
Pipedream accepts workflow submissions for its template gallery at forms.pipedream.com/submit-template (a share link, a short description, a longer Markdown write-up). You do not need a gallery listing to follow this guide. We have not submitted a template for this flow.
What we actually ran
| Claim | Status |
|---|---|
| Apify Pipedream docs + Pipedream Apify app / Run Actor / Get Dataset Items labels | READ from docs.apify.com/integrations/pipedream, pipedream.com/apps/apify, and the published Run Actor action |
HTTP run-sync-get-dataset-items endpoint and 300s / 408 behaviour |
READ from docs.apify.com/api/v2/actor-run-sync-get-dataset-items-post |
| Pipedream env-var and HTTP request action docs | READ from pipedream.com/docs |
| Store pricing | READ 2026-11-08: from $3.00 / 1,000 websites with contacts; failures free |
| Workflow built / tested in Pipedream Cloud | DID NOT RUN |
| Live Apify run for this guide | DID NOT RUN — $0 spent; use your own YOUR_APIFY_TOKEN / APIFY_TOKEN env var |
| Pipedream template gallery submit | DID NOT RUN |