Webex Meeting Data Exporter

Export Webex meeting data (recordings, transcripts, summaries, and action items) to a local folder or to Google Drive so you can use it with tools like Gemini. List and pick existing meetings to export.

Quick Start

git clone https://github.com/WebexSamples/meetings-exporter.git
cd meetings-exporter
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
cp env.template .env
# Edit .env and set WEBEX_ACCESS_TOKEN
meetings-exporter list --from 2026-02-01 --to 2026-02-28 --max 5
meetings-exporter export MEETING_ID --output-dir ./exports

Table of Contents

• Quick Start
• Prerequisites
• Installation
• Configuration
• Usage
• Export Backends
• Webhook Server
• Architecture
• Project Structure
• Testing
• Contributing
• Github Actions
• Installing Prettier via npm (Local Machine)
• Installing and Running Ruff Python Linter
• Pre-Commit Hooks
• Skipping Hooks
• Roadmap
• License
• Thanks!

Prerequisites

• Python 3.11 or later
• Webex account and a Personal Access Token (or OAuth2 app) from developer.webex.com
• For Google Drive export only: Google Cloud project with Drive API enabled and OAuth client credentials

Meetings must be individual instances (not series) to get summaries, recordings, and transcripts. The app lists and exports instance meetings by default.

Installation

1. Clone the repository

git clone https://github.com/WebexSamples/meetings-exporter.git
cd meetings-exporter

2. Create a virtual environment and install the package

python3 -m venv .venv
source .venv/bin/activate   # On Windows: .venv\Scripts\activate
pip install -e ".[dev]"

After this, the meetings-exporter command is available in that environment.

Configuration

1. Copy the environment template

cp env.template .env

2. Set your Webex access token (required for list and export)

Edit .env and set:

WEBEX_ACCESS_TOKEN=your_personal_access_token_here

Get a token from Webex for Developers. No Google or OAuth setup is needed if you only export to a local folder (see Usage).

3. Optional: Google Drive export

To export to Google Drive instead of (or in addition to) local folder:

Step 1: Create OAuth credentials in Google Cloud Console

1. Go to APIs & Services → Credentials
2. Click Create Credentials → Create OAuth client ID
3. If prompted to configure the consent screen first, go to OAuth consent screen and complete it before continuing:
   • User type: External (or Internal if using Google Workspace)
   • App information: App name (e.g. "meetings-exporter"), User support email, Developer contact email. App logo is optional—skip for personal use
   • Scopes: Skip—the app requests drive.file at runtime
   • Test users: Add your Google account email—required for apps in Testing mode; only listed users can sign in
   • Return to Credentials and click Create Credentials → Create OAuth client ID again
4. 1 Credential Type: Select Google Drive API, then User data → Next
5. 2 OAuth Consent Screen and 3 Scopes: Click through (or configure if first time—see above)
6. 4 OAuth Client ID: Application type Desktop app, Name (e.g. "meetings-exporter") → Create
7. 5 Your Credentials: Click Download JSON and save the file (e.g. credentials.json) somewhere safe—do not commit it to git

Step 2: Configure .env

EXPORT_BACKEND=google_drive
GOOGLE_CREDENTIALS_FILE=/path/to/your/credentials.json

Optional: set GOOGLE_DRIVE_FOLDER_ID to a Drive folder ID if you want exports under a specific folder (otherwise they go to Drive root).

Step 3: First run

On first export, the app opens a browser for you to sign in and authorize access. A token.json file is saved locally so you won't need to re-authorize unless you revoke access or the token expires.

"Access blocked" or "has not completed the Google verification process"

Your app is in Testing mode, so only approved test users can sign in. Add your Google account:

1. Go to OAuth consent screen
2. Click Test users → Add users
3. Add your email (e.g. yourname@gmail.com) and save
4. Retry the export

Usage

All commands require WEBEX_ACCESS_TOKEN in your environment (or in .env). Activate your venv before running.

List recent meetings (individual instances only)

meetings-exporter list --from 2026-02-01 --to 2026-02-28 --max 10

Use the meeting ID from the first column (it will look like ..._I_... for instances).

Export a single meeting to a local folder (no Google or cloud setup needed)

meetings-exporter export MEETING_ID --output-dir /path/to/exports

Export all meetings in a date range (no meeting ID required)

meetings-exporter export --from 2026-02-01 --to 2026-02-28 --output-dir /path/to/exports

Optional: --max N (default 100) limits how many meetings to export. Each meeting gets its own subfolder.

