SALES

Log discovery-call objections into an Airtable coaching tracker per rep

Captures every objection from completed Zoom discovery calls and logs them as rows in an Airtable coaching tracker, tagged by rep, objection type, and how the rep responded.

CategorySales
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom discovery transcript completedZoomZoom
  • ActionFetch transcript textZoomZoom
  • ActionTag objections and rate rep responseHugging FaceHugging Face
  • LogicNormalize rep identity from host
  • OutputLog objection rows to Airtable trackerAirtableAirtable

What it does

This workflow builds a per-rep coaching dataset in Airtable. For each discovery call it records every objection raised, the type, the verbatim quote, and a short assessment of how the rep handled it, so coaches can filter by rep and objection type to see exactly where each person needs work.

When to use it

Use it when you run a structured coaching program and need durable, filterable objection data rather than ad hoc notes. It fits enablement teams that score objection handling and want a single source of truth for one-on-ones.

How it works

The flow triggers when a Zoom transcript completes. It fetches the transcript and uses a Hugging Face model to tag each objection and rate the rep's response on a simple acknowledged-reframed-resolved scale. A logic step normalizes rep identity from the meeting host. Each tagged objection becomes a row in the Airtable coaching tracker, linked to the rep record with the type, quote, response rating, and call date.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.