Meeting follow-up & CRM updates

The meeting ends and the work begins: the summary with its citations, the commitments each side made, the CRM fields that should change, and the follow-up email - all proposed, none applied without you.

Talk to us Read the docs

The brief

Written like you’d brief a person.

This is the whole setup - a procedure in plain language, with tools and specialist agents referenced inline. When it runs is not written here: that’s the trigger, configured beside it.

Find the meeting's notes doc with #yekar.google-drive.search and read it with #yekar.google-docs.read, summarise it citing the passages it rests on, extract commitments and next steps, propose stage and stakeholder changes with #yekar.hubspot.update-record, log the summary with #yekar.hubspot.create-note, and draft the follow-up with #yekar.gmail.create-draft.

How it runs

From trigger to logged outcome.

Trigger

Schedule - An hourly sweep for new notes docs from meetings with an external attendee

Process the notes
Reads the approved notes doc for the meeting.
Summarise with citations
Every decision and claim points at the passage it came from.
Extract the commitments
Who promised what, by when - on both sides.
Propose the CRM changes
Stage, stakeholders and next step, as proposals with reasons.
Draft the follow-up
The email and the next meeting plan, parked for the owner.

Where people stay in control

Nothing consequential runs on its own.

CRM changes are proposals until the account owner accepts them.
The follow-up email waits as a draft; the agent never sends to a customer on its own.

Tools it uses

Runs on accounts you already have.

Google Drive
Google Docs
HubSpot
Gmail
Slack

Connected once, governed per agent - this use case gets only the tools listed here.

Illustrative savings

$700–$1,900 / month

Assumes 60–200 external meetings a month at 15–20 minutes of write-up and CRM housekeeping each.

Illustrative monthly savings, estimated from typical handling time at public salary benchmarks, reviewed August 2026. Not a promise or a guarantee - your numbers depend on volume and process.

What makes this dependable

Keep people in controlReview the real action before it runs Operate and improveSee what every answer rested on Run it reliablyNever lose track of accepted work

All use cases →