Search

Personal Links

slack button (do not delete)

How to Integrate Knock with Salesforce

How to Integrate Knock with Salesforce

How to Integrate Knock with Salesforce

The Knock + Salesforce integration connects real-time lead engagement data from Knock directly into your Salesforce CRM, helping sales and marketing teams stay aligned, respond faster, and prioritize the leads most likely to convert.

What You Can Do with the Knock-Salesforce Integration

  • Automatically sync leads from Knock to Salesforce
  • View Slack conversations directly in Salesforce contact records
  • Update contact and company profiles in real time
  • Trigger Salesforce workflows based on Knock data
  • View first-party intent signals and lead actions in Salesforce
  • Prioritize high-intent leads using Knock’s intent scoring
  • View conversational transcript in Salesforce
  • Access lead info instantly inside Slack through CRM cards

90 seconds Knock+ Salesforce Video Tutorial

How to Activate the Knock-Salesforce Integration

You can activate the integration from the Knock App in Slack or directly via the Knock Dashboard.

Option 1: From Slack

  1. Go to the Knock app in your Slack workspace
  2. If you don’t see it, go to Slack’s sidebar:
    • Click Apps → Manage → Browse Apps and search for "Knock"
  3. In the Knock App Home, scroll to the Administration section
  4. Click Start under the Salesforce Integration
  5. Make sure you have admin permissions in Salesforce to complete the connection
image

Option 2: From the Knock Dashboard

  1. Open the Knock Dashboard
  2. Go to the Getting Started or Integrations section
  3. Select Salesforce, then click Connect
  4. Follow the authentication flow
image

Invite Salesforce Admin to the Dashboard

If you are not the admin of Salesforce, click on the Invite button at the top left, and send an invitation to the Salesforce Admin.

image

How Knock Creates Contacts and Companies in Salesforce

This section explains when and how Knock creates contacts and companies in Salesforce, and how you can control which leads are synced.

Contact Creation in Salesforce

  1. By default, Knock creates Accepted leads only in Salesforce. Accepted leads include:
    • Leads assigned to a human representative during a chat
    • Leads who book a meeting using Knock Scheduling
  2. Control which contacts are created in Salesforce
    1. Use the settings to decide when Knock creates contacts in Salesforce. Choose which leads are added as contacts
      1. None - No contacts are added to Salesforce. Commonly used when multiple CRM connections exist and you want to prevent duplicate records.
      2. Engaged - Leads who started a chat or attempted to book a meeting.
      3. Accepted - Leads assigned to a human representative or who booked a meeting.
    2. Filter contacts by intent type - Choose which intent types trigger contact creation:
      1. Buying
      2. Support
      3. Partnership
      4. Job seeker
    3. Control email eligibility - Choose how Knock handles email types when syncing contacts:
      • Only business emails
      • All accepted leads, including personal email addresses
image

Contact and Company Creation in Salesforce

  1. When a lead is accepted, Knock creates a new Salesforce contact with the following standard fields:
    • First Name
    • Last Name
    • Email
    • Company
  2. By default, Knock does not create new companies in Salesforce. When company creation is enabled in settings, Knock creates companies with:
    • Company Name
    • Website
    • Company Owner
    • Knock also creates custom contact and company fields in Salesforce to store enrichment data, such as:

    • Knock Created
    • Knock Connected
    • Knock Enriched
    • Knock Segments

These properties are required for the integration to function correctly.

Additional Knock Data and Field Mapping

All other enrichment data - including intent signals, engagement data, attributes data, and scoring - is not written to Salesforce by default. Knock only writes additional data when it is explicitly mapped.

To store additional Knock data in Salesforce, use the Field Mapping configuration described in the next section. You can configure mapping for:

  1. Contact fields
  2. Company fields

Fields created when a new contact is added

When a lead is accepted, Knock creates a new Salesforce contact with the following standard fields:

  • First Name
  • Last Name
  • Email
  • Company

Knock also creates custom contact fields in Salesforce to store enrichment data, such as:

  • Knock intent score
  • Chat engagement data
  • Meeting status
  • Lead source details

These fields support lead prioritization, workflow automation, and segmentation. Review all contact fields created by Knock here

Company creation in Salesforce

By default, Knock does not create new companies in Salesforce. When company creation is enabled in settings, Knock creates companies with:

  • Company Name
  • Website
  • Company Owner

Knock also creates custom company fields in Salesforce to store enrichment data. Review all company fields created by Knock here

Mapping Knock Fields to Salesforce

Mapping Knock fields to your own Salesforce fields is optional. You may choose to map fields if you want Knock data to:

  • Populate existing Salesforce fields, or
  • Trigger Salesforce workflows that rely on specific fields

Field mapping defines which Salesforce field receives data from each Knock field. Only mapped fields can receive Knock data.

How to Map Knock Fields

