Field Mapping
What this means
Section titled “What this means”A field mapping connects a field in your CRM (say, a deal’s amount in Pipedrive) to the matching field in Playwise HQ. Mappings are what let a webhook event translate into the right update: when a mapped CRM field changes, the corresponding Playwise field changes with it.
A mapping-related webhook error means an event arrived but a CRM field couldn’t be matched to a Playwise field. Two common variants:
- Invalid field configuration — your sync settings reference a field this CRM platform doesn’t actually offer (often after a field was renamed or deleted in the CRM).
- Required field missing — a field that must have a source of truth configured doesn’t have one yet.
Why it happens
Section titled “Why it happens”- Standard fields are mapped automatically when you connect, but custom fields need to be mapped explicitly — an unmapped custom field can’t sync.
- Someone changed or removed a field in the CRM after the mapping was created.
- Sync preferences were saved with a field the platform doesn’t support.
How to fix it
Section titled “How to fix it”- Open Settings → Integrations, choose your integration, and go to the Sync Preferences tab.
- Review the fields listed there against what actually exists in your CRM. Use View Available Fields where offered to see what the platform supports.
- Remove or re-point any mapping that references a missing field, and give required fields a source of truth.
- For custom fields, complete the custom-field mapping step in the integration’s configuration — the mapping is created when you configure the custom field, not before.
Nothing is lost while a mapping is broken: unaffected fields keep syncing, and once fixed, the next change to a record brings the field up to date.
Related: merge strategies control which side wins for each mapped field.
Still stuck?
Section titled “Still stuck?”If a field refuses to map or the error persists after review, contact support.