Contacts & CRM
Import contacts, custom fields, categories, deals, and pipelines.
Contacts are the people you reach out to; the CRM tracks what happens after they reply.
Importing
Two routes share the same column-mapping screen: a file upload and an on-demand Google Sheets sync.
From a file (CSV, TSV, or XLSX, up to 50 MB and 50,000 rows), the wizard runs Upload, Map, Options, Result. Parsing happens server-side. Start it from Contacts, or from a campaign's Leads tab to attach the imports to that campaign automatically. The result step reports imported, updated, skipped, and failed counts, and failed rows download as an error CSV you can fix and re-import.
You must map at least one column to Email.
| Field | Notes |
|---|---|
| Required, and used to dedupe | |
| First name, Last name, Company, Phone | Standard identity fields |
| Subscribed | A truthy value marks the contact subscribed |
| Categories | Existing category names to apply |
| Custom field | Anything else; you name it |
Duplicates match on lowercased email
[email protected] and [email protected] are the same contact. Choose Skip existing (leave untouched), Update existing (merge new values in), or Create duplicates (force a new one, falling back to update if a uniqueness rule blocks it).
Rows with a missing or invalid email are reported with a line number and reason rather than imported.
From Google Sheets, a sheet is a reusable sync source rather than a one-time upload. Connect it once (Warmbly reads only the tab you choose and never writes back), paste the spreadsheet ID from the URL between /d/ and /edit, pick the tab, map columns, then set duplicate handling, a label, and optionally a campaign to enroll into and categories to apply. Nothing syncs automatically: press Sync now, or save and sync immediately.
Saved sources live in your Sync sources list to re-run, edit, or remove. Each sync dedupes on lowercased email using your chosen duplicate handling, so re-syncing a sheet with new rows is safe.
Custom fields
For anything beyond identity: industry, plan tier, account owner. Create them by mapping a column to "Use as custom field" during import, or on a contact's Details tab.
They feed personalization, which is the main reason to get imports right.
Field names with spaces work too
Simple names (letters, numbers, underscores) use a dot: {{.industry}}, {{.account_owner}}. Names with spaces or dashes work the same way, written exactly as named:
Your role as {{.job title}} at {{.Company}} caught my eye.Both forms work everywhere, including inside {{if}} conditions and helper functions.
See Personalization & expressions for the full templating language.
Categories
Colored labels that group and filter contacts (Warm lead, Conference 2026, Enterprise), behaving like tags. The same picker appears in bulk edit, a contact's Details tab, the new-contact dialog, the filters, and the import and sync wizards.
It supports type-ahead search, and typing an unmatched name offers Create to add and select it in one step. Each category keeps its color everywhere its chip appears.
Categories also drive automation: a sequence can run Add tag or Remove tag as a contact moves through a flow, so a label can be applied automatically on a positive reply.
Deals and pipelines
A pipeline is a named, ordered sequence of stages a deal advances through. On the Pipelines page you create pipelines (new ones start with Open, Qualified, Won), then add, rename, recolor, and delete stages, each showing its deal count. Stage order is the left-to-right column order on the board.
| View | Behavior |
|---|---|
| Table (default) | Every deal across all pipelines, server-paginated. Totals like open count and pipeline value are real sums over the whole result, not just loaded rows |
| Board | Single-pipeline kanban, one column per stage, drag cards to move stages. Each column paginates itself, and header counts come from the server summary |
A deal has a name, stage, value and currency (default USD), expected close date, and a status of open, won, or lost. The linked contact is shown read-only.
Campaigns can create and advance deals automatically with Create deal and Move deal stage actions, so the CRM stays current without manual entry.
Suppression
A suppressed contact receives no further mail. Unsubscribed contacts are skipped by every campaign automatically; toggle subscription on the Details tab, and filter the list by Subscribed or Unsubscribed.
Suppression also happens automatically on a hard bounce or spam complaint, and a sequence can run an Unsubscribe action.
This is the safe default response to a bad signal: stop sending rather than keep collecting bounces and complaints. See Deliverability for the signals behind it.