vexaSend Vexa bots to meetings and operate transcript workflows end-to-end (during and after meetings): parse meeting links, request/stop bots, read live/final transcripts, create basic meeting reports, set webhook delivery, and enrich meeting metadata. Use when a user drops a Google Meet/Teams link, asks to auto-join meetings from calendar events, or needs transcript retrieval/summarization/knowledge updates from Vexa. After a meeting ends, create a report with meeting info, transcript, and placeholders for summary/decisions/action items. Treat transcript purge (meeting delete) as destructive and require explicit confirmation.
Install via ClawdBot CLI:
clawdbot install DmitriyG228/vexaSpeak directly to the user as in a natural chat. Do not output internal reasoning, plan summaries, or procedural notes ("I need to...", "According to the skill...", "I will inform..."). Reply with only what you would say to the user — conversational, warm, and to the point.
Use the bundled CLI:
node skills/vexa/scripts/vexa.mjs ...node skills/vexa/scripts/onboard.mjs ...node skills/vexa/scripts/ingest.mjs ...node skills/vexa/scripts/audit.mjsSet for the OpenClaw process (or shell):
VEXA_API_KEY (required)VEXA_BASE_URL (optional, default https://api.cloud.vexa.ai)Always check first: node skills/vexa/scripts/onboard.mjs --check-secrets
{"secrets_ok": true} → secrets exist. Skip onboarding. Use normal flows.{"secrets_ok": false} → run onboarding. Load references/onboarding-flow.md.Webhook — proactive setup: Whenever secrets exist and you're working with Vexa, run node skills/vexa/scripts/onboard.mjs --check-webhook. If webhook_configured is false, advise adding the vexa mapping (see references/webhook-setup.md). For onboarding-only details (webhook requirements, pipeline validation, mock webhook), load references/onboarding-flow.md.
When secrets are missing: Ask them to get their key from https://vexa.ai/dashboard/api-keys and paste it in chat — you write it to skills/vexa/secrets/vexa.env. Alternatively, share the path and format so they can add it manually (better for security if they prefer not to paste the key).
Secrets location: skills/vexa/secrets/ holds vexa.env (API key) and vexa-state.json. This dir is gitignored. When publishing the skill to ClawHub, ensure secrets/ is excluded.
Non-interactive (for scripting): onboard.mjs --api_key
--check-webhook. If not configured, offer to set it up so finished meetings auto-trigger reports.node skills/vexa/scripts/vexa.mjs parse:meeting-url --meeting_url "https://meet.google.com/abc-defg-hij"node skills/vexa/scripts/vexa.mjs bots:start --meeting_url "https://meet.google.com/abc-defg-hij" --bot_name "Claw" --language ennode skills/vexa/scripts/vexa.mjs bots:start --meeting_url "https://teams.live.com/meet/9387167464734?p=qxJanYOcdjN4d6UlGa" --bot_name "Claw" --language enIf a calendar tool/skill is available (for example gog):
bots:start --meeting_url ....meetings:update --name "" --notes "source: calendar" node skills/vexa/scripts/vexa.mjs transcripts:get --platform google_meet --native_meeting_id abc-defg-hijreferences/user-api-guide-notes.md for endpoints and notes).node skills/vexa/scripts/vexa.mjs bots:stop --meeting_url "" After stopping the bot (or once the meeting has ended and transcript is finalized), create a basic meeting report:
node skills/vexa/scripts/vexa.mjs report --meeting_url "https://meet.google.com/abc-defg-hij"node skills/vexa/scripts/ingest.mjs --meeting_url "" Writes to memory/meetings/YYYY-MM-DD- with: meeting info, summary placeholders, key decisions, action items, and full transcript.
node skills/vexa/scripts/vexa.mjs bots:statusnode skills/vexa/scripts/vexa.mjs bots:start --platform google_meet --native_meeting_id abc-defg-hij --bot_name "Claw" --language ennode skills/vexa/scripts/vexa.mjs bots:config:update --platform google_meet --native_meeting_id abc-defg-hij --language esnode skills/vexa/scripts/vexa.mjs meetings:listnode skills/vexa/scripts/vexa.mjs meetings:update --platform google_meet --native_meeting_id abc-defg-hij --name "Weekly Product Sync" --participants "Alice,Bob" --languages "en" --notes "Action items captured"node skills/vexa/scripts/vexa.mjs transcripts:share --platform google_meet --native_meeting_id abc-defg-hij --ttl_seconds 3600node skills/vexa/scripts/vexa.mjs user:webhook:set --webhook_url https://your-public-url/hooks/vexaWhen Vexa sends a "meeting finished" webhook, the transform (scripts/vexa-transform.mjs) instructs the agent to create a report. See references/webhook-setup.md for hooks mapping config. Requires hooks.transformsDir = workspace root and transform.module = skills/vexa/scripts/vexa-transform.mjs.
node skills/vexa/scripts/vexa.mjs report --meeting_url "" node skills/vexa/scripts/ingest.mjs --meeting_url "" (or --platform + --native_meeting_id)node skills/vexa/scripts/audit.mjsgoogle_meet, teamsnative_meeting_id must be numeric ID only.?p= in Teams URL).DELETE /meetings/{platform}/{native_meeting_id} purges transcripts and anonymizes data.
Rules:
platform + native_meeting_id first.meetings:update) whenever possible.node skills/vexa/scripts/vexa.mjs meetings:delete --platform google_meet --native_meeting_id abc-defg-hij --confirm DELETEGenerated Mar 1, 2026
A distributed software team uses the skill to automatically join daily stand-ups via Google Meet links from their calendar. The bot transcribes discussions, and after the meeting, generates a report with action items and decisions, which is shared via Slack for follow-up.
A consulting firm deploys the bot to client meetings on Microsoft Teams to capture detailed transcripts. Post-meeting, reports are created with summaries and key insights, which are stored in a CRM for future reference and compliance.
An online education platform uses the skill to send bots to scheduled webinar sessions on Google Meet. Transcripts are retrieved in real-time for live captioning, and final reports are generated for content review and student notes.
A hospital staff uses the skill to join multidisciplinary team meetings on Teams, ensuring accurate transcription of patient discussions. Reports are created with summaries and action items, integrated into electronic health records for continuity of care.
A sales team employs the bot to record and transcribe demo calls with potential clients on Google Meet. After meetings, reports highlight key objections and decisions, helping refine sales strategies and track follow-ups.
Offer the skill as part of a monthly subscription service for teams, providing access to bot deployments, transcript storage, and report generation. Revenue is generated through tiered pricing based on meeting volume and advanced features like real-time analytics.
Provide basic transcription and report creation for free with limited meetings per month. Upsell premium features such as advanced summarization, custom webhook integrations, and priority support to convert users to paid plans.
Sell annual enterprise licenses to large organizations, including custom integrations with existing tools like CRM and project management software. Revenue includes upfront licensing fees and ongoing support contracts for scalability and security.
💬 Integration Tip
Ensure the VEXA_API_KEY is securely set in environment variables before use, and proactively configure webhooks to automate report generation post-meeting for seamless workflow integration.
Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them. Use this skill when you need programmatic access to your calendar from OpenClaw.
Read, search, and manage Outlook emails and calendar via Microsoft Graph API. Use when the user asks about emails, inbox, Outlook, Microsoft mail, calendar events, or scheduling.
Google Calendar via gcalcli: today-only agenda by default, bounded meaning-first lookup via agenda scans, and fast create/delete with verification--optimized for low tool calls and minimal output.
This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations.
Access and manage Google Calendar events with gogcli for cross-calendar agendas, keyword search, and filtered outputs avoiding unwanted calendars like holidays.
Daily morning rollup of important emails and calendar events at 8am with AI-generated summaries