customerio-ci-integration

Configure Customer.io CI/CD integration with automated testing. Use when setting up GitHub Actions, integration test suites, or pre-commit validation for Customer.io code. Trigger: "customer.io ci", "customer.io github actions", "customer.io pipeline", "customer.io automated testing".

Jump to install

Repository: jeremylongshore/claude-code-plugins-plus-skills
Last source activity: July 17, 2026 at 22:18
Detected SKILL.md language: English
Stars: 2,604
Forks: 378

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill customerio-ci-integration

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

2026-07-23

clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

2026-07-23

clerk-enterprise-rbac

Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".

2026-07-23

View all from this repository

Customer.io CI Integration

Overview

Set up CI/CD pipelines for Customer.io integrations: GitHub Actions workflow with unit + integration tests, test fixtures with automatic cleanup, pre-commit hooks, and environment-specific credential management.

Prerequisites

GitHub repository with Node.js project

Separate Customer.io workspace for CI testing (do NOT use production)

GitHub Actions secrets configured

Instructions

Step 1: GitHub Actions Workflow

# .github/workflows/customerio-tests.yml name: Customer.io Integration Tests on: push: paths: - "lib/customerio-*.ts" - "services/customerio-*.ts" - "tests/customerio*" pull_request: paths: - "lib/customerio-*.ts" - "services/customerio-*.ts" env: CUSTOMERIO_SITE_ID: ${{ secrets.CIO_TEST_SITE_ID }} CUSTOMERIO_TRACK_API_KEY: ${{ secrets.CIO_TEST_TRACK_API_KEY }} CUSTOMERIO_APP_API_KEY: ${{ secrets.CIO_TEST_APP_API_KEY }} CUSTOMERIO_REGION: us jobs: unit-tests: runs-on: ubuntu-latest steps: - uses:

name	customerio-ci-integration
description	Configure Customer.io CI/CD integration with automated testing. Use when setting up GitHub Actions, integration test suites, or pre-commit validation for Customer.io code. Trigger: "customer.io ci", "customer.io github actions", "customer.io pipeline", "customer.io automated testing".
allowed-tools	Read, Write, Edit, Bash(npm:), Bash(gh:), Glob, Grep
version	1.14.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","customer-io","ci-cd","testing","github-actions"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Customer.io CI Integration

Overview

Prerequisites

GitHub repository with Node.js project
Separate Customer.io workspace for CI testing (do NOT use production)
GitHub Actions secrets configured

Instructions

Step 1: GitHub Actions Workflow

# .github/workflows/customerio-tests.yml
name: Customer.io Integration Tests
on:
  push:
    paths:
      - "lib/customerio-*.ts"
      - "services/customerio-*.ts"
      - "tests/customerio*"
  pull_request:
    paths:
      - "lib/customerio-*.ts"
      - "services/customerio-*.ts"

env:
  CUSTOMERIO_SITE_ID: ${{ secrets.CIO_TEST_SITE_ID }}
  CUSTOMERIO_TRACK_API_KEY: ${{ secrets.CIO_TEST_TRACK_API_KEY }}
  CUSTOMERIO_APP_API_KEY: ${{ secrets.CIO_TEST_APP_API_KEY }}
  CUSTOMERIO_REGION: us

jobs:
  unit-tests:
    runs-on: ubuntu-latest
    steps:
      - uses:

// tests/customerio.integration.test.ts import { describe, it, expect, afterAll } from "vitest"; import { getCioTestClient, testUserId, cleanupTestUsers } from "./helpers/cio-test-utils"; const cio = getCioTestClient(); describe("Customer.io Integration", () => { afterAll(async () => { await cleanupTestUsers(cio); }); it("should identify a new user", async () => { const userId = testUserId("identify-new"); await expect( cio.identify(userId, { email: `${userId}@test.example.com`, created_at: Math.floor(Date.now() / 1000), }) ).resolves.not.toThrow(); }); it("should update an existing user", async () => { const userId = testUserId("identify-update"); await cio.identify(userId, { email: `${userId}@test.example.com` }); await expect( cio.identify(userId, { plan: "pro", updated: true }) ).resolves.not.toThrow(); }); it("should track an event on a user", async () => { const userId = testUserId("track-event"); await cio.identify(userId, { email: `${userId}@test.example.com` }); await expect( cio.track(userId, { name: "ci_test_event", data: { test_run: true, timestamp: Date.now() }, }) ).resolves.not.toThrow(); }); it("should track an anonymous event", async () => { await expect( cio.trackAnonymous({ anonymous_id: testUserId("anon"), name: "ci_anonymous_test", data: { page: "/test" }, }) ).resolves.not.toThrow(); }); it("should suppress a user", async () => { const userId = testUserId("suppress"); await cio.identify(userId, { email: `${userId}@test.example.com` }); await expect(cio.suppress(userId)).resolves.not.toThrow(); }); it("should reject invalid credentials", async () => { const badClient = new (await import("customerio-node")).TrackClient( "invalid", "invalid", { region: (await import("customerio-node")).RegionUS } ); await expect( badClient.identify("x", { email: "x@test.com" }) ).rejects.toThrow(); }); });

Practice	Rationale
Dedicated test workspace	Prevents CI from polluting dev/staging data
Unique test user IDs	Prevents collisions between parallel CI runs
Always cleanup in `afterAll`	Prevents accumulating stale test profiles
Rate limit awareness	Add small delays between batched API calls in CI
Skip integration tests if no creds	PRs from forks won't have secrets

Issue	Solution
Secrets not available in PR	Fork PRs don't get secrets — skip integration tests gracefully
Test user pollution	Use `${TEST_RUN_ID}` prefix, cleanup in `afterAll`
Rate limiting in CI	Keep integration test count under 50 API calls
Flaky network failures	Add retry logic to integration tests

customerio-ci-integration

Install options

Review the source files

Customer.io CI Integration

Overview

Prerequisites

Instructions

Step 1: GitHub Actions Workflow

Customer.io CI Integration

Overview

Prerequisites

Instructions

Step 1: GitHub Actions Workflow

Step 2: Test Fixtures and Helpers

Step 3: Integration Test Suite

Step 4: Test User Cleanup Script

Step 5: GitHub Secrets Setup

Step 6: Pre-commit Hook

CI Best Practices

Error Handling

Resources

Next Steps

customerio-ci-integration

Source facts

Install options

Review the source files

More from this repository

Customer.io CI Integration

Overview

Prerequisites

Instructions

Step 1: GitHub Actions Workflow

More from this repository

Customer.io CI Integration

Overview

Prerequisites

Instructions

Step 1: GitHub Actions Workflow

Step 2: Test Fixtures and Helpers

Step 3: Integration Test Suite

Step 4: Test User Cleanup Script

Step 5: GitHub Secrets Setup

Step 6: Pre-commit Hook

CI Best Practices

Error Handling

Resources

Next Steps