Skip to guide

See Distill in action

Request Demo

Tell us a little about yourself and we’ll follow up to schedule time.

Browse guides

Lists

On this page 13 sections

What lists are for#

A Distill list brings people or companies together with information useful for research, assessing audience fit, and outreach. It can contain profiles found in Distill, an existing contact list, event attendees, target companies, or records arriving from another system.

Lists preserve the context around an audience. For example, a list can hold who attended an event, how the sender knows each person, the topic they discussed, and whether the person is relevant to a particular campaign.

A list can support research without being connected to outreach. When it supplies a campaign’s audience, changes to the list can also affect that campaign.

How lists relate to the rest of Distill#

Part of DistillWhat it represents
ProfileInformation about one person or company
ListA collection of profiles or records, with columns for additional context
SearchA way to find and evaluate people or companies; results can be saved to lists
Targeting groupAn audience organized through criteria, searches, and lists
CampaignThe sender, messages, channels, and follow-up used to contact people from an audience

A row belongs to a list. Its matched profile describes the person or company. Those are different things: correcting a row’s match changes which profile it refers to, while editing a note changes the information stored on that row.

People lists contain named contacts. Company lists help identify target organizations and find the relevant people who work there. General lists can hold both record types, but separate People and Company lists make the purpose clearer. A company itself is not a direct outreach recipient.

Connector lists identify people whose available networks can be searched. The Distill team can prepare them using the LinkedIn Connections column described below. Connector lists and Do Not Contact lists have their own purposes and controls; they are not ordinary campaign target lists.

Ways to build a list#

Starting pointWhat Distill supports
Profiles or search results in DistillSave selected profiles to a new or existing list
Known contactsAdd profiles individually or in bulk using identifying information such as LinkedIn URLs or email addresses
SpreadsheetImport a CSV, or upload an Excel .xlsx file in the app; Excel imports use the first worksheet
Form, signup, event, or another systemSend records to a list through its inbound webhook, a private address another system can submit records to
Connected CRM (customer relationship management system)Show available CRM context alongside list entries; available data depends on the provider and connection
Distill’s Global ListsDuplicate an available curated list into an editable copy

A CRM connection, a spreadsheet import, and a webhook are different ways of working with information. Connecting a CRM does not mean that every CRM list or custom field automatically becomes a Distill list. Integrations explains supported CRM providers, matching, screening, refresh timing, updates sent back to the CRM, and disconnection.

Importing existing people, companies, and context#

An import can carry both identity information and extra columns. For people, a LinkedIn profile URL or email provides a useful starting point. A name can be matched with company, title, or email context. A name on its own remains unconfirmed because it does not reliably identify one person.

For companies, a website or LinkedIn company URL is useful. Company-name matching can resolve an exact match, but a name alone may remain unresolved or ambiguous.

Information in the filePurpose
Name, email, or profile URLIdentify the person or company
Company and titleHelp distinguish people with similar names
Extra columns such as Event, Relationship, or Relevant topicPreserve supplied context as text columns

The import needs a header row. Distill recognizes supported identity columns, including email and URL data, and keeps supported extra context columns as text fields. Empty columns and some special-purpose import fields are skipped. Customers can choose to import people, companies, or both. Importing a column does not verify that its contents are true or current.

An email supplied in the file is separate from an email found by Distill. Campaign settings and email checks determine which address can be used.

For example, an event list might include a person’s LinkedIn URL, their company, the event name, and “Discussed a partner referral program.” Distill can retain that context beside the matched profile. It does not establish that the sender met the person unless the supplied information actually supports that claim.

Matching, processing, and duplicates#

Imports can run in the background. A request being accepted does not mean every row has finished processing. Results may include new entries, existing entries that were merged, skipped records, failed records, and people who still need a profile match.

Distill can keep an unresolved record on a list so that its identity can be confirmed later. An incorrect confirmed match can also be corrected. Confirming an unresolved person against a profile already on the same list can merge those rows. Company confirmation has different duplicate checks and may require review instead of a merge.

Re-importing a file does not always just add new rows. Matching rows can update existing custom-column values. Duplicate rows within a file and matches against an existing list are handled differently, so “100 processed rows” does not necessarily mean “100 new people.”

