Lindy.ai meeting prep agent (L3)
Agent reads calendar 1h before each meeting, pulls company news + CRM history + last 3 emails, drops a brief in Slack.
The steps
- 01
Connect Data Sources via OAuth
To start, log into your Lindy.ai workspace and navigate to the 'Integrations' tab on the left-hand sidebar. To achieve a Level 3 automation, you must connect three primary data sources: Gmail, Google Calendar (or Outlook), and your CRM (Salesforce or HubSpot). • For Calendar: Click 'Connect' on Google Calendar, approve the OAuth pop-up, and ensure you select the specific work calendar where your sales calls are held. • For CRM: Search for 'Salesforce' or 'HubSpot'. You will need 'Read' access to Accounts, Contacts, and Opportunities. Provide the credentials of an admin or a user with wide visibility to ensure the agent doesn't miss history due to permission locks. • For Email: Connect Gmail. This allows Lindy to parse the specific context of the thread leading up to the invite. Owner: Sales Ops or RevOps Admin. Time Estimate: 15 minutes. Prerequisite: Admin access to your CRM. Pitfall: Connecting a personal email accidentally. Always verify the work domain is the one active in your browser. Definition of Done: All three icons show a green 'Connected' status in the Lindy dashboard.
- 02
Define the Intelligence Logic
In Lindy, click 'Create New Lindy' and name it 'Meeting Prep Agent'. Under the 'Brain' or 'Instructions' section, you must define the exact prompt that dictates how the agent summarizes data. Don't be generic; instruct it to look for 'Negative Sentiment' in emails and 'Funding Rounds' or 'Leadership Changes' in news. Use this template structure: 'For the upcoming meeting with [Company], provide: 1. The Hook: One recent news event from the last 30 days. 2. The History: A 2-sentence summary of the last CRM Opportunity stage and why it closed/stalled. 3. Email Context: Summary of the last 3 emails,identify the main 'pain point' mentioned. 4. Three Discovery Questions: Tailored to their industry.' Owner: Sales Enablement or VP of Sales. Time Estimate: 30 minutes. Pitfall: Too much fluff. Instruct the agent to 'Be concise and use bullet points only.' Definition of Done: The agent's instruction window contains a structured prompt with clear logic for news, CRM, and email.
- 03
Configure the 60-Minute Trigger
Go to the 'Triggers' menu within your Lindy configuration. Select 'Calendar Event' as the primary trigger. You need to set the timing to exactly 60 minutes before the 'Event Start Time'. • Setting: 'Trigger 1 hour before event'. • Filtering: Add a filter so the agent only runs for 'External Meetings'. You can set a rule like: 'If Attendee Email does not contain @yourcompany.com'. This prevents the agent from wasting credits on internal 1-on-1s or team syncs. • Backup: Ensure the agent is set to 'Auto-run' so it doesn't wait for your manual approval. Owner: RevOps. Time Estimate: 10 minutes. Pitfall: Forgetting to exclude internal domains, leading to Slack spam every time you have a team meeting. Definition of Done: The trigger is toggled to 'Active' and internal domains are successfully filtered out.
- 04
Set Up Slack DM Delivery
Navigate to the 'Actions' or 'Step 2' area of your Lindy workflow. Select 'Slack' as the output channel. Rather than posting to a public channel where data might be sensitive, configure the agent to send a Direct Message (DM) to the 'Organizer' of the meeting. • Mapping: Use the 'Dynamic Field' tool to map the Slack recipient to the 'Meeting Organizer Email' from the calendar event. • Formatting: Use Slack's markdown blocks (e.g., *Bold* for headers) in the Lindy output template to make the brief readable on a mobile device. • Example: 'Hey [Organizer Name], here is your 1-hour prep for [Meeting Title].' Owner: RevOps or IT. Time Estimate: 20 minutes. Prerequisite: Lindy Slack App must be installed in your workspace. Pitfall: Sending to a public channel by mistake. Always test with a 'Private DM' setting first. Definition of Done: A test run successfully delivers a formatted brief to your own Slack DM.
- 05
Monitor and Iterate Context
To ensure the agent is actually improving sales quality, you need to track engagement. In Lindy’s 'Logs' or 'Analytics' tab, check the 'Execution Success Rate'. • Feedback Loop: Add a final step in the Slack message that says: 'Was this helpful? Reply 👍 or 👎'. • Manual Review: Once a week, Sales Ops should compare the CRM 'Next Step' field for meetings that had a Lindy brief versus those that didn't. • Iteration: If reps say the news is 'too generic,' update the Brain logic in Step 2 to target specific sources like TechCrunch or LinkedIn. Owner: Sales Ops. Time Estimate: 30 minutes per week. Pitfall: Setting it and forgetting it. If the briefs are low quality, reps will mute the bot. Definition of Done: A weekly review cadence is established and the prompt is adjusted at least once based on rep feedback.
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.