Changelog

Added: Notion Workflow Integration

You can now read and write Notion pages, databases, and files inside Whippy workflows. The first release ships 40 actions and 32 webhook triggers, with no custom API calls or manual OAuth setup.

What's included

• Pages and content:
  • Search, get, create, and update pages.
  • Update database properties with Update Page, and update the page body with Update Page Markdown. They are separate steps, so you map structured fields and narrative content to the right place.
  • Append or edit blocks, and move or trash pages.
• Databases and data sources:
  • Query rows, create entries, and read or update schemas.
  • Work with databases, views, and templates.
• Files:
  • Upload and Attach File takes a file from an earlier step, such as an Email Parser attachment, and lands it on a page as a real attachment, not a broken link.
• Comments and users:
  • List, create, update, and delete comments, and look up workspace users.
• Triggers (32):
  • Fire a workflow on events such as page created, updated, deleted, or moved, plus content changes, new comments, and new database entries.

How it works

Connect your workspace once through OAuth, then drop a Notion step into any workflow, pick an action, and map fields from the previous step in the same builder you use for messaging and agents. You choose exactly which pages and databases the connection can access.

Why it matters

Teams keep their source of truth in Notion: runbooks, weekly updates, customer notes, project trackers. Now you can push a formatted Linear or LLM summary straight into a database row every Friday, move an email attachment onto the right page, or trigger a workflow when a page changes and notify Slack.

Setup

1. In Whippy: add a step, then App → Notion → Connect, and authorize through OAuth.
2. In Notion: share the pages you need with the connection (page menu → Add connections).
3. For triggers: create the webhook subscription in your Notion Developer Portal, then paste the callback URL from your Whippy workflow trigger when you publish. Trigger setup is a one-time configuration on both sides, per workflow.

Added: Calendly Workflow Integration

Whippy added a native Calendly app to its workflow builder, so teams can trigger automations the moment a meeting is booked or canceled and take action on Calendly data without leaving the workflow editor.

What's Included

Three real-time webhook triggers:

• Invitee Created: a prospect books a meeting
• Invitee Canceled: a booking is canceled
• Routing Form Submission Created: someone submits a Calendly routing form

Plus 56 additional steps to read, create, update, and delete Calendly data, including scheduled events, event types, invitees, availability, scheduling links, contacts, routing forms, webhooks, and more.

How It Works

When a trigger fires, the workflow has immediate access to the booking details. From there, it can enrich the contact, notify the team, update the CRM, or take any action available in Whippy Workflows.

Example: A prospect books a demo. The workflow enriches their profile via Apollo, sends that data to OpenAI to generate a short host prep note, and posts everything to Slack. The team sees who booked, when the call is, and context for the conversation before they ever open their calendar.

The same trigger can also update Whippy CRM, send an SMS or email, or chain additional Calendly steps like fetching event details or updating contact records.

Why It Matters

Acting on a Calendly booking used to mean checking an email notification, manually looking up the prospect, pinging the team, and writing prep notes. A process that worked fine until it got busy and steps got skipped.

This integration makes that entire sequence automatic and consistent, regardless of how full the day is.

Setup

1. Go to Integrations → Calendly in your Whippy account
2. Connect with a Calendly Personal Access Token
3. Add a Calendly trigger or step to any workflow
4. Publish. Webhook triggers register automatically.

Notes

• Webhook triggers require Calendly Paid Plan
• OAuth 2.1 support is planned for a future release

Improved: Faster Long-Timeframe Agents Reports

Agents reports over extended date ranges now load significantly faster, eliminating slow load times for ranges longer than 3 months.

What's Included

• Reduced load times for standard Agents reports under Reports > Agents
• Improved performance across any date range longer than 3 months, including custom ranges selected via the date picker
• No changes to report structure, data, or navigation. Same workflow, faster results
• Full backward compatibility: shorter timeframes are unaffected

How It Works

Open Reports > Agents and select any date range of 3 months or longer, including custom ranges up to a full year. The report loads promptly without stalling or timing out, regardless of how much AI call data your account has accumulated.

This applies to the built-in Agents reports only.

Why It Matters

Long-timeframe reporting on AI agent performance was previously unreliable for analysis workflows on large datasets. That made it impractical to track trends across quarters or identify seasonality patterns without significant waiting.

This update makes extended-range reporting reliable and on-demand. Teams can now pull a full year of agent performance data in the same time it previously took to load a single month, supporting faster decisions without workarounds.

As call history grows over time, report performance stays consistent rather than degrading.

Setup

No setup required. The improvement is applied automatically. There is nothing to configure or enable.

Notes

• Applies to standard Agents reports under Reports > Agents only
• Existing report filters, date pickers, and data remain unchanged

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.