These outcomes are separate:

  • Received: the import or webhook request was accepted.
  • Stored: the row exists on the list.
  • Matched: the row is linked to the intended profile; unresolved rows still need confirmation.
  • Researched: requested profile information and research have finished loading.
  • Eligible for outreach: the person also meets the connected campaign’s screening and sending requirements.

Researching and organizing entries#

Lists support more than names and contact details. Columns can combine supplied information, research, relationship context, and outreach status.

Column categoryExamples and uses
Supplied contextText, notes, status, and imported fields
Profile informationCurrent company and other available person or company facts
Qualification and researchAI Questions, web research, and filter results with supporting information where available
RelationshipsIntro Paths and Graph Score, based on available connection information
Finding people at companiesFind the Right Person and Load People by Roles
CRM and outreachCRM Status, Campaign Notes, campaign position, and Contacted information

Some columns require a connected CRM, campaign, or relevant network access. Research and role searches can fill cells as results become available. An empty cell can mean that work has not finished or that a value has not been selected; it is not always a confirmed “no.”

AI Questions evaluate entries individually. A question such as “Does this company sell to banks?” fits that model. A question comparing all rows against each other, such as “Which of these companies is the best?”, is a different task.

Lists also support searching within entries, sorting, showing or hiding columns, moving matched entries between lists, adding their profiles to another list, and reviewing list history. Adding a profile to another list does not necessarily copy its custom-column values. A search can use a People list as its starting audience, or find relevant employees at companies on a Company list.

LinkedIn Connections and connector lists#

The Distill team can add a LinkedIn Connections column to an eligible people list to read the available connections of the people on it. Adding the column turns the list into a connector list. This is team-assisted setup, not a column every customer or assistant can add directly.

Whose network is this? identifies the Distill user the list is being prepared for. For example, a strategist can prepare an investor list for a founder while keeping the founder as the network owner. The list can flag people who are not that owner's recorded first-degree connections once the owner's own connection import is complete. Before that import finishes, an absent relationship is not a confirmed non-connection.

The column shows whether a person's connections are queued, being read, read, or unavailable, with counts and reasons where available. Hidden connections, missing LinkedIn URLs, account access, and LinkedIn limits can prevent or delay the work. A Read status can include a partial result; it does not promise every connection was retrieved.

A supported people search can then search the connectors' available networks and save matching targets to a separate list. The setup of that search currently requires the Distill team. A customer with access can continue using a search already prepared for their project. The resulting targets and their introduction paths are distinct from the original list of connectors. Networks and Introductions explain this workflow.

Using list context in messages#

Information stored in a list can support campaign personalization, but it is not automatically included in every message.

List information reaches messages in two ways:

  • Message variables insert a field’s value. When a campaign uses multiple source lists, a column must exist on every one to be offered as a variable. That still does not mean every row has a value. The campaign’s variable list shows which fields it can use.
  • AI writing context can include supported text, status, and research values from lists containing the person or their current employer in the same project. Custom AI Text can use this context even when a field is not offered as a message variable.

The block’s instructions and available information shape the generated wording.

An Event column might supply the event name. A Relationship note might help explain a real prior connection. Neither column means that every recipient has the same relationship to the sender, and missing context should not become an invented connection.

The list stores the information; the campaign determines how that information is used in the message. Message previews show the resulting copy for particular recipients.

Lists, campaign audiences, and exclusions#

For the targeting-group campaign workflow, a People list belongs to the intended project and is attached to the relevant targeting group before the campaign uses it. Attaching an existing list to a group does not move it into another project.

Adding people to a list does not create or launch a campaign. However, when the list already supplies an active campaign, new people can enter that campaign’s audience, subject to its screening and sending requirements.

Removing a person or changing a row’s profile can also affect connected campaigns. Removal can be blocked once someone progresses past New People in a campaign still using the list. Ended or deleted campaigns, and candidates already dismissed, do not create that block. Correcting a wrong match can require acknowledgment of the campaign impact. List editing is therefore not a substitute for controlling an active conversation.

