salesloft-debug-bundle

name	salesloft-debug-bundle
description	Collect SalesLoft debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic info for SalesLoft API problems. Trigger: "salesloft debug", "salesloft diagnostic", "salesloft support bundle".
allowed-tools	Read, Bash(curl:*), Bash(tar:*), Grep
version	1.6.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","sales","outreach","salesloft"]
compatibility	Designed for Claude Code

SalesLoft Debug Bundle

Overview

Collect diagnostic data for SalesLoft API issues: authentication state, rate limit usage, endpoint reachability, and API log entries. SalesLoft provides API Logs in the developer portal for request-level debugging.

Prerequisites

• SalesLoft API key or OAuth token
• curl and jq available
• Access to SalesLoft developer portal for API logs

Instructions

Step 1: Create Debug Script

#!/bin/bash
# salesloft-debug.sh
set -euo pipefail

BUNDLE="salesloft-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"
TOKEN="${SALESLOFT_API_KEY:?Set SALESLOFT_API_KEY}"

echo "=== SalesLoft Debug Bundle ===" | tee "$BUNDLE/summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE/summary.txt"

Step 2: Check Authentication & Identity

echo "--- Auth Check ---" >> "$BUNDLE/summary.txt"
curl -s -w "\nHTTP_STATUS: %{http_code}\n" \
  -H "Authorization: Bearer $TOKEN" \
  https://api.salesloft.com/v2/me.json \
  | jq '{id: .data.id, email: .data.email, name: .data.name, role: .data.role}' \
  >> "$BUNDLE/auth.json" 2>&1

Step 3: Check Rate Limit State

echo "--- Rate Limits ---" >> "$BUNDLE/summary.txt"
curl -sI -H  \
  https://api.salesloft.com/v2/people.json?per_page=1 \
  | grep -iE  \
  >>  2>&1