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

Integrations

On this page 12 sections

What integrations add to Distill#

Distill uses connected accounts to bring existing relationship information into outreach and record supported activity in the systems a team already uses. A customer relationship management system (CRM) connection can help show whether someone is already known, whether their company is a customer, and whether contacting them would overlap with existing work. Email, LinkedIn, and calendar connections serve different purposes.

Connections supply information and channel access. Configured screening rules and campaign settings determine how Distill uses them for outreach.

ConnectionMain purpose
CRMShow matching person, company, deal, and activity information; apply configured screening; record supported campaign activity
LinkedInUse the connected sender's LinkedIn account for supported network and outreach activity
EmailSend and receive supported campaign messages through the configured sender account
Calendar and booking toolsSupport meeting detection and scheduling workflows where the required connection or booking-event integration exists
List webhookBring records from an external system into one Distill list
AI assistantLet an authorized assistant use the Distill actions exposed by its connection

CRM connections and availability#

The established CRM connections for customers are HubSpot and Attio. Both bring CRM information into outreach, but they differ in the fields they read, the permissions they need, and the activity they record back in the CRM.

CRMConnectionMain distinctions
HubSpotSign in and grant access through HubSpotReads supported contact, company, and deal information. Supported campaign emails can be logged as email activity; supported LinkedIn actions can be logged as notes. Recording campaign activity can also create contacts and companies where supported.
AttioConnect a workspace access token with the necessary permissionsReads supported people, companies, deals, and eligible pipeline Lists. The workspace must specify which fields and values identify a customer. Supported campaign activity is written as notes; a note does not itself update Attio's last-contacted date.

For Salesforce, Apollo, or another CRM, contact Distill support about available connection options. CSV imports and list webhooks can bring records from other systems into Distill, but they do not provide the screening, activity history, and activity recording of a supported CRM connection.

Where the CRM connection applies#

A project's CRM connection supplies the CRM columns on its lists. Connecting it applies the connection to the project's lists and starts background lookups. New lists in that project receive the configured CRM column too. The connection belongs to the project's workflows; it does not change depending on which teammate opens a row.

Managing the project connection requires permission to edit the project. Granting access to the external CRM is a separate permission step. A person's stored HubSpot connection and a project's configured CRM connection are related but distinct: signing in to HubSpot does not, by itself, prove that the intended project and its lists are configured correctly.

A connection can be reused from another accessible project through the supported import option. This copies the connection settings, not every CRM record or campaign. Replacing a connection marks the affected saved CRM results as outdated and starts new lookups. Old results do not describe the new account.

What CRM information can appear#

CRM columns display supported information for the person or company represented by a Distill list row. They do not reproduce every object, custom field, automation, or report in the external CRM.

InformationExamplesImportant limit
Person recordCRM identity, record link, available contact history, lifecycle or lead statusThe match must refer to the intended person. A company match is not proof that the person has a CRM contact record.
Company recordCompany identity, relationship history, available customer statusA company-related restriction needs the relevant current-employer relationship. A former employer's history should not automatically describe the person's current company.
DealsAssociated deals, available stages, open/won/lost statusThe CRM's structure and the way its fields are mapped matter. A deal being present does not automatically make its company a customer.
ActivityAvailable notes, emails, meetings, calls, tasks, or other supported interactionsCoverage depends on the provider and granted permissions. An incomplete timeline is not evidence that no interaction occurred.

Attio can represent pipeline work through its deals object and through eligible company-based Lists with stage fields. Distill can read both supported forms. A missing permission, a failed pipeline read, or a result cut off by a provider limit can leave incomplete evidence.

The CRMs identify customers differently. HubSpot uses its customer lifecycle status. Attio uses the configured customer field and values, or an explicitly configured won-deal rule when a won deal means someone is a customer in that workspace. A meeting, an email, or an arbitrary status label does not automatically identify a customer.

How Distill matches a row to CRM records#

Distill first searches for a person using eligible email addresses. A returned CRM record must contain the address searched for to count as an exact email match. Without that match, Distill can use the person's name and current employer. Company lookups can use known domains and supported company-name matching.

Distill checks identity before linking a CRM person record. If the name does not match, it can remove that person match while keeping company and deal information matched separately. A row can therefore show a company relationship without a confirmed CRM contact for the person.

Duplicate CRM records, missing names, outdated employment, incomplete domains, or an abbreviated identity can make matching uncertain. Profile matching identifies the person in Distill; CRM matching finds that person's relationship to records in the connected CRM.