An ordinary list named “Customers” or “Do not contact” does not, by its name or membership alone, block outreach. Distill’s actual exclusion and screening settings determine who can be contacted. Person-level exclusions, company-level exclusions, and the project they apply to need to match the intended scope.

A person can appear on a list while being excluded from outreach. Deleting a row is also different from recording a do-not-contact restriction. A useful exclusion depends on identifying the right person or company, rather than guessing from an incomplete name.

Bringing new records in through webhooks#

A list webhook is a private address that lets another system submit records to one list. It can support signups, demo requests, event registrations, or other approved inputs.

It accepts a name, URL, email, or a supported Distill candidate reference, with an optional person/company type and notes. Notes are stored in a list column. A webhook does not create a campaign or decide the messaging.

Webhook submissions are queued for background processing. An “accepted” response confirms receipt, not a successful profile match or delivery of an outreach message. Records can still need identity confirmation after processing.

The webhook address controls access to that input, so it stays private to the systems using it. It can be disabled or rotated. The List Webhooks guide contains the integration format and setup details.

Sharing and exporting#

Project-owned lists follow project access permissions. A link or passcode does not make a project list publicly accessible.

Lists outside projects can have a public view, optional passcode protection, and invited collaborators. Global Lists are curated, read-only sources; an editable duplicate is a separate list. Sharing and duplication depend on the list’s type and access rules.

CSV export supports taking list information into another workflow. The standard table export includes all current list rows and follows the list’s saved visible columns and column order, with additional contact fields when the list contains people. It does not reproduce a temporary search, filter, or row selection. Larger exports can be prepared in the background and delivered by email.

What a connected assistant can do#

The current Distill connector supports finding and creating lists, reading rows and their original input, adding people, importing CSV text, checking import progress, and reviewing unresolved matches. It can confirm an unresolved person or company match, correct a row linked to the wrong person, add text columns, update text or status values, and remove rows within the tool’s rules. Correcting an already confirmed company match is not supported by that same connector action.

Reading requires access to the list; changes require permission to edit it. Creating research or network columns, filling every specialized column, and exporting files are not implied by the presence of a general list tool.

Changes made through a list tool can take effect immediately. The current connected-account reference describes the exact tool fields and how to use them.

Common questions#

Can I bring my own contacts or an event attendee list?#

Yes. Lists can start from your own data. Identifying information helps Distill connect the rows to profiles, while extra columns preserve event or relationship context. Importing the list does not mean that everyone on it will receive outreach.

What information does Distill need to match the right person?#

A LinkedIn profile URL or email is useful. A person’s name can also be matched with company, title, or email context. A name alone is not enough to establish the correct person. Unresolved or incorrect matches can be reviewed and corrected.

Can I start with companies rather than people?#

Yes. A Company list can be the starting point for finding relevant roles at those companies. The resulting people form the contact audience; the company itself is not the message recipient.

Will uploading the same spreadsheet twice create duplicates?#

Distill attempts to merge matching records rather than create another live entry for the same profile on the list. A repeat import can also update existing custom values, so it should not be treated as a harmless duplicate upload. Unresolved or conflicting identities may still need review.

Will the notes and tags in my spreadsheet be used in messages?#

Not necessarily. Supported list values can be available as AI writing context, and supported fields from the campaign’s source lists can be inserted through message variables. Storing a note or tag does not by itself mean the message will use it or the outreach sequence will change. The message preview shows the actual result.

Can we exclude current customers or people already in our pipeline?#

Distill supports exclusions and screening based on connected CRM records. Their effect depends on the configured rules, available data, correct identity matching, and which people, companies, and projects the rules apply to. Merely importing a customer list or adding a “Customer” label is not the same as enabling an exclusion.

Why is someone in the list but not receiving outreach?#

They may still be unmatched, waiting for research, outside the campaign’s source audience, excluded by screening, missing usable contact details, or waiting on the campaign’s sending conditions. A saved row alone does not mean a message is ready to send.

Does removing someone from a list stop their outreach?#

Removing a row and stopping outreach are different operations. A person’s progress in a connected campaign can block removal, and deleting list membership does not record a do-not-contact restriction. Campaign status and exclusions determine the appropriate control for an active recipient.

All guidesBack to top
Distill product guidesAll pages as text