All work
GTM automation, Kuration AI

CRM — Follow-up Presentation & Email

Send a sharp follow-up the same day every call ends. The system reads the call transcript, writes the summary, builds a tailored 4-slide deck, and drafts the email with the deck attached. A 30-minute chore becomes a Gmail draft waiting for one click.

Meeting closed transcript ready
Summarise Gemini
Build the deck Slides template
Gmail draft deck attached

How it works

Trigger on meeting close

Webhook fires when the meeting record is updated after the call. Pulls the meeting, the company, the contact.

Reads the transcript

Gemini reads what was actually said and writes a structured summary: challenges, signals, how we help, next steps.

Branch on transcript

Transcript present: full deck path. Transcript missing: lighter email-only follow-up. Both end with a Gmail draft.

Slide deck built

The follow-up Slides template is duplicated. Gemini drafts the four sections, the Slides API fills the placeholders.

Gmail draft + deck attached

Gemini writes a personalised email referencing the discussion. The deck is downloaded from Drive and attached to the draft.

One click to send

Airtable record updated with deck link and draft status. Read, tweak, send. 30 minutes saved per call.

n8n workflow: webhook, get meeting, update meeting, find company, find contact, branch on transcript presence; if yes path duplicates GTM template, edits PPT with Gemini, edits slides, attaches to Airtable, alerts Slack and creates Gmail draft; if no path creates email follow up with Gemini, drafts in Gmail, updates Airtable
Follow-up workflow: meeting close to Gmail draft + deck.

Why split from the meeting prep flow

Two reasons. Different trigger (meeting status update vs. booking), different destination (Slides + Gmail vs. Airtable record). Splitting also lets the prep flow stay fast, while the follow-up flow can take its time on long-form generation without holding up anything else.

Why a template-and-populate deck

Same logic as the GTM Research flow: hand-design the visual once in Slides, fill placeholders programmatically. The decks read as bespoke without anyone touching them. Edit the template when the message evolves, every new follow-up picks up the change.