Do not turn a LinkedIn profile into an invented email address

A precise guide to separating profile identity, customer-known contact data, authorized enrichment, verification, and outreach permission when DewEngine exposes no such lookup.

Educational research only. LinkedIn account access remains decision-gated. No DewEngine LinkedIn connector is approved or implemented.

Talk to us ↗Read technical guides →

Truthful answer

DewEngine cannot get an email from a LinkedIn profile

The LinkedIn target catalog contains profiles, companies, relations, messages, invitations, posts, search, and jobs. It does not declare email discovery, an email field, or an enrichment-provider contract. The connector is also decision-gated and unimplemented. A product must not imply that a public profile exposes an email through DewEngine or that DewEngine can reveal one today.

Return unsupported for profile-to-email requests
Do not fabricate provider fields from third-party guesses

Identity separation

Keep professional identity and contact point distinct

A profile reference can help a user identify a person, while an email address may come from the customer's address book, a direct exchange, an application, a company directory, or a separately licensed source. Store each external identity and contact point with independent provenance. Matching them requires evidence and review; a shared name or employer is not enough.

Record how the email was obtained and when it was verified
Allow unlinking without deleting unrelated customer history

Authorized alternatives

Prefer first-party and consented contact data

Ask whether the customer already has an email through a legitimate relationship, inbound form, contract, recruiting application, or direct conversation. If a licensed enrichment service is considered, evaluate its data sources, contract, privacy roles, accuracy, suppression, retention, and deletion separately. Do not use scraping, hidden page data, pattern guessing, or access-control bypass as a substitute.

Keep each enrichment vendor outside the LinkedIn fact layer
Document the lawful purpose before any lookup

Verification

A plausible address is not a confirmed mailbox

Pattern-derived addresses can belong to another person, a recycled mailbox, or no account at all. Label guesses as unverified and avoid sending merely to test them. Verification providers have their own contracts and limitations and do not create contact permission. Let users see source, confidence, and last verification, and protect manual corrections from automated replacement.

Never present a guessed address as LinkedIn-provided
Avoid mailbox probing that creates unwanted traffic

Outreach permission

Separate address possession from permission to email

Even a correct business email does not settle lawful basis, recipient expectation, customer purpose, local regulation, prior opt-out, suppression, or sender identity. The email-sending workflow must apply its own policy and provider controls. A profile research action should end without automatically creating a draft or enrolling a sequence. Preserve the decision trail that authorized any later contact.

Check global and customer-specific suppression
Provide an accountable reply and opt-out path where required

Implementation checklist

Make source boundaries visible in schema and UI

A sound contact model stores source type, acquisition basis, subject, customer owner, observed or verified time, confidence, permitted uses, retention, and deletion state. Tests should cover wrong matches, recycled addresses, tenant isolation, correction, export, erasure, and suppression races. None of this changes DewEngine's LinkedIn status; no connector or profile-email feature can ship without separate approval and evidence.

Keep profile and email access permissions independent
Delete derived links when their evidence is withdrawn

Questions

Before you build.

Does profile.get include an email address in DewEngine?+

No. profile.get is only an unimplemented target method, and the capability catalog makes no email-field claim. DewEngine has no approved LinkedIn connector or profile-to-email endpoint.

Can an email pattern guess be used for outreach after matching a profile?+

A guess is not provider data, verified identity, or permission to contact. Keep it labeled and separate, evaluate the source and lawful purpose, and require the email workflow's normal verification and suppression controls.

Build with us

Does this match the workflow your users need?

DewEngine is in development. Real use cases decide what ships first.

Share your use case ↗