Meetings

Disseminate Meeting Insights

Learn how to build a Lindy that joins meetings, takes notes, and shares targeted insights with your team.

Keeping everyone in the loop after meetings can be a real challenge — but Lindy is here to help!

You can think of the Lindy we'll set up in this guide as your meeting assistant and insights distributor, automatically capturing important information and sending it to the right teams. Whether you need to keep your product team updated on customer feedback or share the latest GTM strategies with marketing, Lindy has got you covered.

We'll start with this Disseminate Meeting Insights Lindy.

Here's what it does:

Joins your meetings and records the call
Extracts insights for different departments/teams
Sends insights to specific teams via Slack
Ensures all relevant information is shared across your organization

And the best part? This will take less than 5 minutes to set up.

Let's get started!

Add The Lindy To Your Account

Once you have added the Lindy to your account, open the Flow Editor to see how it works.

Configure The Triggers

The first thing you'll need to do is configure the triggers. This Lindy has two triggers:

1. Calendar Event Started

This trigger will connect your calendar to the workflow.

To configure this step, click the Calendar Event Started trigger and connect the calendar you want Lindy to monitor. This can be a team account or an email address/calendar that can join all team meetings.

Pro Tip: If you want Lindy to only join your team meetings, you can add a filter to the Calendar Event Started trigger.

2. Chat Message Received

The Chat Message Received trigger does not need any customization.

This trigger allows you to send meeting transcripts directly to Lindy in the Task View of the Lindy app without requiring her to join the call, which is handy for one-off meeting insight sharing.

You can click the back button in the flow editor to access the Task View where your Lindy can be woken up by this Chat Message Received action.

The Record Meeting Action

Click the Record Meeting action in your flow. This is the step that will record the meeting and generate the meeting transcript.

The "Meeting URL" field should be left on "Auto". This means Lindy will use intelligence to find the meeting link on the calendar event and join the call automatically.

In the “Chat Message On Join” field, you can customize the message Lindy sends to the meeting attendees once she joins the meeting. To remove the chat message sent by Lindy, keep the field to "Set Manually" mode and leave it blank. Learn more about configuring action parameters here.

You can also customize the name of your Lindy-bot in the “Name” field.

The First Condition

After the Record Meeting action, you'll find a series of Conditions and Slack Channel Message actions that help Lindy categorize and distribute insights from the meeting. Let's set up the first one for product-related insights.

Click on the first Condition action in your flow.

In the Condition field, you’ll see the following prompt:

The meeting transcript contained product-related insights and notable mentions. Examples of product-related insights include: feature requests, user feedback, bug fixes, technical challenges and roadmap changes.

This condition tells Lindy to look for product-related information in the meeting transcript. When this condition is met, Lindy will extract these insights and prepare them to be Slacked to the product team.

You can customize this prompt further if you want Lindy to focus on specific types of product insights that are most relevant to your team.

Remember, this is just the first condition. You'll set up similar conditions for other departments or types of insights in the following steps of your workflow.

The “If Else” Condition tells Lindy that if no product insights were found in the transcript, she can skip this step and go directly to the second Condition.

Send Product Insights To The Corresponding Channel

Click the Send Slack Channel Message action that follows the product insights condition.

In the “Channel” field, set it to "Set manually" mode. Then, type in the name of the Slack channel where you want product insights to be shared. This could be something like "product-team" or "meeting-insights-product".

The “Message” field is where you can customize how Lindy formats and presents the product insights. You can leave the default prompt or customize it to fit your team's preferences.

The default prompt is:

Alert the Team of the key product insights from the meeting transcript. Highlight notable talking points related to the product, including relevant numbers, names, metrics, timelines, and action items. Use your discretion to provide additional context or detail where necessary, ensuring the message captures all critical information for the team’s understanding.

Feel free to adjust this prompt to include any specific information or formatting that would be most useful for your product team.

Remember, this Slack message will only be sent when the previous condition for product-related insights is met. This ensures that your product team receives relevant information without being overwhelmed by updates from every meeting.

The Second Condition

After setting up the product insights condition and Slack message, you'll find another Condition step. This one is for Go-To-Market (GTM) insights.

Click on the second Condition action in your flow.

You'll see the following prompt:

The meeting transcript contained GTM-related insights and notable mentions. Examples of GTM-related insights include: product updates, customer pain points, pricing changes, competitive insights, campaign performance, target audience trends, content needs, user acquisition trends, and conversion insights.

This condition tells Lindy to look for GTM-related information in the meeting transcript. When this condition is met, Lindy will extract these insights and prepare them to be Slacked to the GTM team.

You can customize this prompt further if you want Lindy to focus on specific types of GTM insights that are most relevant to your team.

In the “If else” condition, you'll see the following prompt:

No GTM insights were found.

This tells Lindy that if no GTM insights were found in the transcript, she can skip this step and go directly to the next Condition (if there is one) or end the workflow.

Remember, this condition works in tandem with the previous one, allowing Lindy to categorize different types of insights from the same meeting transcript. You can set up additional conditions for other departments or types of insights following the same pattern.

Completing Your Lindy Setup

Now that you know how to customize the Conditions and Slack Channel Message actions, let's finish setting up your Lindy:

GTM Insights: Click the Send Slack Channel Message action that follows the GTM insights condition. In the Channels field, set it to "Set manually" mode and enter your GTM team's Slack channel (e.g., "gtm-team" or "meeting-insights-gtm"). Review the Message field and adjust the prompt if needed to best suit your GTM team's needs.‍
Engineering Insights: Click on the next Condition action in your flow. Review the condition prompt:

the meeting transcript contained Engineering-related insights and notable mentions. Examples of Engineering-related insights include: technical challenges, bug fixes, feature specifications, system architecture updates, code review feedback, performance metrics, integration requirements, and development timelines.

‍
Edit this prompt if you want to focus on specific types of engineering insights.

Click the Send Slack Channel Message action that follows the engineering insights Condition step. Set the Channels field to "Set manually" mode and enter your engineering team's Slack channel. Customize the Message field as needed for your engineering team.

Additional Teams Repeat these steps for any other teams you want to include, following the same pattern of Condition and Slack Channel Message actions.

You've now completed setting up your Disseminate Meeting Insights Lindy! This Lindy will join your meetings, record them, extract relevant insights, and share them with the appropriate teams via Slack.

Test

The easiest way to test your Lindy is to send a past meeting transcript to Lindy in the Task View.

If you do not have one, have Lindy join your next team call!

See below for an example department insight Lindy shared via Slack:

More examples of insights being shared from the same meeting:

‍

Remember to adjust the Slack Send Channel Message "Message" field to "AI Prompt" mode, and provide Lindy with clear instructions on how you want the messages formatted and what details to include.

Great job! Now you have a Lindy that joins your meetings, extracts key insights, and shares them with the right teams via Slack – helping keep everyone in the loop effortlessly.

Guides

Automated Post-Meeting Scheduling

Customer Case Study Drafter