To create a field mapping:

  1. Select the Contacts or Companies tab
  2. Choose a field category from the list
  3. Select the Knock field you want to map
  4. From the dropdown, choose the Salesforce field that should receive the Knock data. Only compatible Salesforce field types are available for selection.

How Mapped Fields are Updated

For any field you choose to map, Knock updates the mapped Salesforce field only when:

  • The field is empty, or
  • The Override option is explicitly enabled for that field
  • Unmapped Salesforce fields are never modified.
image

You can map Knock fields only to compatible CRM field types with write permissions:

  • String fields - recommended for most Knock fields
  • Date fields - used only for Knock date-type fields (for example, First Seen)
  • Integer fields - used only for Knock numeric fields (for example, Response Time)

Important: The target CRM field must not belong to the Knock Data field group. All other incompatible fields are automatically filtered out to prevent write errors and ensure reliable field mapping.

Contact and Company Duplication Handling

  • If the contact email already exists in Salesforce, Knock updates that contact - No duplicate contacts will be created
  • If a company domain already exists in Salesforce, Knock updates the existing - No duplicate contacts will be created

How the Override Option Works

The Override option controls whether Knock can replace existing values in a mapped Salesforce field. Override settings are configured per field mapping.

  1. Enable or disable Override - To manage the Override setting:
    1. Map a Knock field to a Salesforce field
    2. Use the Override toggle next to the mapped Salesforce field to turn it on or off
  2. Override behavior
    • Override off - Knock writes a value only if the Salesforce field is empty
    • Override on - Knock writes or updates the value even if the Salesforce field already contains data
  3. Additional details
    • Use the CRM sync monitoring table to review how mapped and overridden fields are written in Salesforce
    • For Knock-specific data (such as chat activity, meeting status, signals, and impact data), we recommend enabling Override to ensure the most up-to-date information is written to Salesforce

Knock Data in Salesforce Deals

Knock adds the following custom fields to the Deal object:

  • Knock: Created Account → true if Knock created the associated company
  • Additional fields can be mapped using Knock’s settings panel

View Knock Insights Inside Salesforce

Knock enriches your Salesforce records with unique insights:

  • Intent Signal Card → Shows what pages or assets the lead engaged with
  • Chat Transcript Card → Shows the full Slack conversation history
  • Slack Jump Link → Lets your team jump directly into the live chat thread from Salesforce

How to add Knock unique insights into Salesforce?

Step 1: Install the Knock Insights Package

 View Knock insights, like intent signals and Slack chat transcripts, directly on the Contact page.

  • Access Salesforce Package installer: Link
  • Select: Install for All Users
  • Select checkbox: grant access to this 3rd party web sites
image

Step 2: Add Knock Insights to Lighting Page

  1. Navigate to Object Manager in Salesforce.
  2. Select Contacts from the list of objects.
  3. Click on Lightning Record Pages in the sidebar.
  4. Click New to create a new Lightning record page.
  5. Choose the Record Page option and click Done.
  6. Assign a label to your new record page (e.g., "Contact Insights Page").
  7. Select the object Contact to associate it with this page.
  8. Drag the ContactIntentSignals component to the desired location on the Contact page layout.
  9. Drag the KnockConversations component to the appropriate location on the same page layout.

image

Knock Outreach: Build and Sync High-Intent Segments to Salesforce

Knock helps you surface and act on high-intent leads with real-time buyer signals. You can build segments and sync them into Salesforce in a few clicks.

Steps to Use Knock Outreach:

  1. Go to the Knock Dashboard → Accounts Tab
  2. Select Knock Segments and reveal leads based on engagement, ICP fit, or behavior
  3. Build a custom segment (e.g., "Fintech Companies showing high intent to purchase")
  4. Sync the segment directly to Salesforce

Knock will enrich the contacts and push them into Salesforce, ready for outreach.

Create a Salesforce View for Your Knock Segment

  1. In Salesforce, go to Add View
  2. Filter by Knock:Segment and select the name of the segment
  3. Use this view for outreach or automation
  4. Trigger workflows based on real-time interest
image

Show Salesforce Data in Knock

You can choose which Salesforce fields to stream into Knock to give your team more context and control during lead interactions.

What You Can Do:

  • See Salesforce data in Slack notifications for leads who message your team via Knock
  • Use Salesforce fields in Knock routing rules to assign leads based on CRM data
  • Filter and segment leads in the Knock Dashboard using synced Salesforce fields

How to Enable Salesforce Data in Knock

  1. Open the Knock Dashboard
  2. Go to the Salesforce Integration section
  3. Click on the tab: View Salesforce Data Inside Knock
  4. You’ll see a list of your Salesforce fields
  5. Select the fields you want Knock to extract and display

These selected fields will now appear in Slack lead notifications, be available for routing conditions, and can be used to build dynamic segments in your Knock account.

