LinkedIn Outreach Draft Generator — HeyReach Alternative

Generate LinkedIn outreach drafts from a campaign brief and supplied prospects. Export opening messages, follow-ups, and CRM IDs in a manual-review queue. Every draft remains marked for human review and not sent. For campaign reviewers, each dataset row is one review-ready lead with message drafts, QA signals, and explicit not-sent status.

Workflow: put the results to work

Supply the campaign proposition, call to action, and prospect records already approved for preparation. Review opening and follow-up drafts with their CRM IDs, then edit them before any separate sending step. The Actor preserves the not-sent status on every draft.

What it returns

One dataset item is one review-ready B2B lead record.

Field	What it gives you
sequenceId, draftFingerprint	Stable rerun and CRM join keys.
prospectFullName, companyName, role, linkedInProfileUrl	Known or public professional identity context; unconfirmed company values remain null.
publicProfile	Selected public headline, location, summary, skills, and short experience highlights—never email addresses, cookies, raw responses, or account state.
leadGeneration	The public professional search criteria for leads discovered by this Actor.
enrichmentStatus, collectionTelemetry, source	Clear collection status and safe provenance.
messageSequence	Review-only opening and optional follow-up drafts.
draftWarnings, approvalChecklist	Gaps a human must resolve before any manual use.
reviewStatus, actionStatus	Always requires_human_review and not_sent.

Choose a workflow

Workflow	Starting input	Best use	Does not do
review_known_prospects	CRM or approved-research records	Turn existing leads into governed review records.	Search or collect public profile data unless you opt in.
enrich_public_profiles	Public linkedin.com/in/... URLs	Add selected public professional context to a list you already own.	Access private profiles, emails, cookies, or login-only data.
find_public_leads	Public professional query or job title, plus optional company/location	Build a bounded public lead-research queue and enrich each returned public profile.	Guarantee a match, contact detail, current employment, or contact permission.

Quick start inputs

1. Find and enrich public B2B leads

{
  "workflow": "find_public_leads",
  "campaignName": "US CTO research",
  "campaignGoal": "sales_conversation",
  "senderName": "Example Sender",
  "senderCompany": "Example Studio",
  "reviewOwner": "Example Reviewer",
  "leadSearch": {
    "query": "chief technology officer",
    "company": "Microsoft",
    "location": "United States"
  },
  "valueProposition": "We are researching practical workflow improvements for B2B teams.",
  "callToAction": "Would a brief conversation next week be useful?",
  "followUpCount": 1,
  "maxProspects": 5
}

2. Enrich public profile URLs you already have

{
  "workflow": "enrich_public_profiles",
  "campaignName": "Partner profile review",
  "campaignGoal": "partnership",
  "senderName": "Example Sender",
  "profileUrls": [
    "https://www.linkedin.com/in/example-person"
  ],
  "valueProposition": "We are exploring a practical joint workflow for shared B2B customers.",
  "callToAction": "Would it be useful to compare notes next week?",
  "maxProspects": 1
}

3. Keep your CRM-only review workflow

{
  "workflow": "review_known_prospects",
  "campaignName": "Event follow-up review",
  "campaignGoal": "event_follow_up",
  "senderName": "Example Sender",
  "reviewOwner": "Example Reviewer",
  "prospects": [{
    "externalId": "event-001",
    "fullName": "Example Contact",
    "companyName": "Example Company",
    "role": "Product Lead",
    "contextNote": "Met at the product leadership roundtable."
  }],
  "valueProposition": "We are continuing the discussion about practical review workflows.",
  "callToAction": "Would it be useful to compare notes next week?",
  "followUpCount": 1,
  "maxProspects": 1
}

Set enrichPublicProfiles: true in the CRM-only workflow if each supplied prospect already has a public LinkedIn profile URL you want enriched. It defaults to false, preserving the existing CRM-only collection path.

Representative result

