Skip to main content

Customizing CRM Field Mappings (Salesforce & HubSpot)

Control exactly which Knock2 fields get written to each Salesforce and HubSpot object, and how existing values are handled.

Written by John DiLoreto

Knock2 lets you control exactly which Knock2 fields are written to each object in your CRM — and how existing values are treated — through field mapping. This works for both Salesforce and HubSpot.

Field mapping applies whenever Knock2 writes to your CRM, whether the record is created manually from the dashboard or automatically by a play or workflow.


Where to find it

  1. Go to Settings → Integrations.

  2. Open Salesforce or HubSpot.

  3. Under Write to [CRM], choose the object tab you want to configure.

Objects you can map:

  • Salesforce: Lead, Contact, Account

  • HubSpot: Contact, Company


How a mapping works

Each row maps one Knock2 source field (on the left) to one CRM field (on the right). The source field is fixed; you choose which CRM field it writes to, how it should overwrite, and how to handle multi-value fields.

  • To change a target, pick a different CRM field from the dropdown — including your own custom fields.

  • To stop writing a field, leave its CRM target blank (unmapped).


Overwrite rules

Each mapped field has an overwrite rule that controls what happens when the CRM record already has a value:

  • Always — write the Knock2 value every time the destination runs.

  • If empty — only fill the field when it is currently blank in the CRM (never overwrite a value your team entered).

  • Never — leave this field alone.


Multi-value fields

Some Knock2 fields (for example, company phone numbers) can contain several values. For these you can choose how the value is written:

  • First value — write only the first value.

  • Join — combine all values into a comma-separated list.

  • Count — write the number of values.


Defaults

Field mapping works out of the box — Knock2 ships sensible defaults for every object, so you only need to visit this screen if you want to change what gets written. If your Salesforce org uses State/Country picklists, Knock2 maps to the picklist codes automatically.


Who can edit mappings

Field mappings are managed by the teammate who connected the CRM. Other teammates see the mappings as read-only, with a note showing who manages them.


Related articles

Did this answer your question?