Skip to main content
If you’ve connected Qwoty to a CRM (HubSpot, Salesforce, Pipedrive), every custom field on a manageable object can be mapped to a CRM field. Mapping decides which direction data flows and which CRM field receives or sends the value.
CRM mapping requires an active CRM integration. Connect your CRM first via Settings → Developers → Integration → CRM name, then return to map custom fields.

​
Where mapping lives

Custom field mapping is configured per-CRM, in the integration settings:
1

Open Settings

Click Settings in the left sidebar.
2

Navigate to your CRM

Under the Developers section, click Integration, then click your connected CRM (HubSpot, Salesforce, Pipedrive, or others).
3

Find the Custom fields section

Scroll to the custom fields mapping area. Each Qwoty custom field on the synced object is listed, prefixed with Custom: to distinguish from system fields.

​
Sync directions

For each custom field, you choose one of three sync directions:
When in doubt, start with CRM → Qwoty (one-way pull). It’s the safest setting because Qwoty never overwrites CRM data. Move to Bidirectional only when your team wants to edit the value in both apps without thinking about it.

​
Selecting the CRM field

Each custom field row has two dropdowns:
  • Direction dropdown — pick Bidirectional, CRM → Qwoty, or Qwoty → CRM
  • Select CRM field — pick the matching field on the CRM side (only fields of compatible types are listed)
Compatible types follow these rules:
If the dropdown is empty or doesn’t show the field you expect, check that the CRM field exists, that its type is compatible, and that the integration’s permissions include read/write access to the field.

​
Sync frequency and timing

How often Qwoty syncs depends on the integration:
  • Real-time webhooks for most modern CRMs (HubSpot, Salesforce) — changes propagate within seconds
  • Periodic polling as a fallback when webhooks aren’t available or fail
After saving a mapping, the next sync cycle picks up the new configuration. Existing records start receiving (or sending) values according to the new direction at the next sync.

​
When the CRM field is missing values

If a CRM record doesn’t have a value for the mapped field, Qwoty receives null and stores nothing — the custom field shows empty on the record. The reverse is also true: if Qwoty has no value and the direction includes → CRM, the CRM field is set to its empty state.

​
Save changes

Click Save changes at the bottom of the mapping section to apply your configuration. The new mappings are picked up at the next sync. You can adjust mappings any time without breaking historical data — past values stay intact.

​
Common mapping patterns

Not every custom field needs a mapping. Leave the Select CRM field dropdown empty to keep the field local to Qwoty.

Field properties

Mandatory, Editable, Display — properties that work alongside CRM mapping.

Field types

Type compatibility between Qwoty and CRM fields.

CRM integration

Connect HubSpot, Salesforce, or Pipedrive.

Create a Customer custom field

The most common case for CRM-synced custom fields.