The moment it happens

Turn meeting transcripts into Linear issues

Send a meeting transcript and every action item becomes a Linear issue, with a summary and links posted in Slack.

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

Send this to your assistant

Create a ClickRuntime automation: when I send a meeting transcript to this link, pull out the action items with AI, create a Linear issue for each one, and post a summary with the links to #team.

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

Add to ChatGPT Add to Claude

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

Why use it

Why teams use this automation

A product lead runs three planning meetings a week. Each one ends with a handful of agreed next steps, and someone is supposed to write them up as tickets. Usually that someone is her, at the end of the day, from memory. Some items never make it into Linear, and two weeks later nobody can say who agreed to what.

Sending the transcript to a link right after the call means the action items are captured while they are still accurate, and the team sees the summary in Slack before they have moved on to the next thing.

What you get out of it

Nothing agreed gets lost
Every action item in the transcript becomes an issue, not just the ones someone remembered to write down. Small follow-ups that usually slip away end up in the backlog where they can be prioritised.
Tickets exist before the next meeting
Issues are created minutes after the call ends. By the next check-in, work has already started instead of waiting for someone to do the admin.
Owners are written down
When the transcript names who will do something, the issue says so. That removes the awkward question of who said they would handle it.
One summary for people who missed it
The Slack post gives the decisions and links in one place. People who were not on the call can catch up in a minute instead of asking around.

How it works

What happens, step by step

You send a meeting transcript to your automation's private link, from a notes tool or by hand.
AI reads the transcript and writes a short summary, the decisions made, and a list of action items with owners.
Each action item becomes a new issue in your chosen Linear team.
A summary with links to every new issue is posted in your #team Slack channel.

Before it runs live

Connect Linear
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 Linear issuesjust nowSucceeded

Slack · #teamMeeting summary: agreed to ship the Northwind export in v2.4. ENG-412 Draft migration plan (Priya), ENG-413 Update pricing page copy (Sam)

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 Linear 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.

create_linear_issues_from_meeting_action_items.pyexample

from clickruntime import on_event, ai, credentials, http, notify

TEAM_ID = "your-linear-team-id"
SCHEMA = {"type": "object", "properties": {"summary": {"type": "string"},
          "items": {"type": "array", "items": {"type": "object", "properties": {
              "title": {"type": "string"}, "owner": {"type": "string"}}}}}}

@on_event
def handle(event):
    text = ((event.json or {}).get("transcript") or event.body)[:30000]
    out = ai.generate(["Summarise this meeting and list action items with owners.", text],
                      max_output_tokens=1200, json_schema=SCHEMA).json
    headers = {"Authorization": credentials.secret("LINEAR_API_KEY")}
    q = "mutation($i: IssueCreateInput!){ issueCreate(input: $i){ issue { identifier url } } }"
    links = []
    for item in out.get("items", []):
        title = item["title"] + (f" ({item['owner']})" if item.get("owner") else "")
        r = http.post("https://api.linear.app/graphql", headers=headers,
                      json={"query": q, "variables": {"i": {"teamId": TEAM_ID, "title": title}}}).json()
        issue = r["data"]["issueCreate"]["issue"]
        links.append(f"- <{issue['url']}|{issue['identifier']}> {title}")
    body = "\n".join(links) or "No action items found."
    notify.slack(f"*Meeting summary*\n{out.get('summary', '')}\n{body}", channel="#team")
    return {"issues": len(links)}

FAQ

Common questions

What format does the transcript need to be in?

Plain text from any recording or notes tool works, sent as the body of the request or in a transcript field. Speaker names help attribute action items to the right person, but they are not required.

Which Linear team do the issues go to?

All issues go to one team you choose when setting it up. If your meetings cover several teams, you can run one link per team and send each transcript to the right one.

What if the meeting had no action items?

No issues are created. The Slack summary is still posted with the decisions, and it says that no follow-ups were found, so you know the transcript was processed.

What permissions does it need?

Linear write; Slack 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.

The moment it happensAI