bcharleson/clay-gtm-cli/clay-reply-classify

npm install -g clay-gtm-cli
brew install cloudflared
clay tables add \
  --name reply-classify \
  --webhook-url https://app.clay.com/webhook/YOUR_WEBHOOK_ID \
  --description "Classify email replies — category, sentiment, next action"
clay listen start

# Classify a reply
clay fire reply-classify \
  --data '{
    "reply_text": "Hey, this actually looks interesting. Can we jump on a call next week?",
    "sender_email": "john@acme.com",
    "original_subject": "Quick question on RevOps tooling"
  }' \
  --wait
 
# Classify with full thread context
clay fire reply-classify \
  --data '{
    "reply_text": "We already use a competitor for this. Thanks anyway.",
    "sender_email": "jane@acme.com",
    "original_subject": "RevOps automation",
    "sequence_step": 2,
    "days_since_first_touch": 8
  }' \
  --wait
 
# Classify with prospect context (improves routing accuracy)
clay fire reply-classify \
  --data '{
    "reply_text": "Not the right time — budget is locked until Q3.",
    "sender_email": "cro@bigco.com",
    "original_subject": "Scaling RevOps post-Series C",
    "prospect_icp_tier": "A",
    "company_domain": "bigco.com"
  }' \
  --wait

{
  "success": true,
  "table": "reply-classify",
  "data": {
    "sender_email": "john@acme.com",
    "classification": "interested",
    "confidence": 0.97,
    "sentiment": "positive",
    "intent": "meeting_request",
    "urgency": "high",
    "key_signals": ["asked for call", "next week availability", "positive tone"],
    "objections": [],
    "timing_signal": "immediate",
    "referral_name": null,
    "next_action": "book_meeting",
    "next_action_detail": "Reply within 1 hour with calendar link. This is a warm reply — high close probability.",
    "suggested_reply": "Great to hear, John! Happy to connect. Here's my calendar: [link]. Do any of these slots work for you?",
    "notify_rep": true,
    "crm_stage_move": "Engaged"
  }
}

# Classify and only act on interested replies
clay fire reply-classify \
  --data '{"reply_text":"Yes lets talk — when are you free?","sender_email":"cto@startup.com"}' \
  --wait | jq 'select(.data.classification == "interested") | .data.next_action_detail'
 
# Get suggested reply text
clay fire reply-classify \
  --data '{"reply_text":"This looks relevant, send me more info","sender_email":"vp@acme.com"}' \
  --wait | jq -r '.data.suggested_reply'
 
# Catch unsubscribe requests before they escalate
clay fire reply-classify \
  --data '{"reply_text":"Please remove me from your list","sender_email":"contact@co.com"}' \
  --wait | jq 'select(.data.classification == "unsubscribe_request") | {email: .data.sender_email, action: "remove_immediately"}'
 
# Classify objection and extract timing signal
RESULT=$(clay fire reply-classify \
  --data '{"reply_text":"Not now — check back in Q4","sender_email":"cfo@bigco.com"}' \
  --wait)
CLASS=$(echo $RESULT | jq -r '.data.classification')
TIMING=$(echo $RESULT | jq -r '.data.timing_signal')
echo "Classification: $CLASS | Timing: $TIMING"
 
# Route competitors to nurture, timing objections to future pipeline
clay fire reply-classify \
  --data '{"reply_text":"We just signed with Competitor X last month","sender_email":"vp@co.com"}' \
  --wait | jq 'select(.data.classification == "objection_competitor") | {action: "add_to_competitor_nurture", crm_stage: "Lost - Competitor"}'

clay usage show reply-classify
clay tables reset reply-classify --webhook-url https://app.clay.com/webhook/NEW_ID