procore-ci-integration

Configure Procore CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Procore tests into your build process. Trigger with phrases like "procore CI", "procore GitHub Actions", "procore automated tests", "CI procore".

claude-code
4 Tools
procore-pack Plugin
saas packs Category

Allowed Tools

ReadWriteEditBash(gh:*)

Provided by Plugin

procore-pack

Claude Code skill pack for Procore (24 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the procore-pack plugin:

/plugin install procore-pack@claude-code-plugins-plus

Click to copy

Instructions

Procore CI Integration

Overview

Set up CI/CD pipelines for Procore integrations with automated testing.

Prerequisites

  • GitHub repository with Actions enabled
  • Procore test API key
  • npm/pnpm project configured

Instructions

Step 1: Create GitHub Actions Workflow

Create .github/workflows/procore-integration.yml:


name: Procore Integration Tests

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

env:
  PROCORE_API_KEY: ${{ secrets.PROCORE_API_KEY }}

jobs:
  test:
    runs-on: ubuntu-latest
    env:
      PROCORE_API_KEY: ${{ secrets.PROCORE_API_KEY }}
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test -- --coverage
      - run: npm run test:integration

Step 2: Configure Secrets


gh secret set PROCORE_API_KEY --body "sk_test_***"

Step 3: Add Integration Tests


describe('Procore Integration', () => {
  it.skipIf(!process.env.PROCORE_API_KEY)('should connect', async () => {
    const client = getProcoreClient();
    const result = await client.healthCheck();
    expect(result.status).toBe('ok');
  });
});

Output

  • Automated test pipeline
  • PR checks configured
  • Coverage reports uploaded
  • Release workflow ready

Error Handling

Issue Cause Solution
Secret not found Missing configuration Add secret via gh secret set
Tests timeout Network issues Increase timeout or mock
Auth failures Invalid key Check secret value

Examples

Release Workflow


on:
  push:
    tags: ['v*']

jobs:
  release:
    runs-on: ubuntu-latest
    env:
      PROCORE_API_KEY: ${{ secrets.PROCORE_API_KEY_PROD }}
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
      - run: npm ci
      - name: Verify Procore production readiness
        run: npm run test:integration
      - run: npm run build
      - run: npm publish

Branch Protection


required_status_checks:
  - "test"
  - "procore-integration"

Resources

Next Steps

For deployment patterns, see procore-deploy-integration.

Ready to use procore-pack?