Skip to content

The moment it happens

Turn meeting transcripts into notes in Google Docs and Slack

When a meeting transcript is ready, notes and action items are saved to a Google Doc and the summary is posted in Slack.

Runs
The moment it happens
Apps
Google Docs, Slack
AI
Yes, uses the built-in AI allowance
Access
service account; chat:write

Send this to your assistant

Create a ClickRuntime automation: when a meeting transcript is sent to my trigger link, write notes and action items into a new Google Doc and post the summary with the link to #team in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A team meets several times a week, records the calls and gets a transcript afterwards. Nobody reads a forty-minute transcript, so decisions and action items live only in the memories of whoever was paying attention, and the same topics come back the following week.

Turning each transcript into short notes with clear action items, saved in a doc and posted where the team talks, makes meetings produce something people use. Those who missed the call catch up in a minute.

What you get out of it

  • Action items with owners

    Each action item names who agreed to do it. Posting them in Slack right after the call makes follow-up much more likely than a note in someone's notebook.

  • Catch up on meetings you missed

    A short summary in Slack tells you whether you need to read more. The full notes in the doc are there if you do.

  • One place for all meeting records

    Every meeting gets its own doc in the same folder, named by date and title. Finding what was decided in last month's planning call takes seconds.

  • Nobody has to take notes

    Everyone can take part in the discussion instead of one person typing. The notes are written from the transcript after the call.

How it works

What happens, step by step

  1. When a meeting transcript is ready, your recording service sends it to ClickRuntime.

  2. AI reads the transcript and writes a summary, decisions and action items.

  3. The notes are saved in a new Google Doc named after the meeting.

  4. A short summary with a link to the doc is posted in your team's Slack channel. Each transcript is handled once, even if it is sent twice.

Before it runs live

  • Connect Google Docs
  • Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
  • Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens
Turn meeting transcripts into notes in Google Docs and Slackjust nowSucceeded
Slack · #teamWeekly planning: agreed to ship the Contoso integration on 4 Nov. Action items: QA sign-off (QA team, Fri), pricing page update (marketing, Wed). Notes: https://docs.google.com/document/d/9kL/edit

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Act only on the items that match your own rules, and skip the rest
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Google Sheets
  • Combine it with other Google Docs and Slack steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
meeting_notes_saved_to_docs_and_shared_in_slack.pyexample
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from slack_sdk import WebClient
from clickruntime import on_event, credentials, ai, state

@on_event
def handle(event):
    data = event.json or {}
    transcript, title = data.get("transcript", ""), data.get("title", "Meeting")
    if not transcript or state.get(f"done:{event.event_id}"):
        return {"skipped": True}
    notes = ai.generate("Write meeting notes: summary, decisions, action items (owner, due). Start with a 2-line summary, then '---'.\n"
                        + transcript[:60000], max_output_tokens=1200).text
    summary = notes.split("---")[0].strip()
    docs = build("docs", "v1", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)
    doc = docs.documents().create(body={"title": f"{title} - notes"}).execute()
    docs.documents().batchUpdate(documentId=doc["documentId"], body={"requests": [{"insertText": {"location": {"index": 1}, "text": notes}}]}).execute()
    link = f"https://docs.google.com/document/d/{doc['documentId']}/edit"
    WebClient(token=credentials.connection("slack", "work")).chat_postMessage(channel="#team", text=f"*{title}*\n{summary}\nNotes: {link}")
    state.set(f"done:{event.event_id}", True)
    return {"doc": doc["documentId"]}

FAQ

Common questions

Where do the transcripts come from?
From any recording or transcription service that can send the finished transcript to a link, such as a meeting recorder or a speech-to-text service. You give it your ClickRuntime trigger link.
Can different meetings post to different channels?
Yes. Meetings can be matched by title or organiser, so sales calls post to #sales and engineering stand-ups to #eng.
What do the notes include?
A short summary, key decisions, open questions and action items with owners and due dates where they were mentioned. You can change the structure to match how your team works.
What permissions does it need?
service account; chat:write. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run for each event the app sends.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Turn meeting transcripts into notes in Google Docs and Slack” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.