SALES

Post-Demo Loom Recap Logged to Attio After Calendar Call

After a Google Calendar demo event ends, generates a personalized Loom recap, logs it on the Attio deal, and emails the prospect the recap with next steps.

CategorySales
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDemo calendar event endsGoogle CalendarGoogle Calendar
  • LogicConfirm event is a demo with a linked record
  • ActionGenerate personalized Loom recapLoomLoom
  • ActionLog Loom recap on the Attio dealAttio
  • OutputEmail recap and next steps to prospectGmailGmail

What it does

Closes the loop after a live demo. When a scheduled demo meeting ends, it produces a short personalized Loom that recaps what was covered and the agreed next steps, records it on the Attio deal, and sends the prospect a tidy follow-up — replacing the recap email reps often forget to send.

When to use it

Use it when reps run live demos but follow-up is inconsistent. Best for teams using Attio as CRM and Google Calendar for scheduling who want every demo to end with a polished, on-brand recap.

How it works

  1. 1A Google Calendar event-ended trigger fires for meetings tagged as demos.
  2. 2A filter confirms the event is a demo and has an attached prospect record.
  3. 3A personalized Loom recap is generated from the meeting title, attendees, and notes.
  4. 4The Loom link is written to the matching Attio deal as a note and activity.
  5. 5A Gmail follow-up emails the prospect the recap with proposed next steps.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect LoomVideo transcripts, libraries.
  3. 3
    Connect AttioReal-time CRM with structured data + powerful views.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.