Zoom Meeting Follow-up Agent with Codex
Live demo
Watch it work before it's live
Warehouse rollout call - Nordlys Logistikk
ConfirmedIngrid Solberg · Meeting ID 892 4417 0356
Transcript finished processing for a 47 minute meeting with five participants: Ingrid Solberg and Tomas Weber from our side, plus Kwame Asare, head of operations at Nordlys Logistikk in Oslo, and two of his depot leads. The Zoom summary records that all 14 depots still run on printed pick lists, that Kwame wants a rollout plan covering every depot by 3 November, and that Tomas took on sending per depot pricing by Monday 18 August. Kwame also asked whether the scanners keep working with no signal in the Bergen cold store, and the summary shows nobody answered him.
What you'll need
Set up in minutes
Connect Zoom
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect HubSpot
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Followup style
Describe the email you would have written yourself after a call, and what the HubSpot note has to contain: voice, length, how you sign off, and the things you refuse to put in writing.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
A considered pairing
Why Codex for this agent
No date the summary lacks
Where the summary records no timing, the draft says the timing is still to be confirmed rather than choosing a Friday. An invented date is the one error a customer will hold you to.
Lookups before prose
Matching outside participants to HubSpot contacts and filing the note is API work with a definite answer, and it is most of the run. The email is the short part at the end.
Good to know
Before you fork
Who is on the hook if a draft says something wrong?
Whoever presses send, which is the whole design. The one Gmail operation on this graph creates a draft and there is no send operation anywhere, so a wrong sentence is caught in your own drafts folder. That does mean somebody has to read them, and a rep who sends six unread has removed the only safeguard.
Other editions
Run it with a different agent
Make it yours
Put Zoom Meeting Follow-up Agent to work on Codex.
Free to start. Guided setup, a staged test run, and a workflow you can change at every step.