Using CRM information to avoid overlapping outreach#

The CRM connection provides information. Screening settings decide which information should hold someone back from outreach. Merely connecting a CRM does not mean every existing record is excluded.

For campaigns inside a project, CRM screening uses the project's settings. Supported conditions include:

ScopeConditions
PersonAlready in the CRM; previously contacted
Current companyAlready in the CRM; previously contacted; previously met; is a customer; has an open deal
Selected CRM valuesChosen pipeline stages, lifecycle stages, and lead statuses

An enabled condition can be enough to screen someone. Person-level and company-level history are separate. For example, contacting one employee can matter under the company rule without establishing that a different employee was personally contacted.

Selected stage and status rules work independently of the basic conditions. Their meaning depends on the connected CRM and available information. If Distill cannot read a status or its mapping has not been set up, it cannot be assumed to enforce the customer's intended rule.

Distill also distinguishes an existing relationship from activity it created itself. If a campaign creates a CRM contact, that same campaign does not exclude the person under the basic “in CRM” or “previously contacted” checks. Customer status, meetings, open deals, and selected stages can still exclude them. Other campaigns apply the usual checks. Distill also accounts for its own logged sends when reading last-contacted dates, so recording the previous message does not automatically block the next one.

Changing screening settings can start background rechecks. Saving the setting does not mean every affected person has already been re-evaluated. Loosening a CRM rule also does not remove an unrelated Do Not Contact restriction or another hold.

Screening coverage depends on the configured rule, identity match, available information, and sending action. A manual Send Now action has different checks from automated or scheduled initial outreach.

Missing data and failures#

Distill distinguishes between finding a reason to exclude someone, finding no restriction, and not having enough information to decide. “Unknown” is not the same as “not in the CRM.”

Automated sending can wait when a row has a saved CRM error with no earlier complete result, or when Distill cannot determine whether a selected stage rule applies. Other cases of incomplete data or failed refreshes can leave an earlier result in place or allow sending to proceed. A CRM outage does not necessarily pause every campaign. A failed read also does not remove an existing CRM hold.

For a firm person or company exclusion, the project's Do Not Contact controls serve a separate purpose. See Lists for exclusion scope and Campaigns and personalization for sending controls.

Refresh timing and what “connected” proves#

CRM information shown in a list is a saved lookup result, refreshed through background work and supported row or column refreshes. It is not a live query of the entire CRM every time the list is displayed.

Lookups can start when a CRM column is added, when new entries arrive, when an editable row is opened or refreshed, and during campaign refreshes. A completed lookup can trigger a screening check for the affected entry. A view-only row shows saved information without starting the same refresh. Distill can also try to update outdated saved results before relevant automated sending decisions.

These states are different:

  • Connected: Distill has a configured connection. This does not prove that every permission or request is working.
  • Connection test passed: a particular request to the provider succeeded. It does not confirm that all records were imported or every required field is available.
  • Refresh accepted: background work was queued. Its results may still be pending.
  • Updated result: the intended row received a new result. That result can still contain partial information.
  • Screening completed: the configured rule was evaluated for the relevant person and campaign.

Provider limits, waiting background work, missing permissions, and failures affect how current the information is. A CRM edit can take time to appear across the relevant rows.

What Distill writes back to a CRM#

A campaign with a connected CRM column on its source lists can record supported outreach on the matching CRM person's record. The campaign uses the CRM connections on those source lists. It does not copy everything happening in Distill to the CRM.

ActionCurrent behavior
Campaign email, including supported sequence follow-upsCan log the subject, body, sender, recipient, and activity against the CRM person. HubSpot uses email activity; Attio uses a note.
Supported LinkedIn request, withdrawal, or message actionCan log the action as a note for a matched CRM person. Coverage depends on the specific action.
Emailing someone not found in the CRMCan create the contact and then record the email. Supported providers can also find or create the employer company.
LinkedIn activity with no matching CRM personDoes not create a contact the way email can. The activity may therefore have no CRM record to be saved to.

Under the current default logging settings, automatic connection requests, the first automatic LinkedIn message, and withdrawals caused by an expired wait or leaving a campaign are not written to the CRM. Other supported request, withdrawal, and message actions can be logged. The account's logging configuration can change coverage, so CRM activity is a partial record of outreach.

