Why it matters
Many Whippy workspaces rely on data synced from another system. Knowing which data is owned by an integration helps teams troubleshoot missing records, avoid manual edits in the wrong place, and keep messaging workflows aligned with source-of-truth data.
Key Concepts
Integrated contact: A contact created or updated from an external system or integration.
External ID: An identifier used to match a Whippy contact or object record with the source system.
Synced object data: Object records imported or updated from another system and shown under Contacts > Objects.
Integration-owned structure: Objects or properties where some configuration may be controlled by the connected system.
Sync timing: The delay or schedule between a source-system change and the matching Whippy update.
Step-by-Step: Review synced data
Open Contacts and search for the contact or customer record.
Review the contact's external ID, phone, email, tags, lists, and communication preferences.
Open Contacts > Objects to review synced object types and records.
Open the relevant object record and check whether it is associated with the expected contact.
Open Settings > Objects to confirm the object definition and associations when needed.
Open Settings > Channel mappings if synced object values are used to select sending channels.
Check the connected system when Whippy shows stale or missing synced data.
Tips and Best Practices
Treat the external system as the source of truth when an integration owns the data.
Use external IDs consistently so contacts and object records can match reliably.
Document which fields are safe to edit in Whippy and which should be edited in the source system.
Mark this article for product review when integration-specific sync behavior needs screenshots or exact timing.
Troubleshooting
Issue | Possible Cause | Fix |
A synced customer is missing | The source record has not synced, is filtered out, or lacks a matching identifier | Check the source system, external ID, and integration sync status |
Synced data looks outdated | The integration has not completed its next sync or the source value has not changed | Confirm the source value and wait for or trigger the expected sync process |
A user cannot edit synced fields | The object or field may be integration-owned | Update the data in the source system or ask an admin to review the integration setup |