procore-debug-bundle

Collect Procore debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Procore problems. Trigger with phrases like "procore debug", "procore support bundle", "collect procore logs", "procore diagnostic".

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

Allowed Tools

ReadBash(grep:*)Bash(curl:*)Bash(tar:*)Grep

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 Debug Bundle

Overview

Collect all necessary diagnostic information for Procore support tickets.

Prerequisites

  • Procore SDK installed
  • Access to application logs
  • Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script


#!/bin/bash
# procore-debug-bundle.sh

BUNDLE_DIR="procore-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Procore Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"

Step 2: Collect Environment Info


# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "PROCORE_API_KEY: ${PROCORE_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs


# SDK version
npm list @procore/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"

# Recent logs (redacted)
grep -i "procore" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"

# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"

# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.procore.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"

Step 4: Package Bundle


tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"

Output

  • procore-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
  • summary.txt - Environment and SDK info
  • logs.txt - Recent redacted logs
  • config-redacted.txt - Configuration (secrets removed)

Error Handling

Item Purpose Included
Environment versions Compatibility check
SDK version Version-specific bugs
Error logs (redacted) Root cause analysis
Config (redacted) Configuration issues
Network test Connectivity issues

Examples

Sensitive Data Handling

ALWAYS REDACT:

  • API keys and tokens
  • Passwords and secrets
  • PII (emails, names, IDs)

Safe to Include:

  • Error messages
  • Stack traces (redacted)
  • SDK/runtime versions

Submit to Support

  1. Create bundle: bash procore-debug-bundle.sh
  2. Review for sensitive data
  3. Upload to Procore support portal

Resources

Next Steps

For rate limit issues, see procore-rate-limits.

Ready to use procore-pack?