Topics ▾
Routines ·

Route every meeting transcript to the right Bot with a webhook

Advanced, 30 minutes

When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.

How this helps you

Every call's follow-up reaches the right Bot without you forwarding notes.

✦ Try it
When this webhook fires, read the meeting transcript in the request. Decide which Bot owns it: [routing rules]. Send it to that Bot with a 3 line summary and any action items, and file the transcript in [folder]. If it fits none of them, send it to me. Downstream Bots may draft but never send.

Fill in: [routing rules] is a list like 'deals and offers to TC Desk, marketing to Social, everything else to me'. [folder] is where transcripts are filed.

What they did

Mike Weisman runs a real estate team with a set of single-job Bots: Inbox, TC Desk (transaction coordination for 30 to 50 live deals), a social media manager, a Facebook ads manager, a YouTube Bot and others, all reporting through a Chief of Staff Bot he talks to all day. When a call, walkthrough or training recorded by Granola ends, Granola fires a webhook and his Chief of Staff catches it, reads the transcript, files it and sends it to the right Bot. A conversation about a potential offer goes to TC Desk, which knows the transaction and may draft an email or prepare a form such as an addendum when he asks.

Who it's for: Teams with many calls a day whose follow-up work is spread across several Bots.

Before you start

How to try it

  1. Ask your Chief of Staff Bot to create a routine that starts from a webhook. Copy its webhook URL and key from the routine's details.
  2. In your note taker, set up a webhook to that URL when a recording finishes (we haven't verified this step for Granola).
  3. Paste the routing rules below into the routine.
  4. Record a short test call and check where the transcript landed.
  5. Review the routing log for a week before letting downstream Bots draft anything.

What to expect

A note in the Chief of Staff chat: 'Call with co-broker about 12 Main St sent to TC Desk with 2 action items. Transcript filed.'

Common mistakes

Related tips

Worth knowingCarved from a segment of this video starting at 2:52. Paraphrased by us; watch the original for the full walkthrough.
Next in Routines →Build a monthly usage audit page that labels every routine

Learn more: Grok Bot Routines Not Working? Do It by Hand, Save a Skill, Then Schedule · All Grok Bot routines tips

Related Grok Bot tips

More Routines →
Routines

A read-only usage audit across your whole Bot team

One prompt has your chief of staff check every Bot's routines, schedules and triggers, then report what to pause, slow, narrow or merge, and change nothing until you approve.

How this helps you You see exactly which routines and triggers spend your usage, with a ranked list of safe changes you approve one by one.
Spotted by @Michael_Fenech_ · 3 Nov 2026
Routines

Have a Bot watch for cancellations at a fully booked spot

Ask a Bot to check a booking page every hour and ping you the moment a slot opens, so you can grab a cancellation before anyone else.

How this helps you You stop refreshing a booking page and still catch the cancellation.
Spotted by @mattyp · 31 Oct 2026
Routines

A routine that triages your backlog with RICE and blast radius

Your Bot collects requests into a backlog, then a routine scores each item for reach, impact, confidence, effort and blast radius so the best small jobs rise to the top.

How this helps you You stop arguing about what to build next; the backlog sorts itself by value and risk.
Spotted by Rob Shocks - Switch Dimension (YouTube) · 31 Oct 2026