Skip to main content

Understanding Objects in Whippy

How to view, configure, and use custom objects to power personalization and automation in Whippy.

Written by Maria Cairns

Why it matters

Objects hold structured data connected to your contacts, such as orders, appointments, jobs, assignments, or candidates. This data is used to personalize messages and drive automations based on real-world actions and statuses.

Objects can be managed directly in Whippy or synced from external systems such as TempWorks or Avionté. Understanding where an object is managed is important because integration-managed objects cannot be edited within Whippy.

Key Concepts

Objects: Custom data structures related to contacts or related records (for example, orders, appointments, jobs, assignments, candidates, or locations). Each object contains one or more properties (fields).

Whippy-Managed Objects: Objects created directly within Whippy. These objects can be edited, including their properties, associations, and settings.

Integration-Managed Objects: Objects created and managed by integrations such as TempWorks, Avionté, or other connected systems. These objects are controlled by the source system and cannot be edited in Whippy.

Integration Indicators: Objects created by integrations display the integration's logo on the object card. This helps identify which system owns the object definition.

Relationship to Contacts: Objects are usually tied directly to a contact. They can also be connected indirectly, for example via an external ID (a job record links to an assignment, which links to a candidate whose ID matches the contact's external_id).

Automation and Personalization: Object fields can be used to personalize messages and drive automations and campaigns based on real-world events and statuses.

Creation and Population: Most objects and their data are created programmatically through integrations, AI extraction, or the public API. Users can define object structures in the UI but cannot manually create or populate individual object records.

Custom Object Schema: The definition of an object and its properties, including property names, types, default values, and whether properties are required or searchable.

Channel Mappings: Settings that map object properties to specific channels so that certain values can influence channel behavior.

AI Extraction: You can configure your AI agent to extract custom data objects from calls or messages with a contact and populate your object model.

Step-by-Step: Viewing and Configuring Custom Objects

1. View Object Data

  1. Go to Contacts in the main navigation.

  2. If your workspace has custom objects, you will see Objects listed underneath All Contacts.

  3. Click Objects to view all object records available to your organization.

2. Explore Objects and Download CSVs

  1. Review the table of objects and their fields.

  2. Use filters to narrow down objects by specific field values.

  3. Adjust visible fields to choose which columns appear in the table.

  4. Sort objects by supported fields as needed.

  5. Download a CSV of all objects or filtered objects using the available export option.

3. Review Object Definitions

  1. Go to Settings.

  2. Under the Organization section, select Objects.

  3. Review the list of custom object types available in your workspace.

  4. Look for an integration logo on each object card.

  5. Objects displaying an integration logo are managed by the connected system and cannot be edited in Whippy.

4. Edit an Existing Object Definition*

Only Whippy-managed objects can be edited. Objects managed by integrations such as TempWorks, Avionté, or other connected systems cannot be modified in Whippy.

  1. Navigate to Settings → Objects.

  2. Locate the object you want to edit.

  3. Check whether the object displays an integration logo.

  4. If an integration logo is present, the object is managed externally and cannot be edited in Whippy.

  5. If no integration logo is present, click the three horizontal dots beside the object and select Edit.

  6. Review the existing properties, associations, and settings.

  7. Adjust the sort order if needed.

  8. Configure associations by selecting:

    • Source custom property

    • Target custom object

    • Target custom property

    • Association type

  9. Click Add another association to define additional relationships if needed.

  10. Save your changes.

5. Create a New Property on an Object

  1. Open a Whippy-managed object.

  2. Click Add property.

  3. Enter a Property name (minimum three characters).

  4. Select a Property type:

    • Text

    • Number

    • Float

    • Boolean

    • Date

    • List

    • Map

  5. Set a default value if applicable.

  6. Enable Required if the property must always contain a value.

  7. Enable Search visibility if the property should be searchable.

  8. Click Add property.

6. Configure Channel Mappings for Objects

  1. Navigate to Settings → Channel mappings.

  2. Review existing mappings, including:

    • Mapping name

    • Custom data type

    • Custom property

    • Created and updated timestamps

  3. Click Add channel mapping to create a new mapping.

  4. Use the action menu beside an existing mapping to edit or delete it.

  5. Configure:

    • Channel mapping name

    • Custom data type

    • Custom property

    • Value and channel ID combinations

  6. Save your changes.

Tips and Best Practices

  • Treat objects as the source of truth for structured operational data such as jobs, assignments, appointments, or orders.

  • Look for an integration logo on the object card to identify objects managed by external systems.

  • Manage integration-owned objects in the source platform rather than in Whippy.

  • Create Whippy-managed objects when you need complete control over the object structure and configuration.

  • Use associations to model real relationships (for example, job → assignment → candidate → contact) rather than duplicating data.

  • Mark only relevant properties as searchable to keep search fast and focused.

  • Keep property names consistent and descriptive so they are easy to reuse in segments, automations, and message templates.

  • Work with your integration or engineering team to ensure external systems sync object data correctly into Whippy.

  • Consider configuring your AI agent to extract object data from calls or messages where appropriate.

Troubleshooting

Issue

Possible Cause

Fix

Objects do not appear under Contacts

Workspace has no custom objects configured or synced

Confirm integrations or API syncs are set up and verify object definitions exist in Settings → Objects

Cannot create object records in the UI

Manual record creation is not currently supported

Use integrations, the public API, or AI extraction to populate object data

The Edit option or three-dot menu is missing

The object is managed by an integration such as TempWorks or Avionté

Look for the integration logo on the object card and manage the object in the source system

Changes to an object cannot be saved

The object is managed by an external integration

Update the object configuration in the source platform rather than in Whippy

Segment does not reflect expected object-based conditions

Object relationships or fields are not configured as expected

Review object associations and property values and verify the relationship path between the object and contact

Property not available in search

Search visibility is disabled for the property

Edit the property settings and enable Search visibility

Channel behavior does not match object values

Channel mapping is misconfigured or missing

Review Channel mappings and verify the selected property, values, and channel assignments

Did this answer your question?