Turn the meeting no bot could join into tasks, records and a follow-up.

Plaud records the conversations a meeting bot cannot join: the site visit, the client lunch, the workshop, the chat at a booth. The recording gets captured and summarized. The follow-up is still somebody's evening.

Connect Plaud to a Kylon room and an agent picks it up from there. It reads the transcript and the notes Plaud generated, turns each action item into a task with an owner, proposes the CRM update and drafts the follow-up email. A person approves anything that reaches a client or changes a record.

This page collects everything we have published about Plaud and Kylon: how the connection works, the six in-person meetings teams use it for, two short films and the deeper guides.

What the connection can do

Kylon connects to Plaud through Plaud's official MCP server. You authorize your own Plaud account once from an authorization card, then choose which agents can use it. Those agents can:

• Find recordings by name, with when each one started and how long it ran
• Read the transcript with speaker names and timestamps
• Read the notes Plaud generated, one entry per tab, including summaries from your own templates and the moments you flagged on the device
• Do the follow-up in the room where the project or the account is already discussed, next to its tasks, records and threads

The connection reads. Plaud documents its MCP as read-only and working with synced recordings, so recording, editing and new transcriptions stay in the Plaud app.

Connect Plaud in three steps

1. Turn on Cloud Sync in the Plaud app. A recording reaches the agent once it has synced.
2. Connect Plaud in Kylon. Authorize your Plaud account from the authorization card and pick the agents that can read it.
3. Ask for the first piece of work. For example: "Find my last Plaud meeting and turn it into tasks for the team."

Two habits make it work better. Generate the summary you want in Plaud first, with a template for each kind of meeting, so the agent starts from a structured note. And give recordings real names. Search matches the recording name, not the transcript, so "Alder St kitchen walkthrough" is easy to find and "New Recording 12" is not.

Six in-person meetings teams run through it

1. Site visits and in-home consultations. Scope items become tasks with owners, open questions go to the estimator, and the recap to the client waits for the person who walked the site.
2. Client meetings in person. The agent matches the recording to the account, proposes the CRM fields to update and drafts the follow-up in your connected Gmail.
3. Handoffs to someone who was not there. The new owner reads the commitments in the client's own words, with the lines they came from.
4. Checking numbers before they go out. Square footage, unit counts, dates and prices said out loud are checked against the quote and the project records, and every mismatch is listed for a person to settle.
5. Repeat questions. Questions from the counter, the booth or the open house are collected over a few weeks into a draft answer list that a person edits and approves.
6. Workshops and trainings in more than one language. Decisions and tasks land in the room, with a recap in the language each reader works in.

Each one is written up in full, with the setup, in Kylon + Plaud: Six Use Cases for the Meetings That Happen in Person.

Watch it run

A pitch meeting recorded on Plaud, from the recording to the follow-up. The agent reads the recording and updates the investor's record, a teammate's Codex updates the chart in the record's thread, and the follow-up waits as a draft for a person to send.

The same pattern in a sales team: From inquiry to deal follows a Cal.com booking to a signed deal, with the Read AI report and the Plaud notes turned into the call recap. The film runs 49 seconds, and the page has the prompt that sets the workflow up in your own room.

Everything about Plaud on Kylon

• Six use cases for in-person meetings: site visits, client meetings, handoffs, number checks, repeat questions and workshops, with a room you can play through.
• Plaud MCP: setup, tool reference and limits: the tools the connection exposes, the fields they return, search limits and troubleshooting.
• Plaud Embedded SDK and MCP to CRM and issue tracking: the two routes to Plaud material, what Embedded costs, and a reviewed CRM and issue tracking workflow.
• From inquiry to deal: the sales workflow film, with Plaud notes in the call recap.
• AI meeting notes: how Kylon turns the notetaker you already use into tasks, CRM updates and drafts, with the Plaud pitch meeting film.

What stays with a person

Follow-up emails are created as drafts in your connected mailbox and wait for a person to send them. CRM changes and tasks are proposed in the thread first, so the person who was in the meeting confirms them.

Once a use case works by hand, an Automation in the room can check for new recordings each evening and start the same steps. People review in the morning.

Tell people you are recording. Plaud's own guidance is to inform all participants and confirm consent before recording.