How we handle GDPR data-subject requests on a deadline
Legal
The meeting agent we run on Kortix — connected to Google Calendar, the call transcript, and Linear. After each call it writes structured notes and files action items as tickets assigned to the right people.


Most of what a meeting decides is lost within a day. The notes get taken by whoever remembers to, the action items live in someone's head, and the follow-up happens only if a person turns the conversation into tasks afterward — which is the step that gets skipped when the next meeting starts.
We handle this by putting an agent on the calendar. After each call it writes structured notes and files the action items as tickets, assigned to the people who own them. This writes up how we run that on Kortix — the connections, the steps, and the guardrails.
Turning a conversation into notes and tasks is real work, and it lands on whoever's least busy at the end of the call — which on a small team is nobody. Decisions get made, owners get named out loud, and then the meeting ends and none of it is written down. A week later the thing everyone agreed on hasn't started because it was never a task.
Recording the call solves the record but not the follow-up: nobody rewatches an hour of video to find the three things they agreed to do. The gap is between the transcript and the tickets, and closing it by hand is exactly the chore that falls off.
Our calendar in Google Calendar is connected to an agent running on Kortix. When a call ends, it spawns its own isolated session — a cloud sandbox — with scoped access to what note-taking needs: the event, the transcript, and Linear. It writes structured notes, pulls out the action items, and files each one as a ticket assigned to the person who owns it.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the meeting recap skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a meeting notes agent in this workspace.
Create the agent agents/meeting-notes.md. Its job is to turn each finished meeting's transcript into structured notes and Linear tickets. It may use the Google Calendar, Google Drive and Linear connectors.
Create the skill skills/meeting-recap/SKILL.md with these rules:
Add a cron trigger meeting-ended-check to kortix.yaml. It runs the meeting-notes agent every 15 minutes with the prompt "Load the meeting-recap skill and write notes and tickets for every meeting that ended since the last check."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your calendar, the drive that holds your transcripts and your ticket tracker. Credentials are brokered server-side and never enter the agent's machine.

Finds finished meetings and their attendees.

Reads the meeting transcript.

Files a ticket for each action item.
Merge the change request, then start a session with the meeting-notes agent and send this prompt. Read the notes and check each ticket's assignee before you let the schedule take over.
Write up the meetings that ended since the last check.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: meeting-ended-check name: Meeting-ended check on: cron: "0 */15 * * * *" run: agent: meeting-notes prompt: Load the meeting-recap skill and write notes and tickets for every meeting that ended since the last check.The agent assigns a ticket only when the transcript names the owner or the ownership map in memory covers the topic. Every other action item becomes an unassigned ticket with the ambiguity in its description, for a person to triage. The agent only creates tickets. It never closes, reassigns or edits existing work.
Each meeting ends with notes on the meeting record and tickets in Linear. This is what a run looks like in the session:
Wrote notes for 1 meeting with 2 decisions. Filed 5 tickets in Linear: 4 assigned to the owners named in the call, and 1 unassigned because nobody took the pricing page copy.
Once it works, paste any of these into the same session.
Fifteen minutes before each recurring meeting, add the open tickets from its last session to the event description.
Every Friday, collect the decisions from this week's meeting notes into one Google Doc in Drive, grouped by meeting.
When an action item matches an open Linear ticket, link that ticket in the new ticket's description instead of repeating its context.
Giving an agent the ability to file tickets and assign work is a trust question. The relevant controls on Kortix:
The follow-up that used to depend on someone remembering now arrives as notes and tickets minutes after the call ends. The team reads a clean summary and finds their tasks already in Linear, instead of reconstructing the meeting from memory a week later.
The setup relies on four pieces: sandbox isolation per meeting, a secrets manager to broker the Calendar and Linear tokens, a flag for anything the agent can't confidently assign, and memory that carries context forward across meetings.