OpenClaw Lark bot meeting management functionality

Meetings are where productivity goes to die — unless you have a bot that handles the logistics so humans can focus on the actual discussion. Imagine a Lark bot that schedules meetings, sends reminders, captures action items, and distributes notes — all without anyone opening a calendar app.

That's exactly what you can build with OpenClaw on Lark. Let's wire it up.

What "Meeting Management" Actually Means

A meeting management bot isn't just a calendar wrapper. It covers the full lifecycle:

1. Scheduling: Find available slots across participants, create the event
2. Pre-meeting: Send agendas, prep materials, and reminders
3. During meeting: Track time, capture notes and action items
4. Post-meeting: Distribute summary, assign follow-ups, track completion

Each phase maps to specific OpenClaw skills that interact with Lark's Calendar and Messaging APIs.

Setting Up the Meeting Skill

First, deploy your OpenClaw instance on Tencent Cloud Lighthouse:

1. Visit the Tencent Cloud Lighthouse OpenClaw page to provision your instance.
2. Select the "OpenClaw (Clawdbot)" application template under "AI Agents".
3. Deploy by clicking "Buy Now" — your bot's home base is ready in minutes.

For skill installation basics, the OpenClaw Skills guide covers the fundamentals.

Now configure the meeting management skill:

# /opt/clawdbot/config/lark-meetings.yaml
channel: lark
lark:
  app_id: "${LARK_APP_ID}"
  app_secret: "${LARK_APP_SECRET}"

skills:
  meeting-scheduler:
    enabled: true
    description: "Schedule and manage meetings via Lark"
    permissions:
      - calendar:read
      - calendar:write
      - contact:read
    config:
      default_duration: 30  # minutes
      buffer_between_meetings: 5  # minutes
      working_hours:
        start: "09:00"
        end: "18:00"
        timezone: "Asia/Shanghai"
      auto_reminder: true
      reminder_minutes: [15, 5]

  meeting-notes:
    enabled: true
    description: "Capture and distribute meeting notes"
    config:
      auto_summarize: true
      action_item_detection: true
      distribute_to: "all_participants"

Natural Language Scheduling

The magic of an AI-powered meeting bot is natural language understanding. Users don't need to learn commands:

User: "Schedule a 30-min sync with @Alice and @Bob sometime tomorrow afternoon"

Bot: "I found these available slots for all three of you tomorrow:
  1. 2:00 PM - 2:30 PM
  2. 3:30 PM - 4:00 PM
  3. 4:30 PM - 5:00 PM
  
  Which works best? Or should I pick the earliest?"

User: "Go with option 2"

Bot: "Done! Meeting 'Team Sync' scheduled for tomorrow 3:30-4:00 PM.
  Calendar invites sent to @Alice and @Bob.
  Reminder set for 15 minutes before."

This interaction is powered by the bot's ability to:

• Parse natural language time expressions
• Query Lark Calendar API for free/busy data
• Create events and send notifications

Post-Meeting Automation

After a meeting, the bot can process notes and generate structured output:

# Example: the bot processes a meeting transcript and outputs
# structured action items to the Lark group

# In the bot's skill logic, the output might look like:

{
  "meeting": "Sprint Planning - March 6",
  "duration": "45 minutes",
  "participants": ["Alice", "Bob", "Charlie"],
  "summary": "Discussed Q2 roadmap priorities. Agreed to focus on API v2 and mobile app redesign.",
  "action_items": [
    {
      "assignee": "Alice",
      "task": "Draft API v2 specification",
      "deadline": "2026-03-13",
      "priority": "high"
    },
    {
      "assignee": "Bob",
      "task": "Create mobile app wireframes",
      "deadline": "2026-03-15",
      "priority": "medium"
    },
    {
      "assignee": "Charlie",
      "task": "Review Q1 metrics and prepare comparison report",
      "deadline": "2026-03-10",
      "priority": "high"
    }
  ],
  "next_meeting": "2026-03-13 10:00 AM"
}

The bot posts this summary to the Lark group and optionally creates tasks in Lark's task management system.

Recurring Meeting Intelligence

For recurring meetings, the bot tracks patterns over time:

recurring_meetings:
  weekly_standup:
    schedule: "every Monday 10:00 AM"
    participants_group: "engineering_team"
    auto_create_agenda: true
    carry_over_unfinished_items: true
    attendance_tracking: true

Before each standup, the bot:

• Creates an agenda with carried-over action items
• Pings participants who haven't confirmed
• After the meeting, updates the action item tracker

Handling Conflicts and Rescheduling

User: "Reschedule tomorrow's design review to Thursday"

Bot: "Checking availability for Thursday...
  @Alice has a conflict at the original time (2:00 PM).
  Alternative slots on Thursday:
  1. 10:00 AM - 11:00 AM (all available)
  2. 3:00 PM - 4:00 PM (all available)
  
  Which do you prefer?"

The bot doesn't just move the event — it proactively checks for conflicts and offers solutions.

Monitoring Meeting Bot Usage

Track how the meeting bot is performing:

#!/bin/bash
echo "=== Meeting Bot Stats ==="
echo "Meetings scheduled this week: $(grep -c 'meeting_created' /var/log/clawdbot/output.log)"
echo "Rescheduling requests: $(grep -c 'meeting_rescheduled' /var/log/clawdbot/output.log)"
echo "Notes distributed: $(grep -c 'notes_sent' /var/log/clawdbot/output.log)"
echo "Action items created: $(grep -c 'action_item' /var/log/clawdbot/output.log)"

Start Building

Meeting management is one of the highest-ROI skills you can give your Lark bot. Every minute saved on scheduling logistics is a minute spent on actual work.

1. Visit https://www.tencentcloud.com/act/pro/intl-openclaw to deploy your OpenClaw instance.
2. Select the "OpenClaw (Clawdbot)" template under "AI Agents".
3. Deploy and turn your Lark bot into the meeting assistant your team actually wants.

Let the bot handle the calendar. You handle the decisions.