Changelog

Changed: Improved Call Sync Accuracy to External Systems

Call activity records now sync only after a call is fully completed, ensuring external systems always receive finalized data, including summaries, transcripts, and metadata.

What's Included

• Call delivery status validation added before syncing activity to the database
• Sync now triggers only on completed call states: call_completed and call_completed.agent_hangup
• Active or in-progress calls are excluded from the sync queue until completion
• Applies to all connected external integrations, including Avionté and Aqore

How It Works

Previously, Whippy pushed call activity records to external systems as soon as a call was logged, even while still in progress. Since call summaries, transcripts, and metadata are only generated after a call ends, external systems received incomplete records containing little more than a link back to the Whippy conversation.

Now, Whippy validates the call delivery status before saving or syncing any activity. A record only enters the sync database once the call reaches a completed state. At that point, the full record, including the call summary, transcript, and metadata, is available and synced in a single, complete entry.

Why It Matters

Incomplete call records create noise in external systems: missing context, placeholder links instead of summaries, and data inconsistencies that require manual cleanup.

This update ensures that every synced record is ready to use, with the full context your team and your integrations need to act on it. Whether you're tracking outreach activity in a staffing platform or logging calls in a CRM, the data that arrives is complete and accurate from the first sync.

Notes

• No configuration changes are required. The updated sync behavior is applied automatically.
• Calls that ended before this update was released are not retroactively resynced.
• If your integration previously relied on receiving in-progress call records, those will no longer appear until the call reaches a completed state.

Added: TempWorks Workflows Integration

Whippy now connects directly to TempWorks from the workflow builder, letting staffing teams automate operations on live TempWorks data without custom middleware or manual HTTP requests.

What's included

• Search & lookup: Search employees, contacts, customers, job orders, and assignments using standard filters, and advanced search queries. Load datalists for branches, service reps, statuses, and more.
• Create & update records: Create and update employees, contacts, job orders, and assignments. Post messages, tasks, documents, candidates, onboarding steps, and financial records. Supports document and resume uploads.
• Webhook triggers: Subscribe to real-time TempWorks events including new employees, job order status changes, new contact messages, document uploads, custom property changes, and more.

How it works

The TempWorks app is available directly inside the Whippy workflow builder. Once connected, you can add TempWorks actions and triggers to any workflow the same way you would with any other app.

Authentication requires only your TempWorks tenant and product identifiers (ACR values). Your credentials are stored encrypted and exchanged for a secure access token on each request.

Example workflow: A workflow triggers when a new contact message arrives in TempWorks. A condition checks the message action type. If it matches Client inquiry, the workflow sends a follow-up email via Whippy messaging and updates the contact's status in TempWorks. If it doesn't match, the workflow ends with no side effects.

Why it matters

Staffing operations run on TempWorks. Until now, connecting those records to automated communication and downstream processes required custom-built middleware or one-off API calls.

This integration makes TempWorks a first-class part of Whippy workflows, so teams can build end-to-end automations that read, write, and react to TempWorks data in real time, without engineering overhead.

Setup

1. Open the Whippy workflow builder and add a new workflow or edit an existing one.
2. Search for TempWorks in the app list.
3. Connect using your TempWorks ACR credentials (tenant:… / pid:…).
4. Add TempWorks trigger or action steps to your workflow.

Notes

• The integration covers the TempWorks Open API and Webhooks API.
• Each customer authenticates with their own credentials. No shared access between accounts.

Added: Apollo.io Workflows Integration

Added a native Apollo.io integration inside Whippy Workflows, so teams can search, enrich, create, and update Apollo contacts and organizations directly from any automated workflow, no manual data transfer required.

What's included

• Search for people: find prospects by job title, seniority, location, or company. People Search returns role and company data (name, title, company, LinkedIn), it does not return emails or phone numbers. To retrieve contact details, follow this step with an Enrich Person action.
• Search for organizations: look up target companies and accounts.
• Get contact details: retrieve full contact data for contacts that already exist in your Apollo account using their unique Apollo contact ID. This action only works for contacts your team has added, it does not search Apollo's full database.
• Enrich person records: fill in missing contact data using an email, name + company, LinkedIn URL, or company domain. A name alone may not return a reliable match, combine it with a company name or email when possible, or run a Search People step first to get the right person before enriching.
• Create contacts: add new leads directly into Apollo from a workflow step.
• Update contacts: refresh existing Apollo records to keep sales data accurate.

How it works

The Apollo app appears inside Whippy Workflows alongside other native integrations. Each action calls the Apollo API directly using your own Apollo API key, data flows between tools automatically as part of any workflow you configure. Automated triggers are not included in this release; actions only.

Why it matters

Teams that rely on Apollo for outbound sales and prospecting previously had to move data manually between Apollo and Whippy. This integration removes that step: lead enrichment, contact creation, and CRM updates now run automatically inside your existing workflow automation, keeping contact data current without switching tools or copying data between platforms.

Setup

1. Go to Workflows and create or open a workflow.
2. Add a step (+) and select Apollo from the app list.
3. Click Sign in and enter your Apollo API key. You can create or find your key at Create API Keys.
4. Select your action event and configure the step.

Notes

• API credit usage: Credit usage applies to Search Organizations and Enrich Person only, the other four actions (Search People, Get Contact, Create Contact, Update Contact) do not consume Apollo credits. Enrich Person may use additional credits when revealing personal emails or phone numbers. If either action fails or returns no data, check your available Apollo credits and confirm your API key is active.
• API key level: Search People, Search Organizations, and Get Contact require a master-level Apollo API key. A standard key will cause those three actions to fail.

Added: Recording Duration on the All Calls Page

Recording Duration is now visible on the All Calls page, showing the exact length of playable audio for every call and voicemail.

What's Included

• Recording Duration displayed next to the audio playback button for all calls and voicemails
• Visible alongside the existing Call Duration field for direct comparison

How It Works

Each call record now shows two distinct time values:

These values will often differ. A call may show a Call Duration of 1m 01s with a Recording Duration of only 3s, because the caller navigated IVR menus before the voicemail recording started, or recording was initiated partway through the call.

Why It Matters

Call Duration alone doesn't tell you how much audio is actually available to review. Recording Duration lets support and QA teams prioritize reviews by real audio length and spot recording gaps without opening each file individually.

Notes

• Differences between Call Duration and Recording Duration are expected behavior, not an error
• If Recording Duration consistently appears shorter than expected, review your IVR configuration or recording trigger settings in your Whippy account