This creates folders under the output path with names like 2026-02-05 14-00 - Meeting Title (date-time first so they sort in order), containing meeting_details.txt, transcript.vtt, summary.txt, summary.json, and any recording files.

Export to Google Drive (requires Google credentials in .env)

meetings-exporter export MEETING_ID
# or by date range:
meetings-exporter export --from 2026-02-01 --to 2026-02-28

With EXPORT_BACKEND=google_drive and credentials configured, meetings are uploaded to Drive in the same structure.

Quick test: List a meeting, then export it to Drive:

meetings-exporter list --from 2026-02-01 --to 2026-02-28 --max 1
meetings-exporter export MEETING_ID_FROM_ABOVE

The first export opens a browser for OAuth; subsequent exports use the saved token. The command prints the Drive folder URL when done.

Export Backends

• Local folder (--output-dir PATH): Writes all assets to the given directory. No cloud credentials needed.
• Google Drive (EXPORT_BACKEND=google_drive): Uploads to Google Drive; requires OAuth credentials and optional GOOGLE_DRIVE_FOLDER_ID for a root folder.

OneDrive and Dropbox can be added later; the app is built so new backends plug in without changing ingestion logic.

Webhook Server

The webhook server receives Webex notifications when meetings end, recordings are ready, or transcripts are created, and automatically exports meeting data to your configured backend.

Prerequisites: ngrok for local testing (e.g. brew install ngrok).

Steps:

1. Start the webhook server:

meetings-exporter webhook --port 8080

2. In another terminal, start ngrok to expose your local server:

ngrok http 8080

3. Copy the HTTPS URL from ngrok (e.g. https://abc123.ngrok-free.app).

4. Register webhooks with Webex:

meetings-exporter webhook register --url https://abc123.ngrok-free.app

5. Run a Webex meeting, end it (with recording/transcript if desired), and observe webhook delivery and export in the server logs.

6. To remove webhooks when done:

meetings-exporter webhook unregister

Environment variables: WEBEX_ACCESS_TOKEN (required). Optional: WEBEX_WEBHOOK_SECRET for signature verification.

Architecture

flowchart LR
    subgraph CLI [CLI]
        List[List meetings]
        Export[Export meeting]
    end
    subgraph Core [Core]
        Webex[WebexClient]
        Ingest[Ingestion]
        Factory[Exporter Factory]
    end
    subgraph Backends [Export Backends]
        Local[LocalFolder]
        Drive[Google Drive]
    end
    List --> Webex
    Export --> Ingest
    Ingest --> Webex
    Ingest --> Factory
    Factory --> Local
    Factory --> Drive

Loading

The CLI calls export_meeting() in the ingestion layer, which fetches data via WebexClient and writes via the configured exporter. This design allows export_meeting() to be called programmatically (e.g. from a future webhook handler).

Project Structure

• src/meetings_exporter/ – Main package: Webex client, ingestion, exporters (local, Google Drive), CLI
• env.template – Environment variable template (copy to .env)
• tests/ – Pytest tests for ingestion, exporters, and webhook utilities

Testing

With the virtual environment activated and dev dependencies installed:

pytest tests/ -v

Contributing

See CONTRIBUTING.md for setup, code style, and how to submit changes.

Github Actions

This project uses GitHub Actions to enforce coding standards. These workflows run on every pull request and must pass before merging.

1. Test: Runs pytest. See .github/workflows/test.yml.
2. Ruff: Lints Python. See .github/workflows/ruff.yml.
3. Prettier: Checks formatting for JS/JSON/MD and other supported files. See .github/workflows/prettier.yml.

Installing Prettier via npm (Local Machine)

To format code locally:

npx prettier . --check    # Check only
npx prettier . --write    # Apply fixes

Installing and Running Ruff Python Linter

pip install ruff
ruff check .           # Check only
ruff check --fix .     # Apply fixes

Pre-Commit Hooks

The repo uses Husky and lint-staged. After npm install, the pre-commit hook runs Prettier and Ruff before each commit.

Skipping Hooks

• Single commit: git commit -m "..." -n
• Temporary: HUSKY=0 git ... then unset HUSKY when done

Roadmap

Webhook support is implemented. Use the Webhook Server section above for auto-export when meetings end, recordings are ready, or transcripts are created.

License

This project is licensed under the Cisco Sample Code License v1.1. Use is permitted only with Cisco products and services. See the LICENSE file for full terms.

Thanks!

Made with care by the Webex Developer Relations Team at Cisco.