Configuration
Set up integrations and tune thresholds for your organization's infrastructure needs
Integration Setup
Superkabe integrates with Clay, Smartlead, EmailBison, and Instantly to monitor your outbound infrastructure.
Sending Platform API Keys
Location: Settings → Integrations
Required: Yes (for campaign routing and bounce monitoring)
API Key Format:
sl_live_xxxxxxxxxxxxxxxxxxxxClay Webhook
Webhook URL:
https://api.superkabe.com/webhooks/clayRequired Fields:
- •
email - •
firstName - •
lastName - •
company - •
campaignId— Campaign ID to route to
Threshold Configuration
All monitoring thresholds are configurable at the organization level. Default values are production-hardened.
Mailbox-Level Thresholds
| Threshold | Default Value | Description |
|---|---|---|
| MAILBOX_WARNING_BOUNCES | 3 | Bounces to trigger warning |
| MAILBOX_WARNING_WINDOW | 60 | Sends within warning window |
| MAILBOX_PAUSE_BOUNCES | 5 | Bounces to trigger pause |
| MAILBOX_PAUSE_WINDOW | 100 | Sends within pause window |
| ROLLING_WINDOW_SIZE | 100 | Window before sliding |
Domain-Level Thresholds
| Threshold | Default Value | Description |
|---|---|---|
| DOMAIN_WARNING_RATIO | 0.3 | 30% unhealthy → warning |
| DOMAIN_PAUSE_RATIO | 0.5 | 50% unhealthy → pause |
| DOMAIN_MINIMUM_MAILBOXES | 3 | Below this, use absolute logic |
Risk Score Thresholds
| Threshold | Default Value | Description |
|---|---|---|
| HARD_RISK_CRITICAL | 60 | Hard score → blocks execution |
| HARD_RISK_WARNING | 40 | Hard score → warning state |
| SOFT_RISK_HIGH | 75 | Soft score → logs only |
| SOFT_RISK_WARNING | 50 | Soft score → monitoring |
Cooldown Configuration
| Threshold | Default Value | Description |
|---|---|---|
| COOLDOWN_MINIMUM_MS | 3600000 | 1 hour minimum |
| COOLDOWN_MULTIPLIER | 2 | Exponential backoff |
| COOLDOWN_MAX_MS | 57600000 | 16 hours maximum |
⚠️ Tuning Warning
These thresholds are production-hardened based on industry best practices:
- • 5% bounce rate is the maximum before reputation damage
- • Lowering thresholds increases false positives
- • Raising thresholds risks permanent domain burnout
- • Test changes in OBSERVE mode first
System Mode
Configure the enforcement behavior for your organization:
OBSERVE
No automated actions. All events logged.
Use for: Testing and learning baseline metrics
SUGGEST
Provides recommendations without enforcement.
Use for: Reviewing automation suggestions
ENFORCE
Fully automated protection and pausing.
Use for: Production-ready automated safety
🎯 Best Practice
Recommended configuration workflow:
- 1. Start in OBSERVE — Run for 1 week to establish baseline
- 2. Review metrics — Confirm thresholds align with your infra
- 3. Switch to SUGGEST — Review automated recommendations for 1 week
- 4. Enable ENFORCE — Full production protection