All posts
2 min readby Romiel Inolino

HubSpot recorded meetings no longer create call records. Workflows triggered on calls no longer fire for them

HubSpotCRMworkflowsRevOps

The most useful HubSpot change from Unbound 2026 was not on the main stage. It may already be breaking your workflows.

What happened

MarTech's Unbound 2026 roundup flags a change that is already live. Meetings recorded with Notetaker or a video conferencing integration used to create both a call record and a meeting record. As of August 31, 2026, only the meeting record is created, and the recording and transcript are stored on it.

HubSpot's knowledge base spells out the impact: workflows triggered by call records no longer fire for recorded meetings. Call based properties such as Has transcript are now available on the meeting object, and workflows, reports or integrations that used them may need updates. Call objects still exist for real phone calls, and historical data is unchanged. Recording URLs for meetings are now private and require authentication.

The same roundup covers a new Churn Risk signal in Buyer Intent, which is live on Starter and above and uses HubSpot credits. It reads conversations, emails, calls, transcripts and notes for warning signs like cancellation language, recurring unresolved issues and budget pressure, then flags the risk and explains why. It can trigger a workflow that notifies the account owner.

My take

This is the kind of change that does not throw an error. A follow up task workflow built on "call with transcript" just stops creating tasks for Zoom and Teams meetings, and nobody notices until a rep asks why.

What I would check in any portal this week:

  1. Workflows enrolled on the call object that were meant for meetings. Add or move the trigger to meetings.
  2. Reports that count meetings through call records, or that filter calls to avoid double counting.
  3. Any integration or Zap that reads recording links. Those URLs now need authentication.

Once the meeting record is the single source, it becomes a better trigger. That is a good moment to add Churn Risk to the same flow: flag goes up, the account owner gets a task, and larger accounts also alert a manager. Start with notifications only, and let the team judge the flags for a few weeks before anything automated reaches the customer.

More posts