| name | elevenlabs-ci-integration |
| description | Configure CI/CD pipelines for ElevenLabs with mocked unit tests and gated
integration tests.
Use when setting up GitHub Actions for TTS projects, configuring CI test
strategies, or automating ElevenLabs integration validation without burning
character quota on every PR.
Trigger with "elevenlabs CI", "elevenlabs GitHub Actions",
"elevenlabs automated tests", "CI elevenlabs", "elevenlabs pipeline".
|
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","voice","ai","elevenlabs","ci","github-actions"] |
| compatibility | Designed for Claude Code |
ElevenLabs CI Integration
Overview
Set up CI/CD pipelines that test ElevenLabs integrations without burning
character quota on every PR. Uses a two-tier strategy: mocked unit tests on
every push (no API key, zero quota), and gated integration tests that hit
the real API only on main or a manual dispatch, behind a quota guard.
The full workflow YAML and secret setup live in
references/implementation.md; the complete test
code lives in references/examples.md. This file walks
the strategy end to end, then drills into either reference for copy-paste source.
Prerequisites
- GitHub repository with Actions enabled
- ElevenLabs API key for integration tests (use a test/dev key, not production)
- npm/pnpm project with vitest configured
Instructions
Step 1: Add the two-tier workflow
Create .github/workflows/elevenlabs-tests.yml with two jobs. unit-tests
runs on every push/PR with a mock key. integration-tests runs only on main
or workflow_dispatch, needs: unit-tests, and checks remaining quota before
spending any:
jobs:
unit-tests:
runs-on: ubuntu-latest
steps: [checkout, setup-node, npm ci, npm test -- --coverage]
integration-tests:
if: github.ref == 'refs/heads/main' || github.event_name == 'workflow_dispatch'
