SALES

Write a deal-risk score and call summary back onto the HubSpot deal record

After each Zoom sales call, computes a deal-risk score and a structured call summary, then writes them onto the matching HubSpot deal's custom properties and logs a timeline note.

CategorySales
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom recording completedZoomZoom
  • ActionFetch call transcriptZoomZoom
  • ActionExtract structured risk + summaryOpenAI
  • ActionMatch deal by attendee emailHubSpotHubSpot
  • OutputUpdate deal properties + log timeline noteHubSpotHubSpot

What it does

Keeps your HubSpot pipeline honest by stamping each deal with a fresh risk score and a clean summary every time a call happens. No rep data entry: the deal record always reflects the most recent conversation.

When to use it

Use this when forecasting reviews depend on accurate deal properties but reps under-log calls. Ideal for RevOps teams that build dashboards and forecast rollups off HubSpot custom fields and want those fields trustworthy.

How it works

  1. 1Zoom fires a recording-completed event.
  2. 2The transcript is pulled from Zoom cloud recordings.
  3. 3OpenAI returns a structured object: risk score, sentiment, next steps committed, objections raised, and a two-sentence summary.
  4. 4HubSpot matches the deal via attendee email or the meeting's linked engagement.
  5. 5The flow updates custom deal properties (call_risk_score, last_call_sentiment, last_call_summary) and writes a timeline note with the full summary so AEs and managers see it inline on the record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.