There is no separate per-campaign or per-user switch for this activity logging in the current setup. The CRM columns on the campaign's source lists determine which connections are used. Multiple source lists sharing one connection are not intended to create a separate copy of the activity for each list.

Recording activity in the CRM can fail or be delayed even when the outreach succeeded. The campaign's send history and conversation show what happened beyond the CRM record.

“Two-way integration” refers to the supported reads and activity writes described above. Automatic deal creation, opportunity-stage updates, and copying arbitrary Distill list columns into CRM properties are outside those documented actions.

Changing or removing a connection#

Changing the project's CRM account affects the CRM information used by its lists and campaigns. Fresh results are needed for the replacement account.

Removing the project CRM configuration removes its CRM columns from the project's lists and stops using that project connection. Disconnecting a user's HubSpot authorization is a different action: it makes that stored authorization unavailable and can affect the places that use it. A revoked authorization requires reconnection; repeated refreshes do not restore it.

Neither action means that contacts, companies, or activity already written into the external CRM have been deleted. Disconnecting is also different from requesting deletion of stored information. Removing a connection is not a substitute for pausing a campaign or recording a Do Not Contact restriction.

Webhooks, email, LinkedIn, and calendars#

An inbound list webhook is a private address that receives records for one Distill list. A configured automation in a CRM, form, or event registration system can send the supported fields to that address. Distill then matches and processes the records. If the list already supplies an active campaign, eligible new people can join its audience and proceed under that campaign's sending settings.

For example, a CRM workflow can send a newly added contact to a Distill list webhook. Connecting the CRM alone does not configure this workflow or map its lists to campaign audiences. A successful webhook response confirms receipt, not completed processing or sending. See Lists for supported inputs and private webhook access.

A sender's LinkedIn and email connections support their respective channels. CRM authorization does not authorize either channel. Gmail and dedicated outreach-mailbox setup, account ownership, and required user consent are covered in Using an assistant. Available network data and introduction paths are covered in Networks and Introductions.

A booking link gives a recipient a way to schedule. Supported booking events record the booking, while connected calendar information helps match it to a calendar entry. Missing calendar coverage can make meeting reports incomplete, as explained in Reporting and results.

What a connected assistant can check#

The assistant can read the current user's saved HubSpot setup and provide a browser link for granting access. A supported connection test makes a limited read request to HubSpot and can inspect one specified contact. It does not confirm that the whole CRM has imported, every stage is mapped, or every campaign has the intended screening settings.

The external account owner completes the consent or credential step. Using an assistant explains account access and the broader setup process.

Common questions#

Does connecting our CRM exclude all existing contacts?#

No. The connection supplies information; configured person, company, and stage rules decide which relationships block outreach. An ordinary list named “Customers” is not an exclusion by itself.

Can we avoid companies with open deals but still contact other CRM records?#

Yes, the company open-deal condition is separate from excluding everyone who exists in the CRM. The result depends on the selected rules, readable deal information, and a match to the person's current employer.

Why does Attio show a note but no new last-contacted date?#

Distill records supported campaign activity in Attio as a note. That records the outreach without automatically updating Attio's last-contacted date. HubSpot email activity behaves differently.

Will Distill change our CRM when it sends messages?#

It can. A CRM connection on the campaign's source lists enables supported activity logging. Emailing can create a missing contact and, where supported, the employer's company record. The connection is not read-only.

Why is a CRM record or message missing from Distill?#

Possible reasons include incomplete identifiers, a pending or failed lookup, a missing permission, unsupported activity coverage, or an outdated saved result. A successful connection test does not rule out all of these. Absence from a partial result is not proof that the record or interaction does not exist.

Does changing a CRM stage instantly stop a scheduled message?#

Not necessarily. The relevant rule must be enabled, Distill must have the updated CRM information, and the applicable check must run before sending. Automated and scheduled initial outreach have rechecks, but updates are not guaranteed to take effect instantly. Manual sending has different checks.

Can a form or an external CRM send new contacts into Distill?#

Yes, through a configured automation that sends supported fields to a private Distill list webhook. If that list supplies an active campaign, eligible new people can join its audience. Simply connecting a CRM does not set up this workflow. File imports are another way to bring in records.

Does disconnecting delete everything or stop all outreach?#

No. Disconnecting removes access or settings for that connection. It does not undo information already written to the CRM, request deletion of stored data, or pause all campaigns. Connection controls, campaign status, and exclusions are separate.

All guidesBack to top
Distill product guidesAll pages as text