Gemini takes notes in every meeting you record. Useful, until you try to automate from them: a summary in one doc, the transcript in another, and free text Make can’t route on.
What This Session Is About
In this live session, Diane Rocher (Talent Acquisition Partner, PhantomBuster) will walk through the scenario she runs after every hiring-manager intake meeting. It creates a Slack hiring channel, a screening kit and an updated job description. The live build focuses on the common path: the part every one of those branches depends on, from the trigger to the router. She’ll build it from a blank canvas with the real production settings. A Google Meet recording goes in, and a clean, typed data bundle comes out, ready to route anywhere. The branches after the router are shown in the finished scenario, not built live, and the full blueprint is shared so you can explore them yourself.
Join us for a hands-on build where you’ll see how to go from a raw Gemini recording to data you can route, and which details make it hold up in production.
What we’ll cover:
How to trigger on new Gemini notes and filter out every meeting you don’t care about, before spending a single operation or token
How to find the matching transcript with a Drive API call and a regex, since Gemini splits every meeting into two documents
How to prompt Claude to extract typed data you can route on: fixed categories, “trust the transcript over the summary”
Why it matters:
Get the common path right once, so you can tailor every branch after the router
Feed the LLM the full transcript, not just the summary, so the data is actually right
Reuse the pattern for any recorded meeting: sales discovery calls, client kickoffs, project intakes
Stick around for Q&A at the end — bring your questions, your own interview workflow, or just your curiosity.
Join the Live Session
CLICK HERE TO REGISTER
Free registration • Live build • Q&A session