Changelog

Added: Custom Colors for Grouped Metrics

Custom metrics now support per-group color selection, so teams can keep colors consistent across dashboards and reports.

Previously, custom metrics used a fixed default palette. A group could show up as blue on one chart and green on another, making it harder to read dashboards at a glance or match reports to a brand's colors.

What's included

• Color picker per group: Each group in a metric's series can now be assigned its own color directly from the metric configuration.
• Support for donut, stacked, and distribution charts: Color selection works on donut charts, stacked bar charts, stacked column charts, and distribution charts.
• Colors saved with the metric: Once a color is set, it's stored with the metric and applied automatically everywhere that metric is used, across dashboards and reports.
• Reset to default: Any group color can be reset back to the default palette at any time, individually or all at once.

How it works

Open a metric's configuration and select Group By to enable grouping. From there, click Edit to access group colors. Each group can be set using the color palette or one of the suggested colors. Changes save at the metric level, so the same group keeps the same color on every chart where that metric appears.

Why it matters

• Consistent dashboards: The same color represents the same group everywhere, so teams don't have to relearn what each color means on every chart.
• On-brand reporting: Reports can be color-matched to a company's brand before they're shared with clients or stakeholders.

Setup

No setup is required. Custom colors are available now in the metric configuration for any grouped metric.

Notes

• Existing metrics are unaffected: Metrics keep the default palette until custom colors are set.
• Grouping is required: Color selection only applies to charts that have a Group By configured.
• Single-event charts only: Custom colors currently work on charts built from a single event. Multi-event charts are not yet supported.

Added: Duplicate Workflows

Whippy added the ability to duplicate any existing workflow directly from the workflow list, so teams can build new automations from a working template instead of starting from scratch.

What's included

• A duplicate action available directly from the workflow list
• Full copy of the original workflow's configuration, including steps, actions, and conditions
• The duplicated workflow appears in the list as a separate, editable workflow

How it works

From the workflows list, select the workflow you want to copy and choose duplicate. Whippy creates an exact copy of that workflow, including all existing steps, actions, and conditions. The new workflow is added to the list immediately, and you can rename it and update only the details that need to change for its new use case.

Why it matters

Building a complex workflow from zero takes time, especially when a similar one already exists. Duplication removes that repetition. Teams can reuse a proven workflow structure as a starting point and adjust only what's different, instead of rebuilding every step, action, and condition by hand.

Common use cases include:

• Duplicating a complex workflow and adjusting a few details for a new use case
• Reusing the same workflow structure across different campaigns or audiences
• Creating variations of an existing workflow without rebuilding it from the ground up

Notes

Duplicated workflows are independent of the original. Changes made to one do not affect the other.

Added: Crelate Contact Sync Auto-Links by Phone

Whippy added automatic phone number matching for Crelate contacts that are not yet linked, so messages no longer wait on the next scheduled contact sync to reach Crelate.

What's included

• Added automatic phone number matching for Crelate contacts without an existing Crelate link
• Enabled real-time contact linking during message sync, instead of waiting for the next contact sync cycle
• Enabled immediate message delivery to Crelate once a match is found, within the same sync cycle
• Extended the existing contact linking logic already used for Aqore and TempWorks to include Crelate

How it works

During each Crelate message sync, Whippy checks whether the contact already has a linked Crelate record. If the contact is not linked, Whippy searches Crelate for a matching contact using the phone number. When a match is found, Whippy retrieves the full contact record, saves the mapping, and pushes the message to Crelate in that same sync cycle. If no match is found, the message is held until the next linking attempt.

Why it matters

Crelate contact data syncs every 6 hours, while message sync runs every 10 minutes. Previously, Whippy could only push a message to Crelate if the contact record already had a confirmed link. A new phone number, an updated phone number, or a contact that had not yet synced from Crelate meant the message sat unsynced until the next contact sync caught up, which could take up to 6 hours.

This update removed that bottleneck. Messages tied to unlinked contacts now sync as soon as a phone number match is found, without waiting on the contact sync schedule. This is especially useful for recruiting and staffing teams using Whippy alongside Crelate, where fast, accurate message delivery to the ATS directly affects candidate response times and pipeline visibility.

Notes

This change applies to message sync only. Contact sync schedules and full sync jobs are unaffected. No configuration is required. The update applies automatically to all active Crelate integrations.

Added: Undo Support for Workflow Step Creation and Deletion

Whippy added Undo support to the Workflow Builder, letting users instantly restore up to 3 consecutive steps or branches after an accidental deletion or creation.

What's Included

• Undo button in the editor header. A new Undo control is available directly in the Workflow Builder header while editing a workflow.
• Coverage for creation and deletion. Undo reverts both the deletion of one or more steps and the creation of new steps, including entire branches within a Split Path.
• Multi-step undo. Undo supports up to 3 consecutive changes, allowing users to revert more than one accidental deletion or creation in a row.
• State restoration. The Workflow Builder preserves previous workflow states, so reverting a change restores deleted steps or removes newly created ones without requiring a manual rebuild.

How It Works

While editing a workflow, step creation or deletion can be reversed with a single click:

1. Open a workflow in edit mode.
2. Create or delete one or more workflow steps.
3. Click Undo in the Workflow Builder header to revert the most recent change. Undo supports up to 3 consecutive clicks, reverting multiple changes in sequence.
4. The workflow immediately returns to its previous state, restoring deleted steps or reverting newly created ones.

Why It Matters

Workflow building involves frequent experimentation, and a single deletion inside a Split Path can remove an entire branch of downstream steps. Rebuilding that logic manually costs time and increases the risk of missing a step. Undo removes that risk, even across multiple consecutive changes. Teams can test changes, delete steps, and adjust branches in the Whippy Workflow Builder without worrying about losing work.

Setup

No setup is required. The Undo button is available by default in the Workflow Builder header for all workflows in edit mode.