image

Contact Custom Fields Added by Knock

Knock Contact Enrich

Field
Field Type
Description
Knock: Role
String text
The lead’s job title or function at their company. Example: VP Marketing, SDR.
Knock: LinkedIn Profile
URL
Direct link to the lead’s LinkedIn profile.
Knock: Profile Image URL
URL
Link to the lead’s profile photo.
Knock: Country
String text
The country where the lead is located. Prefer ISO-3166 country names or codes.
Knock: Phone
String text
Lead’s phone number

Attribution

Field
Field Type
Description
Knock: Origin Channel
String text
Top-level channel that started the visit. Examples: Direct, Organic Search, Paid Search, Paid Social, Referral, Email.
Knock: Origin Source
String text
Specific source within the channel. Examples: Google, LinkedIn, Newsletter, Partner site.
Knock: Origin Campaign
String text
First touch campaign identifier. From UTMs or Knock tracking.
Knock: Origin Content
String text
First touch content or creative identifier. From UTMs or the originating asset.
Knock: Referrer URL
URL
Full URL the visitor came from.
Knock: Entry Page
URL
First page the visitor viewed on your site.
Knock: UTM Term
String text
Value of utm_term.
Knock: UTM ID
String text
Value of utm_id.
Knock: GCLID (Google)
String text
Google Ads click identifier captured on arrival.
Knock: FBCLID (Facebook)
String text
Meta click identifier captured on arrival.
Knock: MSCLKID (Microsoft)
String text
Microsoft Ads click identifier captured on arrival.
Knock: LI_FAT_ID (LinkedIn)
String text
Linkedin click identifier captured on arrival.

Knock Signals

Field
Field Type
Description
Knock: Intent Score
String text
Knock’s score for this contact’s buying intent. High means strong intent.
Knock: Intent Signals
String text
Actions that contributed to the score. Examples: Checked Pricing, Watched Demo, Read Reviews.
Knock: Segments
String text
All Knock segments currently matching this contact. Examples: Save the lead.
Knock: Intent type
String text
The intent of the lead: Buying, Partnership, Job Seeker, Support, Spam. This is only for contacts who sent a message though Knock.

Chat

Field
Field Type
Description
Knock: First Touchpoint
String text
Chat link name. Examples: Website Footer
Knock: Touchpoint URL
String Text
Chat link URL
Knock: Chat Owner
User lookup
The email of the rep who assigned as the owner of this contact chat
Knock: Responding Rep
User lookup
The email of the rep who first responds to the contact
Knock: Rep Responding Time
Number (minutes)
Minutes between the rep being added to the chat and their first reply.
Knock: Chat Status
String text
The lead progress in knock engagement funnel
Knock: Total Messages Sent
Number
Total messages sent by the lead

Knock Meeting

Field
Field Type
Description
Knock: First Meeting Booked
Date/Time
Timestamp of the first meeting scheduled via Knock for this contact.
Knock: Meeting Owner
User lookup
The teammate who owns the meeting.
Knock: Meeting Type
String text
Category of the meeting. Examples: Intro, Discovery, Demo, Technical, Pricing, Follow-up.
Knock: Booked Meeting Time
Date/Time
The time of the last meeting booked
Knock: Last Meeting Booked
Date/Time
The time of the last meeting booked
Knock: Number of Meetings
String text
Total number of meeting booked by this contact

Knock Impact

Field
Field Type
Description
Knock: First Seen
Date
The first time the contact was detected by Knock
Knock: Last Seen
Date
The last time the contact was detected by Knock
Knock: Created
String text
Value is True if the contact was created by Knock
Knock: Connected
String text
Value is True if the contact was connected though Knock

Company Custom Fields Added by Knock

Knock Company Enrich

Field
Field Type
Description
Knock: Headquarter
String text
City, state/province, and country of the company’s main office.
Knock: Description
String text
A short description about the company
Knock: Size
String text
Number of employees
Knock: Industry
String text
Primary industry classification for the company.
Knock: Status
String text
Ownership status. Examples: Private, Public, Acquired.
Knock: Founded Date
Date
The company’s official founding date.
Knock: Last Funding
String text
Most recent funding round type. Examples: Seed, Series A, Series B, Series C, Debt, Grant.
Knock: Total Funding
Number
Cumulative capital raised to date.
Knock: Annual Revenue
Number
Latest reported annual revenue

Knock Signals

Field
Field Type
Description
Knock: Intent Score
Number
Measures the company's likelihood of purchasing your solution (High, Medium, Low)
Knock: Segments
String text
All Knock segments currently matching this company. Examples: Save the lead.

Knock Impact

Field
Field Type
Description
Knock: Created
String text
Value is Yes if the contact was created by Knock
Knock: Connected
String text
Value is Yes if the contact was connected though Knock