Skip to main content

Manage Custom Objects in Settings

Create and manage object definitions, properties, and associations from Settings > Objects.

Written by Maria Cairns

Why it matters

Objects define the structured data that can be linked to contacts and used throughout Whippy. Managing the structure carefully keeps filters, variables, associations, and synced records reliable.

Key Concepts

Object definition: The setup that defines an object type and its properties.

Property: A field on an object, such as a name, ID, status, date, number, boolean value, list, or structured value.

Association: A relationship between two object types or between an object and a Whippy resource.

Whippy association: An association that links object records to Whippy resources such as contacts.

Integration-owned object: An object supplied by an integration where edit and delete actions may be limited.

Step-by-Step: Manage an object definition

  1. Open Settings.

  2. Select Objects.

  3. Review the existing objects.

  4. Select Add object when creating a new object definition.

  5. Enter an object name and save.

  6. Open the object to add or update properties.

  7. Configure associations when object records need to connect to contacts or other objects.

  8. Return to Contacts > Objects to view records for the object.

Tips and Best Practices

  • Use clear object and property names because users will see them in filters and variables.

  • Create associations before relying on object data for contact-level personalization.

  • Avoid changing integration-owned objects unless the integration behavior is understood.

  • Review Channel mappings when object values determine the sending channel for sequences.

Troubleshooting

Issue

Possible Cause

Fix

The Add object action is unavailable

The user may not have permission to manage objects

Review the user's role and admin access

An object does not show records in Contacts > Objects

The definition exists but no records have been synced or created

Check the data source, integration, or import process for object records

A property cannot be changed

The property may be integration-owned or used by existing records and workflows

Review the connected integration and downstream usage before changing it

Did this answer your question?