Changelog

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

Added: Schedule AI Agent Calls and Chat Sessions

Whippy added outbound call scheduling and timed chat session support to AI Agent automations, tools, the Inbox, and the public API, giving teams full control over when AI-driven outreach happens.

What's Included

• Start Call action: Outbound AI calls are now available as an automation action, with immediate or scheduled delivery.
• Scheduled Start Chat action: The existing Start Chat action now supports a future start time, so AI Agent chat sessions no longer have to begin immediately.
• Dynamic scheduling via Execute Actions tool: AI Agents can schedule follow-up calls or chat sessions mid-conversation, in real time.
• Inbox scheduling for calls and chats: Users can manually schedule calls and chat sessions from the Inbox, consistent with how message scheduling already works.
• API support via schedule_at: The public V1 start_call and start_chat endpoints now accept a schedule_at parameter for external scheduling from any connected system.

How It Works

From Automations
Add a Start Call or Start Chat action anywhere actions are supported. Choose whether it triggers immediately or at a scheduled time. No separate timing logic required.

From the Inbox
Select a contact, choose Start Call or Start Chat, and pick a delivery time, the same flow used to schedule messages today.

Via AI Agent (Execute Actions tool)
During a live call or chat, the AI Agent can schedule the next touchpoint on its own. For example: if a candidate asks to continue the conversation tomorrow, the agent books that session before the current one ends.

Via API
Pass schedule_at as an ISO 8601 timestamp in the start_call or start_chat request body. No external scheduling service needed.

Why It Matters

Before this update, outbound AI calls weren't available as an automation action, and every AI Agent session had to start immediately. That forced teams to build timing logic outside Whippy or manually trigger outreach at the right moment.

Now, recruiting, sales, and support teams can schedule AI-driven calls and chats the same way they already schedule messages, reducing manual intervention, eliminating external orchestration overhead, and letting AI Agents handle follow-up timing autonomously during live conversations.

Setup

No additional configuration is required for Inbox scheduling or automation actions. To use prompt-based scheduling inside the Execute Actions tool, make sure the AI Agent's prompt includes the current time variable, for example, {{current_time_America/New_York}}, so the agent knows the current time when scheduling. Refer to your AI Agent prompt settings for details.

Notes

• Prompt-based scheduling for Start Call and Start Chat is only available inside the execute_actions tool.
• Scheduled calls may start slightly after the selected time during high-traffic periods. Treat the scheduled time as a target, not a guaranteed exact timestamp.
• Context sharing between AI Agent calls and chat sessions is being improved in a future release.