Skip to main content

Platform Integrations

Integrate Status Check with your favorite automation platforms and workflows.

Overview​

Status Check is designed to work seamlessly with popular workflow automation platforms, allowing you to build sophisticated lead enrichment and validation pipelines without writing code.

Available Integrations​

Webhook-Based Integration (Universal)​

The most flexible way to integrate Status Check with any platform that supports webhooks.

Supported Platforms:

  • n8n
  • Zapier
  • Make (Integromat)
  • Pipedream
  • Integromat
  • Any custom application

How it works:

  1. Register a webhook in Status Check
  2. Subscribe to events (validation.complete, credits.low, etc.)
  3. Receive real-time notifications when events occur
  4. Process results in your workflow

Learn More: Webhook Integration Guide

HTTP API Integration​

For platforms that support HTTP API calls (like Clay), you can directly call Status Check endpoints.

Supported Platforms:

  • Clay
  • Airtable Automations
  • Google Sheets + Apps Script
  • Custom applications
  • Any platform with HTTP request capabilities

Typical Workflow:

Data Source → HTTP API Call to Status Check → Process Results → Destination

Example Use Cases:

  • Enrich leads in Clay tables
  • Validate form submissions in Airtable
  • Check domains from Google Sheets
  • Real-time validation in custom apps

Integration Patterns​

Pattern 1: Lead Enrichment Flow​

Goal: Validate and score leads before adding to CRM

Source (CSV, Google Sheets, Airtable)
  ↓
Status Check API - Create & Validate Leads
  ↓
Filter by Score (leadDeliverabilityRating > 70)
  ↓
CRM (HubSpot, Salesforce, Pipedrive)

Platforms: n8n, Zapier, Make, Clay

Endpoints Used:

  • POST /v1/leads/bulk - Create multiple leads
  • POST /v1/leads/validate - Trigger validation
  • Webhook: validation.complete - Get results

Pattern 2: Real-Time Form Validation​

Goal: Validate email/domain when user submits a form

Form Submission (Typeform, Webflow, Custom)
  ↓
Status Check API - Validate Single Lead
  ↓
Decision:
  • High Score → Accept & Add to CRM
  • Low Score → Reject or Flag for Review

Platforms: Zapier, Make, n8n, Custom webhooks

Endpoints Used:

  • POST /v1/leads - Create and validate single lead
  • GET /v1/leads/{id} - Check validation status

Pattern 3: Nightly Batch Processing​

Goal: Validate large lists on schedule

Scheduled Trigger (Daily at 2 AM)
  ↓
Export from CRM/Database
  ↓
Status Check API - Bulk Validate
  ↓
Wait for Completion (webhook or polling)
  ↓
Update CRM with Results

Platforms: n8n, Zapier, Make

Endpoints Used:

  • POST /v1/leads/bulk - Upload batch
  • POST /v1/leads/validate - Trigger validation
  • Webhook: validation.complete - Notification

Platform-Specific Guides​

n8n​

Status: Community node available (coming soon)

Installation:

npm install @status-check/n8n-nodes-status-check

Features:

  • API key authentication
  • Create and validate leads
  • Query leads
  • Webhook triggers for events

Example Workflow:

CSV File → Status Check (Validate) → Filter (Score > 80) → HTTP Request (CRM)

Zapier​

Status: Native app (coming soon)

Connection: Search for "Status Check" in Zapier app directory

Triggers:

  • Validation Complete
  • Credits Low
  • New Lead Created

Actions:

  • Create and Validate Lead
  • Get Lead Details
  • Update Lead

Make (Integromat)​

Status: Custom app (coming soon)

Modules:

  • Create Lead
  • Validate Leads
  • Get Lead
  • Watch Validation Complete (webhook)

Clay​

Current Method: HTTP API Enrichment

Setup: See Clay Integration Guide in the webhook documentation

Steps:

  1. Add HTTP API enrichment
  2. Configure POST request to Status Check API
  3. Map response fields to Clay columns
  4. Use filters to route based on score

Getting Started​

Step 1: Get Your API Key​

  1. Sign up at app.status-check.io/signup
  2. Navigate to Account Settings
  3. Click "API Keys" tab
  4. Create a new API key
  5. Copy and save securely

Step 2: Choose Your Integration Method​

Use Webhooks if:

  • You want real-time event notifications
  • Your workflow is event-driven
  • You're using n8n, Zapier, Make, or similar platforms

Use HTTP API if:

  • You need synchronous responses
  • You're building custom integrations
  • You're using platforms like Clay or Airtable

Step 3: Build Your First Workflow​

Start with a simple validation workflow:

# Example: Single lead validation
curl -X POST https://api.status-check.io/v1/leads \
  -H "X-API-Key: sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "test@example.com",
    "website": "https://example.com",
    "validate": true
  }'

Response:

{
  "leadId": "lead_abc123",
  "leadDeliverabilityRating": 95,
  "emailValid": true,
  "domainHttpStatus": 200,
  "leadRecommendation": "high_priority"
}

Step 4: Scale Up​

Once your first workflow is working:

  1. Add webhooks for event notifications
  2. Batch process larger lists
  3. Build complex flows with multiple steps
  4. Monitor usage in your dashboard

Common Workflows​

Workflow 1: Lead List Cleanup​

Use Case: Clean an existing lead database

Airtable (Existing Leads)
  ↓
Status Check - Bulk Validate
  ↓
Update Airtable:
  • Add deliverability score
  • Flag invalid emails
  • Update domain status

Workflow 2: Form Validation​

Use Case: Validate leads as they come in

Typeform Submission
  ↓
Status Check - Validate Lead
  ↓
Router:
  • Score > 80 → Slack Notification + Add to HubSpot
  • Score 50-80 → Add to Nurture List
  • Score < 50 → Discard

Workflow 3: Scheduled Enrichment​

Use Case: Enrich CRM data daily

Scheduler (Daily 2 AM)
  ↓
Get New Leads from HubSpot
  ↓
Status Check - Validate
  ↓
Update HubSpot with Scores
  ↓
Email Report to Sales Team

Best Practices​

1. Handle Rate Limits​

Status Check enforces rate limits (60/min, 1000/hour). For large batches:

  • Use bulk endpoints (/v1/leads/bulk)
  • Space out API calls
  • Use webhooks instead of polling
  • Monitor rate limit headers

2. Implement Error Handling​

Always handle these scenarios:

  • 402 Insufficient Credits - Notify user or pause workflow
  • 429 Rate Limit - Retry with exponential backoff
  • 500 Server Error - Retry or alert admin

3. Use Webhooks for Async Operations​

For validation operations, use webhooks instead of polling:

✅ Good: Register webhook → Receive notification when complete ❌ Bad: Call API repeatedly to check status

4. Verify Webhook Signatures​

Always verify webhook signatures to ensure requests are from Status Check:

import hmac
import hashlib

def verify_signature(payload, signature, secret):
    expected = hmac.new(
        secret.encode(),
        payload.encode(),
        hashlib.sha256
    ).hexdigest()
    return signature == f"sha256={expected}"

5. Monitor Credit Usage​

  • Check credit balance before large operations
  • Set up low credit alerts via webhooks
  • Monitor usage in dashboard

Support​

Need help with your integration?

Next Steps​