01
Direct answer
There is no DewEngine Sales Navigator extraction path
Sales Navigator search, lead and account lists, profiles, and InMail context are decision-gated targets described in the platform plan, not released methods. DewEngine has no approved contract, adapter, or real-account evidence. Do not substitute page scraping, session replay, reverse engineering, or access-control bypass. Begin with a data requirement that can accept customer-owned or licensed inputs.
- Keep the integration control disabled
- Document a non-LinkedIn source for essential customer workflows
02
Entitlement
Verify the exact subscription and user
A future connection would need to bind the customer workspace, acting user, professional account, Sales Navigator entitlement, and approved operations. Search, lists, and InMail cannot be assumed to travel together. Capability discovery should be recomputed after connect, reconnect, subscription change, and role reassignment. Unknown entitlement must fail closed rather than return guessed support.
- Store entitlement evidence with observation time
- Invalidate scheduled work after downgrade or transfer
03
Data selection
Choose a narrow resource and destination
A CRM account-review feature may need selected company observations and provider-list membership. A lead-review feature may need user-selected profiles and query provenance. Neither requires every message, saved item, or search result. Define fields, time range, purpose, retention, customer record mapping, and review step for each flow. Treat list membership as account-scoped context, not universal truth.
- Minimize fields before designing pagination
- Keep people and company imports in typed pipelines
04
Staged import
Preview and reconcile before writing CRM truth
Place authorized observations in a tenant-scoped staging area, match them using provider IDs and customer evidence, then show additions and conflicts. Commit accepted changes idempotently and record who reviewed them. A new role or company should not overwrite ownership, consent, or lifecycle stage. Partial pages remain visible as partial rather than masquerading as a complete export.
- Support reject, unlink, merge, and split
- Resume from durable progress after interruption
05
Operations
Respect account state and product feedback
Search and list refreshes need conservative per-account budgets, cancellation, deduplication, and stale coverage indicators. Challenge, restriction, entitlement loss, or legal kill switch stops collection and provider-visible actions. Do not use randomized access patterns, distributed accounts, or human-mimicry to avoid enforcement. The operator should see safe failure classes and a user-action path.
- Separate product budgets from claimed provider quotas
- Keep raw personal content out of operational telemetry
06
Approval evidence
Qualify the selected slice, not the brand
Release requires counsel and provider approval, verified eligible subscriptions, field and filter fixtures, list ownership tests, pagination, partial sync, throttling, restriction, reconnect, tenant isolation, CRM conflict handling, retention, export, deletion, audit, and kill switches. Consented real-account proof is method-specific. Until it exists, software teams should treat this page as requirements guidance only.
- Maintain a dated method-and-field matrix
- Remove public claims automatically when evidence expires