{
  "sequenceId": "seq_c3a8fb37e5b786bb",
  "externalId": null,
  "campaignName": "US CTO research",
  "prospectFullName": "Example Person",
  "companyName": "Example Ltd",
  "role": "Chief Technology Officer",
  "linkedInProfileUrl": "https://www.linkedin.com/in/example-person",
  "publicProfile": {
    "headline": "Chief Technology Officer",
    "location": "United States",
    "summary": "Selected public professional summary.",
    "skills": ["Engineering", "Product strategy"],
    "experienceHighlights": [{ "title": "Chief Technology Officer", "companyName": "Example Ltd" }],
    "collectedAt": "2026-09-02T00:00:00.000Z"
  },
  "enrichmentStatus": "completed",
  "source": "public_lead_search_and_profile_enrichment",
  "reviewStatus": "requires_human_review",
  "actionStatus": "not_sent"
}

The sample illustrates shape, not accuracy, contact permission, relevance, or a claim that a person is currently employed by a company.

How this workflow alternative fits beside HeyReach

This is a focused workflow alternative, not a full-suite replacement. It can replace the bounded job of researching public professional leads, enriching a review queue, and preparing a governed record before manual action.

Choose HeyReach when the job needs its broader connected execution suite: sender accounts, active campaigns, automated LinkedIn actions, inbox work, multichannel outreach, workspaces, or its documented integrations. See HeyReach’s current plans, campaign workflow, and integrations.

Same-job dimension	This Actor	HeyReach
Bounded job	Public lead research, public-profile enrichment, and review records.	Broader connected campaign execution and collaboration.
Buyer input	Query/profile URLs/known CRM prospects plus a campaign brief.	Connected sender accounts plus campaign and lead workflow setup.
Deliverable	Structured rows with provenance, QA, approval checks, and no-send status.	Campaign operations, actions, inbox, and connected workflows.
Billing	Pay per event plus platform usage; see the Pricing tab for current rates.	Current plan and capacity terms apply; check the linked live terms.
Effective efficiency	One accepted public or known lead becomes one joinable review record with provenance and QA in the same run.	Broader campaign operations suit jobs that continue beyond review.
Trade-off	Best where the work ends at research and human approval.	Best where the work continues into automated outreach and inbox operations.

API and agent use

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/heyreach-alternative').call({
  workflow: 'find_public_leads',
  campaignName: 'Partner research',
  senderName: 'Example Sender',
  leadSearch: { query: 'partnerships lead', location: 'United States' },
  maxProspects: 3
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

For an MCP client, ask for a bounded job and leave every final contact decision with a reviewer:

Find up to five public CTO profiles in the United States, enrich the public profile facts, return review-only records, show QA warnings, and keep actionStatus as not_sent. After the run, read OUTPUT.outcome, inspect dataset provenance, and check the capped event cost.

Inspect OUTPUT.outcome, RUN_SUMMARY, and the dataset before acting on results.

Outcomes and recovery

Outcome	Meaning	What to do
COMPLETE	Every in-cap record completed as requested.	Review warnings and complete the checklist.
PARTIAL	Useful records were written, with invalid, capped, or unavailable enrichment noted.	Read RUN_SUMMARY; rerun only the missing scope.
VALID_EMPTY	A working public search found no eligible public profiles.	Tighten or broaden the query before another run.
INVALID_INPUT	A required campaign field or workflow input is missing/invalid.	Follow the input example and retry.
CONFIG_ERROR / UPSTREAM_FAILED	The advertised public-data path could not produce useful output.	Retry once later; if repeated, share the run ID with support.

Best results

Start with a specific public role or professional query, a clear geography, and a small maxProspects cap. Provide factual relationship context for known prospects, confirm public-profile facts in the resulting row, and use source, enrichmentStatus, and draftWarnings as the reviewer’s starting point. The best workflow pairs public data collection with an authorized CRM review process before any manual contact decision.

Builder's note

I built this workflow around a simple observation: a public profile alone is not a usable lead workflow. I designed the record to preserve provenance, make missing facts visible, keep the data small and reviewable, and leave the contact decision with a person.

Responsible use

Use only professional data you are authorized to process. Before manual outreach, verify identity, company, factual relevance, legitimate purpose, prior contact, consent, objections, opt-outs, privacy/anti-spam duties, applicable law, platform terms, timing, and channel. This Actor leaves every final contact decision to a human.

HeyReach is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by HeyReach.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
review-ready-prospect	Review-ready prospect draft	One caller-supplied prospect converted into a persisted review-only draft sequence. The Actor never sends or schedules the drafts.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.