Field mapping controls what Knock2 writes out to your CRM. The opposite direction — what Knock2 reads in from your CRM — is configured in the Read from [CRM] section of the same screen. This works for Salesforce, HubSpot, and Attio.
Read data flows one way: from your CRM into Knock2. These fields are read-only inside Knock2 — Knock2 never writes back to them.
Where to find it
Go to Settings → Integrations.
Open Salesforce, HubSpot, or Attio.
Scroll to Read from [CRM] (the Read tab of Field Mapping), below the Write section.
Deal & opportunity fields (automatic)
Knock2 automatically reads your open deal/opportunity data and attaches it to the matching account, so you can see live pipeline context next to your identified visitors. These mappings are fixed and read-only:
HubSpot (Deals)
Deal name → Deal name
Deal stage → Deal stage
Amount → Deal value
Close date → Close date
Deal owner → Deal owner
Company owner → Company owner
Salesforce (Opportunities)
Opportunity name → Deal name
Opportunity stage → Deal stage
Amount → Deal value
Close date → Close date
Opportunity owner → Deal owner
Account owner → Account owner
Attio (Deals)
Deal name → Deal name
Stage → Deal stage
Value → Deal value
Close date → Close date
Deal owner → Deal owner
Company owner → Company owner
There is nothing to configure here — these fields appear automatically once your CRM is connected. Knock2 matches a HubSpot Company or Salesforce Account by domain, and matches an Attio Company by domain as well.
Custom read columns
Beyond the standard deal fields, you can pull additional fields off your HubSpot Company, Salesforce Account, or Attio Company records into Knock2 — for example a renewal date, account tier, or any custom property your team uses. Each one becomes a custom read column on your account data in Knock2.
To add a custom read column:
In the Read from [CRM] section, under Custom fields, click Add field.
Pick the CRM field to read from. Both standard and custom CRM properties (or Attio attributes) are available, grouped accordingly.
Enter a Knock2 label — the name this column shows under in Knock2.
Choose a type: Text, Number, Date, or Boolean. Knock2 pre-fills this based on the CRM property, but you can change it.
Click Save.
Limits & behavior
Up to 3 custom read columns per workspace. This limit is shared across HubSpot, Salesforce, and Attio combined.
To remove a column, click the trash icon next to it.
If a mapped CRM field is later deleted or renamed in your CRM, the column is flagged Unavailable. Remove it or remap it to a field that still exists.
Viewing your custom columns in Knock2
After you add a custom read column, it may be hidden by default in the Contacts and Accounts tabs. If you do not see your data right away, turn the column on:
Open the Contacts or Accounts tab.
Click the three-dot menu in the top-right corner of the table and select Columns.
Find your new column and toggle it on. You can also drag to reorder and resize it.
Column preferences are saved per user, so each teammate controls their own view. See Using the Contacts Tab and Using the Accounts Tab for more.
Who can edit
Like field mappings, read columns are managed by the teammate who connected the CRM. Other teammates see them as read-only, with a note showing who manages them.