Product tour
See how each source changes the map.
Contacts, calendars, CRM exports, customer files, LinkedIn exports, and target accounts each add different evidence. WarmPath keeps that evidence visible instead of flattening everything into a generic lead list.
More sources make the map stronger.
WarmPath gets stronger with every source you connect. You can begin with one read-only source to see your first warm paths, but add every relevant source you can — CRM, calendar, contacts, or upload context — to uncover more overlaps, stronger evidence, and better account-specific angles.
Every connector is read-only
We never send messages, update CRM records, or contact anyone
You can disconnect any source at any time
Coverage score
Add more connectors to improve coverage. One source gives an initial graph; more relevant sources improve overlap, corroboration, and confidence.
- Contacts: find who you already know
- Calendar: find past meetings and shared attendees
- CRM: add account history and ownership context
- Target accounts: focus the graph on companies you care about
14Upload / export
6Sandbox OAuth
5Roadmap
CRM (5)Contacts & calendar (9)Workspace (1)CDP & product analytics (2)Payments & commerce (2)Community & events (2)Newsletter & audience (2)Upload fallbacks (2)
Upload/export
Grouped by source type — upload CSV, ICS, or export files you already have.
Contacts & people
| Source | Status | What we read | Requested scopes | Privacy posture |
|---|---|---|---|---|
| Contacts CSV | Upload/export | Personal and work contacts from spreadsheet exports | No OAuth scope; upload/export fallback | Uploaded contact files stay scoped to your WarmPath build; we do not reshare or enrich with bought lists. Fallback: Upload a contacts CSV with name, email, company, and title columns |
| Customer CSV | Upload/export | Existing customers and past buyers | No OAuth scope; upload/export fallback | Customer data is treated as proprietary relationship signal — never sold or merged with third-party databases. Fallback: Upload a customer CSV with name, email, company, and status columns |
| Newsletter subscriber exports | Upload/export | Audience and subscriber CSVs | No OAuth scope; upload/export fallback | Newsletter subscriber data stays scoped to your build and is not used for list resale. Fallback: Upload a newsletter or community subscriber CSV |
| LinkedIn export | Upload/export | Official connection export or manually prepared CSV — upload only | No OAuth scope; upload/export fallback | LinkedIn is upload/export only. No login, cookies, browser automation, scraping, or credential access. Fallback: Use LinkedIn's official connection export or a CSV you prepare manually |
| Google Contacts export | Upload/export | Contacts export or prepared CSV until OAuth tests pass | No OAuth scope; upload/export fallback | Google Contacts export files are parsed like any upload — no Google credentials required for this path. Fallback: Export Google Contacts to CSV and upload |
Accounts & targets
| Source | Status | What we read | Requested scopes | Privacy posture |
|---|---|---|---|---|
| Accounts CSV | Upload/export | Named companies and account lists | No OAuth scope; upload/export fallback | Account uploads are used only to build your private graph for this build. Fallback: Upload an accounts CSV with company name, domain, and industry columns |
| Target-account CSV | Upload/export | Named accounts you want to reach | No OAuth scope; upload/export fallback | Target-account lists inform fit scoring within your private graph only. Fallback: Upload a target-account CSV with company name and domain |
CRM & revenue systems
| Source | Status | What we read | Requested scopes | Privacy posture |
|---|---|---|---|---|
| CRM export files | Upload/export | HubSpot, Salesforce, and similar CRM contact/deal exports | No OAuth scope; upload/export fallback | CRM exports are parsed locally for your build; we do not sync live CRM or store credentials. Fallback: Export contacts/deals from your CRM and upload the CSV |
| HubSpot exported files | Upload/export | Contacts, companies, and deals export | No OAuth scope; upload/export fallback | HubSpot exports are file-based only until OAuth is implemented and tested. Fallback: Export HubSpot contacts/companies/deals and upload CSV |
| Salesforce exported files | Upload/export | Accounts, contacts, and opportunities export | No OAuth scope; upload/export fallback | Salesforce exports are file-based only until OAuth is implemented and tested. Fallback: Export Salesforce accounts/contacts/opportunities and upload CSV |
| CDP & product exports | Upload/export | Segment-style usage and customer product signals | No OAuth scope; upload/export fallback | Product usage exports inform timing signals only within your private graph. Fallback: Upload a CDP or product analytics customer/event export CSV |
Calendar & events
| Source | Status | What we read | Requested scopes | Privacy posture |
|---|---|---|---|---|
| Calendar ICS/CSV | Upload/export | Meeting history from calendar exports | No OAuth scope; upload/export fallback | Calendar uploads use event metadata (title, time, attendees) — private event bodies are not ingested. Fallback: Export calendar as ICS or upload a meeting-history CSV |
| Google Calendar export | Upload/export | Calendar export or ICS until OAuth tests pass | No OAuth scope; upload/export fallback | Google Calendar ICS uses metadata-first posture — event bodies not ingested by default. Fallback: Export Google Calendar as ICS and upload |
| Event & community exports | Upload/export | Attendee, member, and participant files | No OAuth scope; upload/export fallback | Event lists are used for relationship overlap signals — not for outbound sending. Fallback: Upload an attendee or community member CSV export |
Sandbox direct connect (test mode)
OAuth connectors staged in sandbox/test mode only — not live production connect.
| Source | Status | What we read | Requested scopes | Privacy posture |
|---|---|---|---|---|
| Google Contacts OAuth | Sandbox direct connect | Sandbox direct connect — read-only Google Contacts via least-privilege OAuth | https://www.googleapis.com/auth/contacts.readonly | Sandbox/test-mode OAuth only. Read-only contact names, emails, and organizations — no write, delete, or live production connect without operator go. Fallback: Export Google Contacts to CSV and upload until live OAuth is operator-approved |
| Google Calendar OAuth | Sandbox direct connect | Sandbox direct connect — read-only calendar metadata via OAuth | https://www.googleapis.com/auth/calendar.readonly | Sandbox/test-mode OAuth only. Metadata-first: event title, time, and attendees — private event bodies are not ingested. Fallback: Export Google Calendar as ICS and upload until live OAuth is operator-approved |
| HubSpot CRM OAuth | Sandbox direct connect | Sandbox direct connect — read-only HubSpot CRM contacts via OAuth | crm.objects.contacts.read | Sandbox/test-mode OAuth only. Read-only HubSpot contacts and companies — no live production connect without operator go. Fallback: Export HubSpot contacts/companies/deals and upload CSV until live OAuth is operator-approved |
| Salesforce CRM OAuth | Sandbox direct connect | Sandbox direct connect — read-only Salesforce accounts and contacts via OAuth | api | Sandbox/test-mode OAuth only. Read-only Salesforce CRM objects — no live production connect without operator go. Fallback: Export Salesforce accounts/contacts/opportunities and upload CSV until live OAuth is operator-approved |
| Microsoft Contacts OAuth | Sandbox direct connect | Sandbox direct connect — read-only Microsoft 365 contacts via Graph OAuth | Contacts.Read | Sandbox/test-mode OAuth only. Read-only Microsoft contacts — no live production connect without operator go. Fallback: Export Microsoft contacts to CSV and upload until live OAuth is operator-approved |
| Microsoft Calendar OAuth | Sandbox direct connect | Sandbox direct connect — read-only Microsoft calendar metadata via Graph OAuth | Calendars.Read | Sandbox/test-mode OAuth only. Metadata-first calendar events — private event bodies are not ingested. Fallback: Export Microsoft calendar as ICS and upload until live OAuth is operator-approved |
Direct connect
Production direct connect paths require operator go-live. Use sandbox OAuth or upload/export fallbacks below.
Roadmap
Planned connectors — not available in your build until implemented and tested.
Pipedrive, Close, AttioSegment, Amplitude, Mixpanel, PostHogMailchimp, ConvertKit, BeehiivStripe & Shopify customersLuma, Eventbrite, Circle, Slack exports
Your data becomes a private opportunity graph
Sources normalize into people, accounts, relationships, and signals — then rank into warm paths you can inspect before any outbound motion.
Sources
- Contacts & calendars
- CRM/CDP exports
- Customer & audience files
- LinkedIn export
- Target accounts
Private graph
People · Accounts · Relationships · Signals
Your data stays yours. Evidence preserved per source.
Ranked opportunities
- Best warm path
- Why now
- Suggested intro ask
- Confidence & gaps
How it works
Step 1You can begin with one read-only source or upload fallback.
Step 2Add more connectors to improve coverage and corroboration.
Step 3Inspect source evidence, confidence, and gaps.
Step 4Export CSV + brief + manual review checklist.